Use arrow keys to highlight a previously entered value, such as 'TestOne'
Press Enter
Tab to focus 'Middle name'
Use arrow keys to highlight a previously entered value, such as 'TestOne'
Press Enter
Tab to focus 'Legal last name'
Use arrow keys to highlight a previously entered value, such as 'TestOne'
Press enter
View those three input background colors to be blue
QUESTION: Why are we seeing two different background colors depending on the method used to enter the same text?
Reproducing the error on the docsite
None
Expected behavior
Background color of auro-input fields would be the same color when valid, regardless of what method the user used to enter the text.
method examples: 1. clicking into input and typing new text, 2. tabbing into input, using arrow keys to navigate to a previously entered value, pressing enter to select
What browsers are you seeing the problem on?
Chrome
Additional context
it didn't seem to matter whether the input was required or not required, either way the questionable behavior is found
if this depends on the browser having previously used values saved, and that causes difficulty, please reach out to me and I can show a screen share demo
currently unable to repro on Auro docsite, perhaps because there's not a set of inputs together within one form (they are stand alone examples of different use cases)
Please verify the version of auro-input you have installed
2.13.2
Please describe the bug
There are two different background colors of the auro-input box to view:
Background is WHITE
Background is BLUE
QUESTION: Why are we seeing two different background colors depending on the method used to enter the same text?
Reproducing the error on the docsite
None
Expected behavior
Background color of auro-input fields would be the same color when valid, regardless of what method the user used to enter the text. method examples: 1. clicking into input and typing new text, 2. tabbing into input, using arrow keys to navigate to a previously entered value, pressing enter to select
What browsers are you seeing the problem on?
Chrome
Additional context