Daniel Holbert

So: we may be kind of stuck here. Given the current interop noted in my past few comments (and in https://github.com/w3c/csswg-drafts/issues/5843#issuecomment-756480046 ), I am guessing that the web already depends...

Here's what the site looks like in step 6 (after I've completed a translation). Note that this non-functional "display statistics" menu-item has disappeared. 

I can also reproduce using current Nightly Firefox 105.0a1 (2022-07-26) (64-bit) and the Nightly translations-extension-version linked from https://github.com/mozilla/firefox-translations#nightly-builds , v1.1.3

Aha, so the "Display Statistics" menu-item *looked* like it had no effect, but really it does do something -- it seems to activate a special diagnostic mode **during the subsequent...

Gotcha, ok. So maybe "Statistics" isn't too far off. So then my main UX-gripe would be just that the label sound like it'll have an immediate effect (`Display $X` sounds...

...oh, it looks like our CSS here is all third-party; we're just using Bootstrap styles here, with a little bit of additional local styles. And apparently Bootstrap doesn't have special...

Just to clarify the proposal... How does writing-mode play into this (if at all)? E.g. in your example at the end, would anything need to work out differently if the...

(and relatedly: in practice, does this only change behavior for abspos flex children?)

> (Also none of the browsers support these keywords on min-block-size. But they parse it.) Could you elaborate on the lack-of-support? I believe we (Firefox at least) treat these keywords...

Hmm, interesting. I do see in the csswg discussion quoted there: > at one poin the spec defined min-content/max-content/fit-content to behave the same as 'auto' in the block axis So...