- From: Oriol Brufau via GitHub <noreply@w3.org>
- Date: Tue, 31 Mar 2026 02:46:34 +0000
- To: public-css-archive@w3.org
> To me they have the same behaviour for each property - its just if it failed to produce a size at all, we have to give it some size - and the fallback for the stretchable replaced elements is to just stretch to the container if possible I'm not sure if I'm getting this. When does this fallback kick in? It's still when resolving the value of each property right? - In `min-width`, fall back to 0 - In `max-width`, fall back to infinity - In `width`, fall back to stretch In all cases, clamp by transferred min/max-height if height is indefinite (if height is definite, just use the transferred height). In Servo that would be a bit annoying because the logic that resolves min/max-content (taking sizing constraints from the other axis into account) is not property-specific. The logic that resolves sizing values is property-specific, but currently doesn't have access to the sizing constraints from the other axis. -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13149#issuecomment-4159477821 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 31 March 2026 02:46:35 UTC