Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint

SVGPointList is a list of mutable points, so using DOMPoint there seems appropriate - that the list methods themselves does not mutate the objects does change what is stored in the list. Methods could (and maybe should?) take `DOMPoint or DOMPointReadOnly` and then invoke the same copying semantics as read-only DOMPoints are subjected too. The objects returned would still be DOMPoint regardless (since they represent a mutable entry in the list.)

As for "read-only DOMPoint" (I'm not finding the text about read-only list with read-write items - that sounds odd) I suspect that stems from `animatedPoints`, which has since been turned into an alias of `points` probably making the point about read-only points moot.

-- 
GitHub Notification of comment by fsoder
Please view or discuss this issue at https://github.com/w3c/svgwg/issues/389#issuecomment-370179768 using your GitHub account

Received on Saturday, 3 March 2018 21:05:27 UTC