You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 5, 2024. It is now read-only.
When using the demo section for input errors, the first time I focus on an element, it inherits the "normal" ink color, which is incorrect. The spec indicates that when an error appears, both the label and underline are activated with red. So when an error appears, the input would never use the default ink unless the error was resolved.
In the angular demo, it's only after focusing on an input with error twice does the expected behavior occur.
When using the demo section for input errors, the first time I focus on an element, it inherits the "normal" ink color, which is incorrect. The spec indicates that when an error appears, both the label and underline are activated with red. So when an error appears, the input would never use the default ink unless the error was resolved.
In the angular demo, it's only after focusing on an input with error twice does the expected behavior occur.