[Webkit-unassigned] [Bug 133916] Implement DOMPoint/DOMPointReadOnly

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Oct 12 16:43:26 PDT 2016


--- Comment #21 from Dirk Schulze <krit at webkit.org> ---
(In reply to comment #20)
> I talked to Geoff about built-ins. Using built-ins would be advantageous if
> we think most property access on these classes is going to come from script.
> However, if they are mainly used as parameters to call into native code, or
> if used largely from native code, then they would be better as native code.
> I don't have a feel for how DOMPoint etc are likely to be used in the wild.
> My guess is that most devs currently just use [x, y] or { x:, y: }, and
> would get little win from using DOMPoint.
> DOMRect and DOMRectInit are certainly going to be used as arguments to
> IntersectionObserver, but maybe also stand-alone in script?
> DOMMatrix is the one class that is more likely to be used extensively from
> script, so I think it might get the most win from being a built-in.
> Of course, we can always change something to being a built-in once we have
> usage experience from the wild.

DOMPoint and DOMRect are for DOM to JS communication. So built-ins might be less useful. I agree for DOMMatrix though. Especially with WebGL and WebVR as future main consumer.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20161012/b45b3edb/attachment.html>

More information about the webkit-unassigned mailing list