Daniel Holbert
Daniel Holbert
Indeed, the FF behavior is just because I haven't implemented `stretch` behavior in the block axis yet (keep getting distracted by other tasks, but made a little local progress this...
CC @fsoder @karlcow who've been involved on the Chromium and WebKit bugs, respectively. (@fsoder if I'm mischaracterizing your findings [about further improvements to Chromium on this being unshippable], please let...
Ah, I also just recalled/rediscovered that we've got a similar problem for the `.width` and `.height` attributes, noted in https://bugzilla.mozilla.org/show_bug.cgi?id=1935269#c17 Those are defined in terms of the "density-corrected natural width...
> This makes perfect sense to me. Would you be willing to work on a spec PR? Possibly! I suspect I can carve out some time for it next week....
Proposed spec-edit still coming eventually here; I'm currently finalizing some test updates and our implementation update, which will inform the proposed spec change. As part of the spec changes here,...
Chrome and Safari actually do agree with Firefox on [the testcase](https://bugzilla.mozilla.org/attachment.cgi?id=9428769) under one condition: if I open the browser's network-DevTools panel and check the "Disable Caches" checkbox. (Under that configuration,...
> iank_: in some cases Chromium is the only implementation that treats break-inside as non-monolithic. advised people to use contain: size for some cases. [...] > correcting earlier notes, iank...
This is a version of https://github.com/mozilla-mobile/firefox-ios/issues/11574 -- it looks like Firefox is dynamically resizing its viewport depending on the presence/absence of the dynamic toolbar. You can see this by visiting...
Still reproducible as-described in initial comment. (I just retested with current Firefox release vs. Safari, on my iPad.)