Closed
Bug 1501774
Opened 6 years ago
Closed 6 years ago
click event not firing when element gets `will-change: transform` (frame reconstruct) between mousedown and mouseup
Categories
(Core :: Layout, defect, P3)
Tracking
()
RESOLVED
DUPLICATE
of bug 1497524
People
(Reporter: myfrom.13th, Unassigned)
References
Details
(Keywords: parity-chrome, parity-edge)
Attachments
(1 file)
223 bytes,
text/html
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.67 Safari/537.36 Steps to reproduce: This bug appears to be related to specific markups and styles combinations. I'm able to reproduce with an element that is absolutely positioned within its parent and has a ::before pseudo-element with a letter as content. I know it also happens with web component paper-input (https://www.webcomponents.org/element/@polymer/paper-input) In those cases, if you add two listeners to the parent of aforementioned element: 1) `mousedown` in which you add `will-change: transform;` to parent and 2) `mouseup` in which you remove the style from the element, after clicking in my case on the ::before pseudo-element's content (letter "X" in demo), the click event for the element (not parent, element) will not fire; in paper-input case, clicking the input field will not focus it. Clicking on padding, margin or border of the element, or outside ::before does work properly. Demo: https://jsfiddle.net/myfrom/e5Lvukqn/3/ Sorry for so much complication but I wasn't able to reproduce it with simpler markup/styles. Actual results: Click event wasn't fired Expected results: Click event is fired just as with clicks outside ::before but still inside the element
Updated•6 years ago
|
Component: Untriaged → DOM: Events
Product: Firefox → Core
Updated•6 years ago
|
Status: UNCONFIRMED → NEW
status-firefox63:
--- → wontfix
status-firefox64:
--- → wontfix
status-firefox65:
--- → affected
status-firefox-esr60:
--- → wontfix
Ever confirmed: true
Keywords: parity-chrome,
parity-edge
Updated•6 years ago
|
Blocks: will-change
Version: 62 Branch → 36 Branch
Updated•6 years ago
|
Component: DOM: Events → Layout
Comment 1•6 years ago
|
||
I wonder if bug 1089326 actually fixes this.
Updated•6 years ago
|
Priority: -- → P3
Comment 2•6 years ago
|
||
Adding "will-change: transform" to an element with abs-pos (or fixed-pos) children would trigger reframe on it, which may mean that the pseudo-element is reconstructed (IIRC?). Not sure what's the best way to handle this case, nor whether it's Layout or DOM should be responsible...
Summary: click event not firing when element gets `will-change: transform` between mousedown and mouseup → click event not firing when element gets `will-change: transform` (frame reconstruct) between mousedown and mouseup
Comment 4•6 years ago
|
||
Should log `click` when clicking on the 'X', but that's not the case.
Updated•6 years ago
|
Attachment #9022458 -
Attachment mime type: text/plain → text/html
You need to log in
before you can comment on or make changes to this bug.
Description
•