W3C home > Mailing lists > Public > public-css-archive@w3.org > January 2017

[csswg-drafts] [geometry] Why does DOMQuad have readonly mutable points?

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Wed, 11 Jan 2017 20:31:45 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-200199526-1484166704-sysbot+gh@w3.org>
tabatkins has just created a new issue for 

== [geometry] Why does DOMQuad have readonly mutable points? ==
DOMQuad's p1/p2/p3/p4 attributes are readonly, which means there's no 
setter.  However, the points themselves are DOMPoint, not 
DOMPointReadonly, so they're mutable.  This seems like a bizarre 
amalgam?  You *can* mutate the quad's points, you just can't reassign 

We should either make DOMQuad fully mutable (removing the readonly 
annotations), or switch them to DOMPointReadonly, rename DOMQuad to 
DOMQuadReadonly, and if necessary, add a fully mutable DOMQuad as 

Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/888 using your GitHub 
Received on Wednesday, 11 January 2017 20:31:53 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:07 UTC