- From: François REMY <francois.remy.dev@outlook.com>
- Date: Sun, 17 Feb 2013 23:13:47 +0100
- To: Tab Atkins Jr. <jackalmage@gmail.com>, Simon Sapin <simon.sapin@kozea.fr>
- CC: "Jens O. Meiert" <jens@meiert.com>, www-style list <www-style@w3.org>
> Correct on all counts. The parser isn't frozen, but neither are we > willing to make changes without corresponding benefits. This is what I wanted to stress: if we can get the same benefits without changing the syntax, not changing the syntax will be preferred. Changing the syntax can and will be done, when it will be needed. > Also, having the get and set notations identical will, I believe, lead > to persistent confusion among new authors that we can avoid by having > them slightly different. True. > A further downside of a syntax like Jens' is demonstrated by his very > example - he used "line-height: [var]px;", building a dimension out of > a variable and an identifier. It is workable. What bother me to me the most is that brackets should be kept for list-related things, something that CSS doesn't currently handle as good as it could. > (individual WG members might like one or the other > slightly better, but the WG as a whole hasn't found any to be > obviously superior) This is exactly the whole point. It's not because a majority has a preference for something else than what's currently in the spec that a majority around any of the alternative can be built. I don't think we really need more proposals at this point, we just need to see how much people are ready to make a compromise on their preference to build a majority around one or the other proposal.
Received on Sunday, 17 February 2013 22:14:17 UTC