- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Sat, 03 Mar 2018 01:10:31 +0000
- To: public-svg-issues@w3.org
> If the input is DOMPointReadOnly you can pass either type. What you're saying is that calling this method won't change the values of the passed in object. Ah, I see. The naming scheme doesn't make it clear that the mutable versions are a subclass of the read only versions, not the reverse—although that of course makes sense when it comes to the exposed interface: `X` is all the features of `XReadOnly`, plus mutability. So yes, this is an obvious error, then. Otherwise we'd be breaking compatibility with SVG 1. Still, it's technically a substantial change, so we should get a resolution on the next telcon. @longsonr Have you reviewed similar interfaces to see if the same error crops up anywhere else? -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/svgwg/issues/389#issuecomment-370102048 using your GitHub account
Received on Saturday, 3 March 2018 01:10:34 UTC