- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 May 2018 14:44:18 +0000
- To: public-css-archive@w3.org
The attribute needs to support any syntax that was valid & supported for SVG 1.1, and preferably also any syntax that was technically invalid per spec but was widely supported. I would *like* to eventually make it a deprecated syntax & recommend authors use the CSS syntax, but we can't do that until browsers actually support the CSS syntax in the attribute. There is currently no "hybrid" syntax that works in either case. If defining the legacy syntax in CSS parsing grammar makes this second situation more likely, that would be a route forward. But I am in no way suggesting that we should remove currently well-supported syntax structures. So yes, that would mean defining a new syntax that looks something like `<legacy-translate-function> = [translate (|translate(]<number>[,? <number]?)` (with two options for the function, one as a single token and one as two tokens separated by whitespace). -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2623#issuecomment-386002600 using your GitHub account
Received on Wednesday, 2 May 2018 14:44:27 UTC