Issue #3418999 by quietone: Correct spelling of autocomplete type words

merge-requests/8631/head
Alex Pott 2024-07-02 10:21:04 +01:00
parent c3383f44d5
commit 57325ce447
No known key found for this signature in database
GPG Key ID: BDA67E7EE836E5CE
6 changed files with 22 additions and 16 deletions

View File

@ -20,9 +20,6 @@ arrowstop
arrowthick arrowthick
arrowthickstop arrowthickstop
assertable assertable
autocompletefocus
autocompleteselect
autocompleting
autoconfiguration autoconfiguration
autoconfigured autoconfigured
autocreate autocreate

View File

@ -1,3 +1,5 @@
// cspell:ignore is-autocompleting
module.exports = { module.exports = {
'@tags': ['core'], '@tags': ['core'],
@ -28,7 +30,8 @@ module.exports = {
.waitForElementVisible('body', 1000); .waitForElementVisible('body', 1000);
// Tests that entering a character from the // 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 browser
.setValue('[name="autocomplete_4"]', '/') .setValue('[name="autocomplete_4"]', '/')
.pause(1000) .pause(1000)

View File

@ -12,6 +12,8 @@
* @see autocomplete.js * @see autocomplete.js
*/ */
/* cspell:ignore is-autocompleting */
/** /**
* Since the autocomplete library is attached conditionally and not globally, * Since the autocomplete library is attached conditionally and not globally,
* we can be 99% sure that the default icon will be used. * we can be 99% sure that the default icon will be used.
@ -19,14 +21,14 @@
* autocomplete input's background until are sure that it will be pushed by * autocomplete input's background until are sure that it will be pushed by
* the server with HTTP/2. * the server with HTTP/2.
* *
* The autocompleting (active) state's background-image is inlined because * The active autocomplete state's background-image is inlined because non-used
* non-used CSS selectors are usually ignored; popular browsers don't download * CSS selectors are usually ignored; popular browsers don't download their
* their 'url' references. * 'url' references.
* If these selectors become active, the browser needs some time for painting * 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 * previously ignored remote asset: it should get it from server, parse it and
* repaint the background of autocomplete field. With the inlined background we * repaint the background of autocomplete field. With the inlined background we
* can prevent an additional timeout caused by a new request/response pair. * 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 * missing asset gets downloaded/parsed/painted, and the missing instant visual
* feedback would be a usability/accessibility issue as well. * feedback would be a usability/accessibility issue as well.
*/ */
@ -53,7 +55,7 @@
} }
/** /**
* Autocomplete wrapper for autocompleting message. * Autocomplete wrapper for autocomplete message.
*/ */
.claro-autocomplete { .claro-autocomplete {

View File

@ -5,6 +5,8 @@
* @see autocomplete.js * @see autocomplete.js
*/ */
/* cspell:ignore is-autocompleting */
/** /**
* Since the autocomplete library is attached conditionally and not globally, * Since the autocomplete library is attached conditionally and not globally,
* we can be 99% sure that the default icon will be used. * we can be 99% sure that the default icon will be used.
@ -12,14 +14,14 @@
* autocomplete input's background until are sure that it will be pushed by * autocomplete input's background until are sure that it will be pushed by
* the server with HTTP/2. * the server with HTTP/2.
* *
* The autocompleting (active) state's background-image is inlined because * The active autocomplete state's background-image is inlined because non-used
* non-used CSS selectors are usually ignored; popular browsers don't download * CSS selectors are usually ignored; popular browsers don't download their
* their 'url' references. * 'url' references.
* If these selectors become active, the browser needs some time for painting * 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 * previously ignored remote asset: it should get it from server, parse it and
* repaint the background of autocomplete field. With the inlined background we * repaint the background of autocomplete field. With the inlined background we
* can prevent an additional timeout caused by a new request/response pair. * 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 * missing asset gets downloaded/parsed/painted, and the missing instant visual
* feedback would be a usability/accessibility issue as well. * feedback would be a usability/accessibility issue as well.
*/ */
@ -50,7 +52,7 @@
} }
/** /**
* Autocomplete wrapper for autocompleting message. * Autocomplete wrapper for autocomplete message.
*/ */
.claro-autocomplete { .claro-autocomplete {
position: relative; position: relative;

View File

@ -3,6 +3,8 @@
* Claro's enhancement for autocomplete form element. * Claro's enhancement for autocomplete form element.
*/ */
// cspell:ignore is-autocompleting
(($, Drupal, once) => { (($, Drupal, once) => {
Drupal.behaviors.claroAutoCompete = { Drupal.behaviors.claroAutoCompete = {
attach(context) { attach(context) {