Re: [fxtf-drafts] [geometry] return DOMPoint or DOMPointReadOnly accordingly, from matrixTransform method?

Although I agree this would be a bit more idiomatic for JavaScript-created classes, and friendly toward author-created subclasses, it's pretty unprecedented for platform-implemented classes. I imagine it'd be tricky to implement given how most Web IDL bindings systems work, and not worth the churn.

So, I'd suggest not changing this, especially given that we have no reports of actual problems caused by this, and instead only theoretical ones. (I interpret "Just seems like..." differently from "I was trying to build an app that did X...")

GitHub Notification of comment by domenic
Please view or discuss this issue at using your GitHub account

Received on Monday, 16 April 2018 14:33:25 UTC