[CSS] Cannot overwrite pointer-events for <button>'s child elements
Categories
(Core :: DOM: Events, defect)
Tracking
()
People
(Reporter: ian.html, Assigned: smaug)
References
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0
Steps to reproduce:
Set "pointer-events: none" to a <button>, and then set "pointer-events: auto" on its child element.
Actual results:
The child element's pointer-events is not being overwrote as "auto".
Expected results:
The child element's pointer-events should have been overwritten as "auto".
Comment 1•5 years ago
|
||
Hi Ian Yang,
Please provide a simplified testcase so we can check this issue out.
(In reply to Timea Babos from comment #1)
Hi Ian Yang,
Please provide a simplified testcase so we can check this issue out.
Here is a simplified testcase: https://jsfiddle.net/ujpn9v0y/5/
Comment 3•5 years ago
|
||
Thanks for the testcase Ian!
Unfortunately, I still do not understand exactly what is the issue. If you could elaborate a bit or share a recording of how it should be and how it is currently that would be appreciated.
(In reply to Timea Babos from comment #3)
Thanks for the testcase Ian!
Unfortunately, I still do not understand exactly what is the issue. If you could elaborate a bit or share a recording of how it should be and how it is currently that would be appreciated.
Although the button has "pointer-events: none" and is unclickable, its child element which has "pointer-events: auto" should be clickable.
The issue is that its child element is being unclickable, too.
Comment 5•5 years ago
|
||
Thank again Ian, that helped :)
Reproduced the issue on Firefox Release 65.0 - I believe you see the issue on this Firefox version too.
Can't reproduce it on latest Beta nor Nightly, mozregression pointed out that this Bug 1512259 patch fixed it.
Can you also confirm if it is fixed on Beta or Nightly?
(In reply to Timea Babos from comment #5)
Thank again Ian, that helped :)
Reproduced the issue on Firefox Release 65.0 - I believe you see the issue on this Firefox version too.
Can't reproduce it on latest Beta nor Nightly, mozregression pointed out that this Bug 1512259 patch fixed it.Can you also confirm if it is fixed on Beta or Nightly?
I just tried the Beta and couldn't reproduce the issue. It appears that the Beta fixed the issue.
Comment 7•5 years ago
|
||
Glad to hear that. Closing this issue as Resolved: WorksForMe with the note that this will be fixed in the upcoming Release 66 version as it has been fixed in Beta and Nightly.
Assignee | ||
Comment 8•5 years ago
|
||
It should have been bug 1089326 which fixed this.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Description
•