- From: Domenic Denicola via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 Mar 2017 00:43:55 +0000
- To: public-media-capture-logs@w3.org
Because Point2D is only used in dictionaries, the distinction is very slight. If DOMPointInit was used (not DOMPoint; that would be bad) then inputs like `{ x: 1, y: 2, get z() { throw new Error("z"); } }` would throw when being converted to a DOMPointInit, even though the plan is to ignore the z (and w). Whereas in the current spec, given such input the z (and w) are ignored, so it would not throw. So I think Point2D as used here is the right choice.
However, if the points were ever exposed externally (e.g. as attribute values or method return values), then DOMPoint might be a better choice, for platform harmony. I can't find any such instances in the spec right now.
--
GitHub Notification of comment by domenic
Please view or discuss this issue at https://github.com/w3c/mediacapture-image/issues/145#issuecomment-289628320 using your GitHub account
Received on Tuesday, 28 March 2017 00:44:02 UTC