Pointer Event Handler Attributes not invoked
Reported by
jay.dunn...@jmrapidapps.net,
Dec 11 2016
|
|||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14 Steps to reproduce the problem: 1. Create an HTML document containing an element with a pointer event handler attribute (such as '<div onpointerdown="window.console.log(event.type)">Pointer Down</div>". 2. Load the document in a browser and interact with the element. What is the expected behavior? Pointer event handlers declared as attributes should be invoked. What went wrong? Pointer event handlers declared as attributes are not invoked. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 55.0.2883.87 Channel: n/a OS Version: OS X 10.11.6 Flash Version: Pointer event handlers added as properties are invoked. This defect occurs both on Windows and Mac.
,
Dec 11 2016
I obviously linked to the wrong line. Here - https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/html/HTMLElement.cpp?type=cs&q=onmouseup+file:WebKit+-file:LayoutTests+file:Element&sq=package:chromium&l=389
,
Dec 11 2016
Damn, you wrote "onpointerdown", anyway, it is around. :)
,
Dec 12 2016
,
Dec 12 2016
,
Dec 12 2016
jay.dunning@ : Thanks for the report. Could you please help providing more details for the expected result. Please find the screen cast of Mac 10.11.6 using 55.0.2883.87 upon loading and clicking on "Touch Me.."
,
Dec 12 2016
The test file has two "Touch Me" divs. The first div assigns event handlers as properties; the second div declares event handlers as attributes. Event handlers on the first work. Event handlers on the second do not.
,
Dec 12 2016
#6 - a more explicit test case it attached, try that. You should see the name of the event, as well as the ID of the target element. When you click on the first "Touch me...", you should see "pointerup, target1" in the console, for example. For the second, you should see "pointerup, target2" in the console, for example. Try both of the "Touch me..." instances and make sure you see target1 as well as target2 (with "pointerup") when you are done.
,
Dec 12 2016
Yup we are aware of this. I believe it is fixed in trunk; it will be merged into 56.
,
Dec 12 2016
,
Dec 12 2016
,
Dec 12 2016
,
Dec 12 2016
I just merged the fix to M56.
,
Dec 16 2016
I tested the latest M56 build and the problem is fixed after the patch.
,
Jan 5 2017
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by phistuck@gmail.com
, Dec 11 2016