Bug 82274
| Summary: | [Refactoring] WebKitPoint should be named DOMPoint, and should stay under dom/ | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Hajime Morrita <morrita> |
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | ahmad.saleem792, cdumez, shinyak, simon.fraser, zcorpan |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Hajime Morrita
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)
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
For reference (Blink Commit) - https://src.chromium.org/viewvc/blink?view=revision&revision=181252