Re: [fxtf-drafts] [geometry] Why does DOMQuad have readonly mutable points?

Having readonly properties with mutable objects is quite common. 

For example
https://fetch.spec.whatwg.org/#request `headers`
https://html.spec.whatwg.org/#dom-document-head
https://html.spec.whatwg.org/#dom-dataset
https://dom.spec.whatwg.org/#dom-element-classlist
https://dom.spec.whatwg.org/#dom-element-attributes
https://drafts.csswg.org/css-font-loading/#dom-fontfacesource-fonts

...etc. So I think it doesn't follow that just because the object is mutable, the attribute must also be writable.

What is the use case for assigning the points in a `DOMQuad`?

I can think of a downside to changing them to be writable: code that assigns new points all the time (e.g. every animation frame) instead of assigning the primitive values on the points themselves would create a lot of garbage.

-- 
GitHub Notification of comment by zcorpan
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/124#issuecomment-290645482 using your GitHub account

Received on Friday, 31 March 2017 08:06:30 UTC