Spent last week in Paris for @csswg face-to-face meeting. Full agenda was wiki.csswg.org/planning/pari… . Thread on some interesting bits:
1
6
6
Additive cascading proposal, to fix a longstanding problem with CSS cascading, was well-received. Need to find the least-bad syntax.
1
2
Additive cascading would allow CSS declarations to add to the next-highest-priority declaration rather than overriding.
1
Open question on additive cascade is whether it's just about appending to list-valued properties, or does more interpolation.
1
It's good to see progress on CSS Fonts level 4, thanks to @Litherum. Think we sorted spec/implementation inconsistency on CSSFontFaceRule.
1
1
Key feature driving Fonts 4 seems to be OpenType variations, which seem to have a lot of momentum, and could lead to a bunch of new things.
1
CSS Shadow Parts tabatkins.github.io/specs/cs… by @tabatkins was well-received, and seems like a good encapsulation balance. Naming questionable.
1
1
Proposal from @grorgwork for standardized browser-defined CSS variables (for things that are like media queries) is also interesting.
2
1
1
And we had (another) long discussion of ways to maintain even line spacing (for which we have 2 draft specs: css-line-grid & css-rhythm)...
1
2
... in which I suggested turning on line-grid should also change inline layout to honor 'line-height' only on blocks (not inlines) ...
1
Replying to @davidbaron @csswg
... which would mean variations in size/alignment of line's contents (that still fit within the line-height) wouldn't jitter line spacing.

Aug 8, 2017 · 3:38 AM UTC

1
Replying to @davidbaron @csswg
This made me want to look into whether there are ways to simplify the css-line-grid proposal a little (and maybe integrate with css-align).
1