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
Not really a bug, but unexpected behaviour none the less:
I just found out that the forms example (example #3) works incorrectly in combination with a chrome extension of my password manager, 1password.
It seems that 1password interferes with typing text in any two inputs of which the second is of the password type. The resulting behaviour can be a runtime error: "Cannot read property 'replaceData' of undefined" or the value of the field remaining at 1 character long (the last character that was typed).
Strange enough the extension doesn't seem to have a 'disable for current webpage' function, so uninstalling the extension or using an incognito window seem to be the only viable solutions.
My environment:
MacOS High Sierra (10.13.3)
Chrome 69.0.3497.100
1Password 1.12.2
Using elm reactor to run the examples in this repository, issue found in example #3, also reproduced locally in example #2 for investigation by adding a second input field of type password.
The text was updated successfully, but these errors were encountered:
Not really a bug, but unexpected behaviour none the less:
I just found out that the forms example (example #3) works incorrectly in combination with a chrome extension of my password manager, 1password.
It seems that 1password interferes with typing text in any two inputs of which the second is of the password type. The resulting behaviour can be a runtime error: "Cannot read property 'replaceData' of undefined" or the value of the field remaining at 1 character long (the last character that was typed).
Strange enough the extension doesn't seem to have a 'disable for current webpage' function, so uninstalling the extension or using an incognito window seem to be the only viable solutions.
My environment:
MacOS High Sierra (10.13.3)
Chrome 69.0.3497.100
1Password 1.12.2
Using elm reactor to run the examples in this repository, issue found in example #3, also reproduced locally in example #2 for investigation by adding a second input field of type password.
The text was updated successfully, but these errors were encountered: