Rune Lillesveen

Counter landed (for M105): https://chromium-review.googlesource.com/c/chromium/src/+/3698090 ons. 8. jun. 2022 kl. 11:44 skrev Simon Pieters ***@***.***>: > Summary: > > If it's web-compatible, I think we should remove this part of...

https://chromium-review.googlesource.com/c/chromium/src/+/6646507

Apart from the fact that it doesn't inherit from its originating element as the definition of tree-abiding says.

> I think we've settled on a proposal here, in two parts (see [#7551 (comment)](https://github.com/w3c/csswg-drafts/issues/7551#issuecomment-1398727361)): > > * No container is considered 'valid' for unknown query features (`general-enclosed`) > *...

The public use counter is super low, but quite early for that level of aggregation: https://chromestatus.com/metrics/feature/timeline/popularity/4596 But, I've also looked at the internal numbers which confirms that it's super low.

> Okay, first draft of the new spec text committed. It was a larger change than I thought it would be at first, but I think this captures the behavior...

> > What's the definition of first laid out? With container queries and scroll timelines there may be multiple passes where a box flips between being rendered and not in...

Regarding syntax, at least Gecko has shipped @font-feature-values accepting ``, so they will only recognize `@swash` in the latter rule. ``` @font-feature-values family { font-display: block; @swash { swishy: 1;...

Could a new rule for @font-face default values be an alternative? ``` @font-face-defaults # { } ```

Any feedback on this, or a counter-proposal? > Could a new rule for @font-face default values be an alternative? > > ``` > @font-face-defaults # { > > } >...