Re: [svgwg] Serialization format for path strings

So to be clear you propose to not absolutize in getComputedStyle either? I didn't understand that, sorry. That's fine for me as well.

The only thing I'd like is not having to switch representation from specified to computed style.

> D3 animation of complex types like path strings works by breaking the string into numbers versus text, and then interpolating the numbers while instantly switching the strings.

That looks very error-prone fwiw :)

So to be clear, there are three different possible proposals here:

 1. Absolutize at parse-time, and thus both specified and computed value returns absolute coordinates.
 2. Absolutize at computed-value time, that is, specified style serializes as specified, computed style serializes with always-absolute coordinates.
 3. Don't absolutize anywhere except when needed for animations.

I'm fine with either 1 or 3, but 2 is a bit of a pain for us, because it requires either normalizing the path eagerly or once-per-element, or more special-casing which I'd love to avoid.

If I understand correctly Chrome currently does 3.

Per your comment above, looks like the behavior that would break D3 is either 1 or 2, and what you want is 3, right? Or are you proposing other kind of normalization? If so, which?

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

Received on Thursday, 20 September 2018 19:46:31 UTC