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

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 using your GitHub account

Received on Wednesday, 23 May 2018 22:49:20 UTC