- From: Fredrik Söderqvist via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Apr 2020 14:45:23 +0000
- To: public-svg-issues@w3.org
This API is only a (very) rough sketch, but I think the intended behavior is the second option. The API is defined in terms of "segments", and there are three of those in this example, not two. If a consumer want's to know the exact original data they can examine the string. Expecting round-trips to be "character-accurate" does not seem reasonable - "segment-accurate" more so. I'm not aware of other cases where round-tripping, for example, an IDL attribute offers this guarantee on serialization (in general because that would require preserving too much data). -- GitHub Notification of comment by fsoder Please view or discuss this issue at https://github.com/w3c/svgwg/issues/789#issuecomment-611567627 using your GitHub account
Received on Thursday, 9 April 2020 14:45:25 UTC