Browsers: Hey developers, tell us what features you want and give us use-cases! Everyone: Container Queries please 馃檹 heres a hundreds of reasons why Browsers: No, not them
4
5
81
/cc @tabatkins @chrishtr
2
2
@briankardell shared some very interesting thoughts over the f2f with me, Ian, and several others. Looks pretty promising, watch this space. (General answer, tho, is: getting CQs that don't have a 1-frame styling delay is super hard, but nothing else in CSS has such a delay.)
1
8
Brian's big insight was: can we allow the user to style used-value-time properties (anything that's not required for processing computed values; this excludes 'display', 'position', etc, but allows 'width', 'left', etc) using information that a LayoutWorklet would have access to?
4
5
I worry being unable to style 'font-size' cuts too heavily into the use cases for this. I should try to write up my current thoughts -- not this week, but maybe next.
1
2
font-size should be able to work within this mechanism I believe?
1
1
Oh right b/c font-size & rem... ugh.
1
1
Replying to @davidbaron @bfgeek @slightlylate @hankchizljaw @chrishtr @briankardell
Solution (not entirely joking): add a new 'actual-font-size' property that actually sets the font-size, and defaults to `1em`. 'font-size' just sets the size of the font-relative units. (Like how in SVG 'color' just sets currentcolor, other properties actually paint.)
2
5
smart!
1