-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Svg pars #2738
Svg pars #2738
Conversation
@kangax what do you think? |
@kangax Any chance to give a quick look to this? |
@asturur I would love to hear from one of the implementors (firefox, chrome, edge) if this is indeed an existing spec violation. @dstorey @tschneidereit @paulirish folks, any chance to ping one of your engineers familiar with SVG implementation in a browser? |
@erikdahlstrom should be a useful person to ask, and @boggydigital on Edge’s side. |
Looks like we're a bit lenient there, yes. Whether that's likely at all to change or the spec should just be changed to align with reality, I don't know. @heycam, can you comment? |
My personalo opinoin is that whetever is, or will be, in the spec, undestanding the transform attribute without spaces is a good feature. -transform value do not overlap each other so that the space ( or comma ) is necessary. -filling a transform attribute without spaces intentionally to make the transform uneffective is very unlikely. |
@kangax i still belive we should just merge this. |
The space between the transform items should be optional. Especially now given that the SVG |
Thanks juriy. |
Specs says that a space or comma between two transform is needed.
Chrome and firefox do not care for this space.
So maybe we should not care as well.
closes #2730