W3C home > Mailing lists > Public > public-fxtf-archive@w3.org > April 2018

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

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Mon, 16 Apr 2018 18:04:19 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issue_comment.created-381696150-1523901858-sysbot+gh@w3.org>

> Having readonly properties with mutable objects is quite common.

All of those examples are of things where producing the object in question *directly* would be quite rare, so the "readonly but mutable" weirdness doesn't matter in practice.

On the other hand, the geometry objects, particularly Points, are useful on their own, and it's reasonable to create those manually via their constructor.  It's weird that you can't change the points directly, and instead have to manually mutate their properties, when you can reasonable have Point objects that you'd like to use (or are pulling off of other objects).

GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/124#issuecomment-381696150 using your GitHub account
Received on Monday, 16 April 2018 18:04:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:50:22 UTC