fantasai

@davidsgrogan > The flex item in question does not have a specified size suggestion, and is not replaced, and therefore it falls through to the final clause and uses its...

We need to go through https://drafts.csswg.org/css-flexbox/#min-size-auto and make sure that the new text is consistent with that; replaced elements at least should not have new behavior because of the new...

Key point: a flex item that has `min-width: 0` has no minimum for flex shrinkage. Any constraints transferred through the aspect ratio have an effect on the minimum size only...

I think this was fixed in https://github.com/w3c/csswg-drafts/commit/a5044beab5cd35e6eee2b6252dd788bf889880b8 @cbiesinger let me know if the spec seems to be correct now?

Disagree in the case of @supports. You're doing a syntax "is it supported" check there, and !important is arguably part of it.

Notes from chatting with @bramus, @mirisuzanne, and @rachelnabors: - Remove `view-timeline-fit` - Split `animation-timeline` into `animation-timeline-name` and `animation-timeline-phase`, with `animation-timeline` shorthand ``` animation-timeline-name: [ auto | none | ]# animation-timeline-phase:...

@birtles Wrt phases... I think it is an overlapping concept with timeline phases, it's just that we'd need timeline phases to be non-exclusive. You'd be in the active phase as...

Summary of where I think we're at from the [meeting notes](https://lists.w3.org/Archives/Public/www-style/2022Jun/0013.html): - Remove the `phase` API from Web Animations 1, and remove the before/after concepts, keeping just active/inactive states. -...

It seems that we have two ways forward towards interoperability here: - Option 1: Remove this special behavior from WebKit, and just let the font do what it does on...

So the goal of the min-content and max-content sizes are to represent the smallest and largest sizes that the box and its contents could lay out into without triggering overflow...