Consider using isFocusable instead of isVisible when determing whether a field is eligible for address and credit card autofill
Categories
(Toolkit :: Form Autofill, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox120 | --- | fixed |
People
(Reporter: dimi, Assigned: janika)
References
(Regressed 1 open bug)
Details
(Whiteboard: [fxcm-cc-new-geo])
Attachments
(1 file)
We have seen in some cases, a field is not visible but should still be autofilled (state field in Bug 1835852, expiry month/year in Bug 1845321).
Maybe we should use "isFocusable" instead of "isVisible"? If this is the right thing to do, can we use elementIsFocusable
[1]?
Reporter | ||
Updated•2 years ago
|
Updated•2 years ago
|
Reporter | ||
Comment 1•1 years ago
|
||
Maybe we should use "isFocusable" instead of "isVisible"? If this is the right thing to do, can we use
elementIsFocusable
[1]?
@edgar, we had chatted about this during the AllHands, but could you help confirm again that elementIsFocusable
is the right API to use for our use cases, thank you!
Comment 2•1 years ago
•
|
||
Yes, you can use elementIsFocusable
with flag=0 to check whether a element is focusable, i.e. does the focus can be moved to a element either by mouse clicking or calling element.focus()
. And if I read code correctly, you can also use FLAG_BYMOUSE to check whether a element is focusable by mouse clicking.
Assignee | ||
Comment 3•1 year ago
|
||
Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Comment 5•1 year ago
|
||
Backed out for causing bc failures on browser_HomeDepot.js
Assignee | ||
Comment 6•1 year ago
|
||
Hi @Norisz, thank you for pinging me! I checked the failures and updated and fixed the patch (see try push).
![]() |
||
Comment 8•1 year ago
|
||
bugherder |
Description
•