Use of unknown property Ci.nsIAutoCompletePopup.TEXTVALUE_REASON_COMPLETESELECTED
Categories
(Toolkit :: Form Autofill, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox-esr78 | --- | unaffected |
firefox78 | --- | unaffected |
firefox79 | --- | unaffected |
firefox80 | --- | disabled |
firefox81 | --- | fixed |
People
(Reporter: standard8, Assigned: abr)
References
(Regression)
Details
(Keywords: regression)
I just discovered this use of an unknown property:
browser/extensions/formautofill/FormAutofillHandler.jsm
656:14 error Use of unknown property Ci.nsIAutoCompletePopup.TEXTVALUE_REASON_COMPLETESELECTED
That should probably use nsIAutoCompleteInput, however, looking at the uses of setTextValueWithReason we can probably drop the reason argument altogether as neither of the implementations actually use it.
The slight complication would be what to rename the function to as there's already a SetTextValue
in c++ which does something slightly different.
Comment 1•4 years ago
|
||
Set release status flags based on info from the regressing bug 1604807
Updated•4 years ago
|
Updated•4 years ago
|
Comment 2•4 years ago
|
||
The severity field is not set for this bug.
:MattN, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Comment 3•4 years ago
|
||
Fixed by Bug 1658086
Updated•4 years ago
|
Comment 4•4 years ago
|
||
Hi Adam,
Is there a way for us to verify this manually or manual testing is not required in this case?
Thanks.
Assignee | ||
Comment 5•4 years ago
|
||
(In reply to Alin Ilea from comment #4)
Hi Adam,
Is there a way for us to verify this manually or manual testing is not required in this case?
Thanks.
It's just a code-level change that isn't visible. If you want to verify it, you can run through a credit-card fill and then check the console to make sure that the specific error that Mark pasted into Comment 0 doesn't appear. But given that it's not visible to users, it's not clear that manual testing is warranted.
Comment 6•4 years ago
|
||
Tried to reproduce this on Firefox RC 80 but didn't see the error in the console. The same goes for the latest Nightly 81, so this is indeed something we can't verify manually as Adam said. Adding qe- flag to mark this as not actionable on QA side for verification.
Updated•4 years ago
|
Description
•