Summary: | TouchEvent objects shouldn't contain co-ordinates | ||
---|---|---|---|
Product: | WebKit | Reporter: | Tim Dresser <tdresser> |
Component: | UI Events | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW --- | ||
Severity: | Normal | CC: | bdakin, benjamin, cdumez, dino, rbyers, sam, simon.fraser |
Priority: | P2 | ||
Version: | Safari 9 | ||
Hardware: | iPhone / iPad | ||
OS: | Unspecified |
Description
Tim Dresser
2016-05-02 10:12:07 PDT
I assume this is because pageX, pageY, layerX, layerY are on UIEvent.idl in WebKit (https://github.com/WebKit/webkit/blob/66e68cd8d7bf4ea1cf52f31ed9cb242f83ea5b57/Source/WebCore/dom/UIEvent.idl). Chromium has never (AFAIK) reported non-zero values for TouchEvent.pageX/pageY/layerX/layerY, and we removed those properties from TouchEvent completely about a year ago (https://bugs.chromium.org/p/chromium/issues/detail?id=50327). We're not aware of a single website which is depending on seeing these properties on TouchEvents, so it's likely highly web compatible to move them from UIEvent to MouseEvent as we did in blink. See https://bugs.webkit.org/show_bug.cgi?id=147740#c11 for discussion of the interaction between these non-standard properties and the standard constructor syntax. |