HTML select element change event: Error: getUserNameAndPasswordFields: input element required
Categories
(Toolkit :: Password Manager, defect, P4)
Tracking
()
People
(Reporter: feedbro.reader, Unassigned)
Details
(Keywords: regression)
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0
Steps to reproduce:
- Install Feedbro WebExtension: https://addons.mozilla.org/firefox/addon/feedbroreader/
- Open Feedbro reader (click the Feedbro WebExtension icon and select "Open Feed Reader")
- Click "Add folder" icon - use the name "foo" (without double quotes) - OK
- Click "Add feed" icon - (Feed URL: example.com, Title: yeah, Folder: foo) - press Save
- Click "Add feed" icon - change the Folder select value from "foo" to "Root"
Actual results:
-> in the background page Console there's an error right after you change the folder from "foo" to "Root":
Error: getUserNameAndPasswordFields: input element required
getUserNameAndPasswordFields resource://gre/modules/LoginManagerChild.jsm:2510
handleEvent resource://gre/modules/LoginManagerChild.jsm:257
receiveMessage resource://gre/actors/SelectChild.jsm:268
receiveMessage resource://gre/actors/SelectChild.jsm:465
Expected results:
There should be no such error. Feedbro does not have an event listener in the folder element so this is entirely something incorrectly generated by Firefox.
Here's a quite minimal Test Case as a standalone WebExtension that can be used to reproduce this bug.
Comment 2•4 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
Comment 3•4 years ago
|
||
Since the error is from toolkit/components/passwordmgr/
:
Updated•4 years ago
|
Comment 4•4 years ago
|
||
Thanks for filing @Voltron! I was able to reproduce on Firefox 78.0.2 (release), but not on Nightly or when building from Central (I tested each both with FeedBro and your minimal example). So whatever the bug was, it seems likely that it's been fixed.
If this has a major impact on your workflow we might consider working out what the fix was and uplifting it to an earlier version (since 80 will take a while to be released), but I didn't notice any user facing problem here. If I'm wrong please reopen the ticket, describe the impact, and we can prioritize the work.
Thanks again!
Updated•4 years ago
|
Description
•