Use HTMLInputElement.hasBeenTypePassword instead of checking `type` manually
Categories
(Toolkit :: Password Manager, enhancement, P2)
Tracking
()
People
(Reporter: MattN, Assigned: MattN)
References
(Depends on 1 open bug)
Details
(Whiteboard: [passwords:tech-debt] [passwords:fill-ui] [passwords:generation] [passwords:capture-UI])
Attachments
(4 files)
In order to proper handle password fields where the user is able to toggle @type to reveal the password, we should use the ChromeOnly HTMLInputElement.hasBeenTypePassword
API to determine whether a field is a "password" field.
We may want to be careful about filling into an unmask password field but I'm not sure there is a good solution to that since we can't be sure the user still has a visible toggle.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 3•5 years ago
|
||
This affects https://accounts.google.com (bug 1595414) and other popular sites (causing us not to save or autocomplete) so I think we should address this in the near-term.
Assignee | ||
Comment 4•5 years ago
|
||
spun-off-to-another-bug |
We may want to also update the DOMInputPasswordAdded
event code to use this property too.
Assignee | ||
Comment 6•5 years ago
|
||
Assignee | ||
Comment 7•5 years ago
|
||
I've rebased some old patches I had for this.
Assignee | ||
Comment 8•5 years ago
|
||
(In reply to Matthew N. [:MattN] (PM me if request are blocking you) from comment #0)
We may want to be careful about filling into an unmask password field but I'm not sure there is a good solution to that since we can't be sure the user still has a visible toggle.
I wonder if we should start by only filling into these when userTriggered
?
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 9•5 years ago
|
||
Context menu code using this.onPassword
also should change.
Assignee | ||
Comment 10•5 years ago
|
||
Assignee | ||
Comment 11•5 years ago
|
||
Depends on D68322
Assignee | ||
Comment 12•5 years ago
|
||
Depends on D68323
Assignee | ||
Comment 13•5 years ago
|
||
Depends on D68324
Comment 14•5 years ago
|
||
Comment 15•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/97360a5f3b85
https://hg.mozilla.org/mozilla-central/rev/7e4f51820b4a
https://hg.mozilla.org/mozilla-central/rev/27a026da4531
https://hg.mozilla.org/mozilla-central/rev/71e4739111e7
Comment 16•5 years ago
|
||
Hey Matt,
Verified the scenarios described in Bug 1570638 and Bug 1616523 and they are both fixed with this on Windows 10.
Is there anything else to check for this bug fix?
Assignee | ||
Comment 17•5 years ago
•
|
||
I already tested bug 1595414 so I don't think you need to again. That's probably good enough. Thanks
Comment 18•5 years ago
|
||
Thanks Matt!
Verified-Fixed on latest Nightly 76.0a1 (2020-04-01) on Windows 10, MacOS 10.13 and Ubuntu 16.04 based on Comment 16.
Description
•