![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact:
Bert BosCopyright © 2020 W3C®
Last updated 2008-04-04 07:39:23
This is a page from the Cascading Style Sheets Working Group Blog. Some other places to find information are the “current work” page, the www-style mailing list, the Future of CSS syndicator, and the issue list on Github.
Do you want to know how the CSS WG works? Fantasai has written about:csswg, An Inside View of the CSS Working Group at W3C.
Highly experimental brainstorming-level stuff. No resolutions, just notes.
Discussed tree lists styling prompted by Andrew Fedoniouk.
Noted: Solution should satisfy 80-90% case; no point in adopting if it only solves 10%.
Noted: Designers will want control over color, width, style of lines. Using ‘outline’ or ‘border’ precludes giving the element a real outline or border.
Idea: A pseudo-element could provide a place to put styling.
Idea: One possible model is each list item has a T-shaped or L-shaped marker that connects with the previous.
Idea: Another possible model is each list item has a horizontal bar marker and the vertical line belongs to the parent.
Idea was to have two pseudo-classes, one :normal and one :alternate. UA toggles between styles. (N styles also possible.)
Existence of the pseudos makes the element toggleable. There were strong reservations about that.
Bert’s writeup is still Member’s only.
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.
Clear use case for importing colors from a site-wide style sheet. CSSWG wants more concrete use cases for anything beyond that.
fantasai points to webstandards.org comments and suggests macros for selectors, values, and declaration sets would fulfill most requests there.
CSSWG will post a simple proposal macros for values only, and see if that will cause web designers to post real examples of where more powerful macros are needed.
Suggested to add this to Selectors 4. Need implementors’ “strong interest”.
Steve reports on conclusions from joint meeting with Paul and fantasai: plan is to introduce text-orientation, which operates on runs of tex–unlike XSLFO/SVG’s glyph-orientation, which operates on individual glyphs. Glyph-orientation’s behavior causes characters to be in the wrong order for some of its values. text-orientation will take keywords for common effects in vertical text.