NEW 82274
[Refactoring] WebKitPoint should be named DOMPoint, and should stay under dom/ 
https://bugs.webkit.org/show_bug.cgi?id=82274
Summary [Refactoring] WebKitPoint should be named DOMPoint, and should stay under dom/
Hajime Morrita
Reported 2012-03-26 17:54:02 PDT
Similar to Bug 82273. It should have a vendor-prefix-free name and an appropriate home.
Attachments
Add attachment proposed patch, testcase, etc.
Simon Pieters (:zcorpan)
Comment 1 2017-05-19 01:34:45 PDT
Chromium successfully removed WebKitPoint a few years ago. See intent thread: https://groups.google.com/a/chromium.org/d/msg/blink-dev/pIbpN_8Lqpg/tp9f71GsslIJ Gecko does not have WebKitPoint. EdgeHTML still does. The Geometry APIs specification specifies a DOMPoint interface instead, and does not alias WebKitPoint. The hope is to converge on not exposing WebKitPoint. Also see https://github.com/w3c/fxtf-drafts/issues/163 https://github.com/w3c/fxtf-drafts/pull/166 https://github.com/w3c/web-platform-tests/pull/5975
Ahmad Saleem
Comment 2 2023-11-11 16:34:13 PST
For reference (Blink Commit) - https://src.chromium.org/viewvc/blink?view=revision&revision=181252
Note You need to log in before you can comment on or make changes to this bug.