Open karlcow opened 2 years ago
Given this is implemented everywhere today, does it make sense to just handle this in the CSS WG rather than in the Compat WS?
Given this is implemented everywhere today, does it make sense to just handle this in the CSS WG rather than in the Compat WS?
Sounds like a better destination, yes.
Yes it does, hence my Just as a placeholder for now.. aka paper trail for future references.
And I realize this can be read as a placeholder in the spec. This is not it. I'm talking about a placeholder in the issues list :) aka there is an entry in the issues list of compat repo if someone is looking for information here so we can redirect to the right place.
see https://bugzilla.mozilla.org/show_bug.cgi?id=1896571 where the site is not scrollable in Firefox.
@miketaylr in #269
Firefox is shipping this, see: https://groups.google.com/a/mozilla.org/g/dev-platform/c/-pMSV-kgUjA/m/VRL09R1NAAAJ
Extracting a comment from interop discussions Just as a placeholder for now.
width
/height
,(min|max)-(width|height)
with the valuestretch
It's a mess.
Two years ago I was wondering if there was a counter for
-webkit-fill-available
@foolipOriginally posted by @karlcow in https://github.com/web-platform-tests/interop-2022-viewport/issues/18#issuecomment-1224091012