- From: Cameron McCormack via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 May 2020 06:28:00 +0000
- To: public-svg-issues@w3.org
Someone brought up a test case that runs into this difference between Firefox (which still addresses individual UTF-16 code units, per the current spec text) and other browsers (which use whole Unicode characters). I just want to clarify that the previous resolutions are in line with Tav's original request to change Firefox to match Chrome and Safari by indexing on whole characters. I'm fine with that, and the patch to fix that is pretty easy. If that's right, I can file a PR to fix the "addressable character" definition. @AmeliaBR could you confirm? -- GitHub Notification of comment by heycam Please view or discuss this issue at https://github.com/w3c/svgwg/issues/537#issuecomment-629054442 using your GitHub account
Received on Friday, 15 May 2020 06:28:02 UTC