Closed
Bug 1525207
Opened 5 years ago
Closed 5 years ago
Clicking on a disabled input does not trigger an event on the document in Gecko, but does in Chrome.
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
DUPLICATE
of bug 1220048
| Tracking | Status | |
|---|---|---|
| firefox67 | --- | affected |
People
(Reporter: twisniewski, Unassigned)
References
Details
(Whiteboard: [webcompat])
Attachments
(1 file)
|
274 bytes,
text/html
|
Details |
In the attached test-case, clicking on the disabled input in Chrome will still fire an event targetting the input, which the handler will use to remove the disabled attribute. This works in Chrome, but not in Firefox, which does not fire the click event.
This is causing an interop issue on Yahoo Mail, where users cannot select their closest city and timezone in their profile (as per https://webcompat.com/issues/24628).
Flags: webcompat?
|
||
Comment 1•5 years ago
|
||
Seems duplication of Bug 1220048
|
||
Updated•5 years ago
|
Component: DOM: Events → DOM: Core & HTML
|
|
||
Comment 2•5 years ago
|
||
But yes, a dup. And unfortunately undefined behavior :/
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•