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

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

From: Blake Kaplan via GitHub <sysbot+gh@w3.org>
Date: Wed, 23 May 2018 22:49:12 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issue_comment.created-391524335-1527115751-sysbot+gh@w3.org>
As an additional data point: currently, Chromium computes the `DOMQuad`'s bounds in the `DOMQuad` constructor, meaning that it's possible to construct an object whose bounds are out of sync with its current state. Is this a bug in the spec or Chromium?

GitHub Notification of comment by mrbkap
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/124#issuecomment-391524335 using your GitHub account
Received on Wednesday, 23 May 2018 22:49:20 UTC

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