- From: Dirk Schulze via GitHub <sysbot+gh@w3.org>
- Date: Thu, 12 Apr 2018 07:53:42 +0000
- To: public-svg-issues@w3.org
I really like the proposal from @domenic to use `DOMPointInit` instead of `DOMPointReadOnly` (and I think it is less confusing as well). One could bring up the argument that it might be easier for implementations to comply to `DOMPointReadOnly` than to the `DOMPointInit` usage. Because of the mapping of `SVGPoint` implementations don't really need to do much. However, `SVGPoint` maps to `DOMPoint` and not `DOMPointReadOnly`. So changing `DOMPoint` to `DOMPointReadOnly` already requires changes to implementations. I would propose to go either one of the following 2 paths: 1. If we are concerned that implementations are not updating their implementations to `DOMPointInit` in time to get SVG2 to REC, we shouldn't do any change to the current interfaces for level 2 at all (not even use `DOMPointReadOnly`) and update the spec in an errata or another revision when we see implementations adapt. 2. Go with `DOMPointInit` for level 2 already. I'd prefer 2 but maybe we should get implementers buy in first. -- GitHub Notification of comment by dirkschulze Please view or discuss this issue at https://github.com/w3c/svgwg/issues/389#issuecomment-380712117 using your GitHub account
Received on Thursday, 12 April 2018 07:53:45 UTC