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
When using an ngx-ui input on a tab, there is a bug where autofill styles from the browser are applied when navigating between the tabs wrapping the inputs. When you change tabs and return the animation skips to the end and the field then has the built-in and non-overidable autofill styles.
Seems like because it is trying to autofill text into an input field the autofill-preview pseudo class is never removed. So we get stuck with the autofill styles that become visible when the animation jumps to the end.
Possible solutions:
Add a decent style for autofill, for when it is used.
Ensure the input type is included in the id to avoid collision across types.
and/or
When no id is provided, generate a collision resistant id.
setting autocomplete="off" (tricky, not cross platform)
The text was updated successfully, but these errors were encountered:
When using an ngx-ui input on a tab, there is a bug where autofill styles from the browser are applied when navigating between the tabs wrapping the inputs. When you change tabs and return the animation skips to the end and the field then has the built-in and non-overidable autofill styles.
Seems like because it is trying to autofill text into an input field the autofill-preview pseudo class is never removed. So we get stuck with the autofill styles that become visible when the animation jumps to the end.
Possible solutions:
and/or
autocomplete="off"
(tricky, not cross platform)The text was updated successfully, but these errors were encountered: