CSS Working Group latest resolutions
The CSS WG had a face-to-face meeting in San Diego last month, and have released their latest resolutions in a series of posts on their blog:
Part I, Part II, Part III, Part IV, Part V, Part VI
Some of the highlights I saw on my first read through:
- Apple’s proposed animation & transition properties are to be considered.
- Web fonts are to be worked on with the SVG team
- The Advanced Layout module is still being discussed but will be renamed the Template Layout module
- A new type of list, tree-lines, was proposed
- A proposal for the use of constants will be published
Obviously there’s a lot more in there, but it’s nice to see that the Working Group is working!













Wow, looks like the group has been very busy. I dig the constants and tree-lines proposals.
Looks like they are talking about doing “text-orientation” so you can do vertical text. Hopefully that will make it.
In part IV, the centering stuff was quite interesting.
I agree, that if I want to apply a “centering” it is only to a specified container… I do not want any children to inherit this centering.
Good progress!
I like the idea of constants. Very often I wished that I could define a set of colour constants and refer to them so I won’t have to search and replace every occurrence when I modify the colour scheme.
[...] A recent post on CSS3.Info regarding the CSS WG F2F in San Diego nicely sums up resolutions relating to possible up-coming CSS features. [...]
One thing that stuck out like a sore thumb:
> Scriptable Selectors
> Idea was that a selector accepts a JavaScript function that returns true or false, determining whether the selector matches or not. VERY strong reservations about this from implementors: executing functions during selector matching is scary, particularly if those functions are allowed to modify the elements during matching!
> Alternate idea is to define a set of tokens on the element node, allow scripts to add and remove tokens, and match against that set.. thereby avoiding the execution of any functions during style matching.
Don’t we already have that alternate idea? We call those tokens “classes”.
[...] CSS çalışma grubunun son toplantısından sonra alınan sonuçlar ve özet. Bağlantı [...]
Tree-line lists would be nice, but aren’t semantically obvious. Defining a list as a tree doesn’t offer any benefit in terms of organization, it’s purely decorative. Still would be nice.