Loading core/misc/cspell/dictionary.txt +0 −3 Original line number Diff line number Diff line Loading @@ -20,9 +20,6 @@ arrowstop arrowthick arrowthickstop assertable autocompletefocus autocompleteselect autocompleting autoconfiguration autoconfigure autoconfigured Loading core/tests/Drupal/Nightwatch/Tests/claroAutocompleteTest.js +4 −1 Original line number Diff line number Diff line // cspell:ignore is-autocompleting module.exports = { '@tags': ['core'], Loading Loading @@ -28,7 +30,8 @@ module.exports = { .waitForElementVisible('body', 1000); // Tests that entering a character from the // data-autocomplete-first-character-blacklist doesn't start autocompleting. // data-autocomplete-first-character-blacklist doesn't start the // autocomplete process. browser .setValue('[name="autocomplete_4"]', '/') .pause(1000) Loading core/themes/claro/css/components/autocomplete-loading.module.css +7 −5 Original line number Diff line number Diff line Loading @@ -12,6 +12,8 @@ * @see autocomplete.js */ /* cspell:ignore is-autocompleting */ /** * Since the autocomplete library is attached conditionally and not globally, * we can be 99% sure that the default icon will be used. Loading @@ -19,14 +21,14 @@ * autocomplete input's background — until are sure that it will be pushed by * the server with HTTP/2. * * The autocompleting (active) state's background-image is inlined because * non-used CSS selectors are usually ignored; popular browsers don't download * their 'url' references. * The active autocomplete state's background-image is inlined because non-used * CSS selectors are usually ignored; popular browsers don't download their * 'url' references. * If these selectors become active, the browser needs some time for painting * previously ignored remote asset: it should get it from server, parse it and * repaint the background of autocomplete field. With the inlined background we * can prevent an additional timeout caused by a new request/response pair. * Besides this, the autocompleting event itself may easily finish before the * Besides this, the autocomplete event itself may easily finish before the * missing asset gets downloaded/parsed/painted, and the missing instant visual * feedback would be a usability/accessibility issue as well. */ Loading @@ -53,7 +55,7 @@ } /** * Autocomplete wrapper for autocompleting message. * Autocomplete wrapper for autocomplete message. */ .claro-autocomplete { Loading core/themes/claro/css/components/autocomplete-loading.module.pcss.css +7 −5 Original line number Diff line number Diff line Loading @@ -5,6 +5,8 @@ * @see autocomplete.js */ /* cspell:ignore is-autocompleting */ /** * Since the autocomplete library is attached conditionally and not globally, * we can be 99% sure that the default icon will be used. Loading @@ -12,14 +14,14 @@ * autocomplete input's background — until are sure that it will be pushed by * the server with HTTP/2. * * The autocompleting (active) state's background-image is inlined because * non-used CSS selectors are usually ignored; popular browsers don't download * their 'url' references. * The active autocomplete state's background-image is inlined because non-used * CSS selectors are usually ignored; popular browsers don't download their * 'url' references. * If these selectors become active, the browser needs some time for painting * previously ignored remote asset: it should get it from server, parse it and * repaint the background of autocomplete field. With the inlined background we * can prevent an additional timeout caused by a new request/response pair. * Besides this, the autocompleting event itself may easily finish before the * Besides this, the autocomplete event itself may easily finish before the * missing asset gets downloaded/parsed/painted, and the missing instant visual * feedback would be a usability/accessibility issue as well. */ Loading Loading @@ -50,7 +52,7 @@ } /** * Autocomplete wrapper for autocompleting message. * Autocomplete wrapper for autocomplete message. */ .claro-autocomplete { position: relative; Loading core/themes/claro/js/autocomplete.js +2 −0 Original line number Diff line number Diff line Loading @@ -3,6 +3,8 @@ * Claro's enhancement for autocomplete form element. */ // cspell:ignore is-autocompleting (($, Drupal, once) => { Drupal.behaviors.claroAutoCompete = { attach(context) { Loading core/misc/autocomplete.js +2 −2 File changed.Contains only whitespace changes. Show changes Loading
core/misc/cspell/dictionary.txt +0 −3 Original line number Diff line number Diff line Loading @@ -20,9 +20,6 @@ arrowstop arrowthick arrowthickstop assertable autocompletefocus autocompleteselect autocompleting autoconfiguration autoconfigure autoconfigured Loading
core/tests/Drupal/Nightwatch/Tests/claroAutocompleteTest.js +4 −1 Original line number Diff line number Diff line // cspell:ignore is-autocompleting module.exports = { '@tags': ['core'], Loading Loading @@ -28,7 +30,8 @@ module.exports = { .waitForElementVisible('body', 1000); // Tests that entering a character from the // data-autocomplete-first-character-blacklist doesn't start autocompleting. // data-autocomplete-first-character-blacklist doesn't start the // autocomplete process. browser .setValue('[name="autocomplete_4"]', '/') .pause(1000) Loading
core/themes/claro/css/components/autocomplete-loading.module.css +7 −5 Original line number Diff line number Diff line Loading @@ -12,6 +12,8 @@ * @see autocomplete.js */ /* cspell:ignore is-autocompleting */ /** * Since the autocomplete library is attached conditionally and not globally, * we can be 99% sure that the default icon will be used. Loading @@ -19,14 +21,14 @@ * autocomplete input's background — until are sure that it will be pushed by * the server with HTTP/2. * * The autocompleting (active) state's background-image is inlined because * non-used CSS selectors are usually ignored; popular browsers don't download * their 'url' references. * The active autocomplete state's background-image is inlined because non-used * CSS selectors are usually ignored; popular browsers don't download their * 'url' references. * If these selectors become active, the browser needs some time for painting * previously ignored remote asset: it should get it from server, parse it and * repaint the background of autocomplete field. With the inlined background we * can prevent an additional timeout caused by a new request/response pair. * Besides this, the autocompleting event itself may easily finish before the * Besides this, the autocomplete event itself may easily finish before the * missing asset gets downloaded/parsed/painted, and the missing instant visual * feedback would be a usability/accessibility issue as well. */ Loading @@ -53,7 +55,7 @@ } /** * Autocomplete wrapper for autocompleting message. * Autocomplete wrapper for autocomplete message. */ .claro-autocomplete { Loading
core/themes/claro/css/components/autocomplete-loading.module.pcss.css +7 −5 Original line number Diff line number Diff line Loading @@ -5,6 +5,8 @@ * @see autocomplete.js */ /* cspell:ignore is-autocompleting */ /** * Since the autocomplete library is attached conditionally and not globally, * we can be 99% sure that the default icon will be used. Loading @@ -12,14 +14,14 @@ * autocomplete input's background — until are sure that it will be pushed by * the server with HTTP/2. * * The autocompleting (active) state's background-image is inlined because * non-used CSS selectors are usually ignored; popular browsers don't download * their 'url' references. * The active autocomplete state's background-image is inlined because non-used * CSS selectors are usually ignored; popular browsers don't download their * 'url' references. * If these selectors become active, the browser needs some time for painting * previously ignored remote asset: it should get it from server, parse it and * repaint the background of autocomplete field. With the inlined background we * can prevent an additional timeout caused by a new request/response pair. * Besides this, the autocompleting event itself may easily finish before the * Besides this, the autocomplete event itself may easily finish before the * missing asset gets downloaded/parsed/painted, and the missing instant visual * feedback would be a usability/accessibility issue as well. */ Loading Loading @@ -50,7 +52,7 @@ } /** * Autocomplete wrapper for autocompleting message. * Autocomplete wrapper for autocomplete message. */ .claro-autocomplete { position: relative; Loading
core/themes/claro/js/autocomplete.js +2 −0 Original line number Diff line number Diff line Loading @@ -3,6 +3,8 @@ * Claro's enhancement for autocomplete form element. */ // cspell:ignore is-autocompleting (($, Drupal, once) => { Drupal.behaviors.claroAutoCompete = { attach(context) { Loading
