-
Notifications
You must be signed in to change notification settings - Fork 47k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IE 11 and Edge no longer prompt to remember password on controlled form #7328
Comments
This issue is caused by this commit 4338c8d#diff-5a2abece6f8c2495d8242daa40245434L156 value: MUST_USE_PROPERTY | HAS_SIDE_EFFECTS, to value: 0, It looks like the key is the I see that |
Any progress on this bug? The PR to fix it seems to be hanging around for a while and has not yet been merged. |
is there any workaround for this issue? |
This commit replaces the method of synchronizing an input's value attribute from using setAttribute to assigning defaultValue. This has several benefits: - Fixes issue where IE10+ and Edge password icon disappears (#7328) - Fixes issue where toggling input types hides display value on dates in Safari (unreported) - Removes mutationMethod behaviors from DOMPropertyOperations
This commit replaces the method of synchronizing an input's value attribute from using setAttribute to assigning defaultValue. This has several benefits: - Fixes issue where IE10+ and Edge password icon disappears (#7328) - Fixes issue where toggling input types hides display value on dates in Safari (unreported) - Removes mutationMethod behaviors from DOMPropertyOperations
This commit replaces the method of synchronizing an input's value attribute from using setAttribute to assigning defaultValue. This has several benefits: - Fixes issue where IE10+ and Edge password icon disappears (#7328) - Fixes issue where toggling input types hides display value on dates in Safari (unreported) - Removes mutationMethod behaviors from DOMPropertyOperations
This commit replaces the method of synchronizing an input's value attribute from using setAttribute to assigning defaultValue. This has several benefits: - Fixes issue where IE10+ and Edge password icon disappears (#7328) - Fixes issue where toggling input types hides display value on dates in Safari (unreported) - Removes mutationMethod behaviors from DOMPropertyOperations
* Use defaultValue instead of setAttribute('value') This commit replaces the method of synchronizing an input's value attribute from using setAttribute to assigning defaultValue. This has several benefits: - Fixes issue where IE10+ and Edge password icon disappears (#7328) - Fixes issue where toggling input types hides display value on dates in Safari (unreported) - Removes mutationMethod behaviors from DOMPropertyOperations * initialValue in Input wrapperState is always a string * The value property is assigned before the value attribute. Fix related tests. * Remove initial value tests in ReactDOMInput I added these tests after removing the `value` mutation method. However they do not add any additional value over existing tests. * Improve clarity of value checks in ReactDOMInput.postMountWrapper * Remove value and defaultValue from InputWithWrapperState type They are already included in the type definition for HTMLInputElement * Inline stringification of value in ReactDOMInput Avoids eagier stringification and makes usage more consistent. * Use consistent value/defaultValue presence in postMountHook Other methods in ReactDOMInput check for null instead of hasOwnProperty. * Add missing semicolon * Remove unused value argument in ReactDOMInput test * Address cases where a value switches to undefined When a controlled input value switches to undefined, it reverts back to the initial state of the controlled input. We didn't have test coverage for this case, so I've added two describe blocks to cover both null and undefined.
For me this bug is still present in 16.2.0. |
I'm still having this issue with both IE and Edge: Works with 15.1.0: https://codesandbox.io/s/lpvz0zy9wq In order to test this effectively, you have to follow a few steps: Using Edge, go to Settings >> View Advanced Settings, under Privacy and ServicesSteps to reproduce when IT WORKS (15.1.0)
Steps to reproduce when IT DOESN'T WORK (15.2.0, 15.6.2, 16.3.1)
|
Is there a work around for this issue? I tried updating react to 16.4.1, didnt fix the issue for me |
@abbybhat Oh no! Can you send over a reproduction case? |
@nhunzaker The reproduction case was already provided by @luisrudge above. I updated it to 16.4.1: Password prompt in IE 11 showing with 15.2.0: Password prompt in IE 11 not showing with 16.4.1: |
Seems like this wasn't fixed after all. We need to figure out why we thought this was fixed in #11534. |
There might have been a mismatch with the originally referenced issue in #8266, which was focused on the password reveal icon. |
I believe this works in Edge, but not IE11. I am still confirming IE11, but I need to step away for a bit. Here is what I found: I setup a fixture for this, and I'm not having an issue getting the "remember password" flow". I have made a test fixture for this case here: http://react-password-remember.surge.sh/password-inputs And the associated diff: This holds true for master, React 16.4, and React 16.3. Additionally, I am not having an issue triggering the password flow in @luisrudge's example: And I can also see the passwords saved in the manager: |
Looks like we already came to this conclusion in #12749. This does not work in IE11, and was being tracked to that issue. |
Do you want to request a feature or report a bug?
Bug (regression) IE/Edge
What is the current behavior?
On React > v15.2.0, Edge and IE11 do not prompt the user to save the password for the form
Steps to reproduce
With react 15.1.0:
https://jsfiddle.net/69z2wepo/49876/
With React 15.2.0:
https://jsfiddle.net/69z2wepo/49877/
What is the expected behavior?
The browser prompts the user to save their password for the form
Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
React > 15.2.0. It worked in React 15.2.0
IE 11, Edge
The text was updated successfully, but these errors were encountered: