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

Why would the input parameter need to be restricted to read only, in either case? You're calculating a result based on the current point value, not creating a permanent relationship to the object.

If anything, the intersection list functions are the ones that should change. I don't know why the parameters are specified as read only, but I wouldn't be surprised to discover it's because of some overzealous find & replace when the read only interfaces were defined.

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

Received on Saturday, 24 February 2018 03:11:20 UTC