Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint from CSS Meeting Bot via GitHub on 2018-03-05 (public-svg-issues@w3.org from March 2018)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Mon, 05 Mar 2018 19:46:05 +0000
To: public-svg-issues@w3.org
Message-ID: <issue_comment.created-370540398-1520279164-sysbot+gh@w3.org>

The Working Group just discussed `Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint`.

<details><summary>The full IRC log of that discussion</summary>
&lt;BogdanBrinza> topic: Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint<br>
&lt;BogdanBrinza> GitHub: https://github.com/w3c/svgwg/issues/389<br>
&lt;BogdanBrinza> Resolved: Change the argument to functions that take DOMPoint (getCharNumAtPosition, isPointInFill, isPointInStroke) to DOMPointReadOnly<br>
&lt;BogdanBrinza> additional note that we'll keep GitHub issue active to continue SVGPointList ongoing discussion<br>
</details>


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

Received on Monday, 5 March 2018 19:46:11 UTC