(But also, to be clear, our test failure with-that-pref-enabled doesn't actually indicate a new bug being introduced here as part of `stretch`. The test just happens to rely on `width:stretch`, which means it only does-the-interesting-stuff if you have `stretch` enabled. But the same issue reproduces in current and older Firefox versions if you use devtools to replace `stretch` with its vendor-prefixed inline-specific sort-of-equivalent `-moz-available`.)
Bug 1920634 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(But also, to be clear, our WPT test failure with-that-pref-enabled doesn't actually indicate a new bug being introduced here as part of `stretch`. The test just happens to rely on `width:stretch`, which means it only does-the-interesting-stuff if you have `stretch` enabled. But the same issue reproduces in current and older Firefox versions if you use devtools to replace `stretch` with its vendor-prefixed inline-specific sort-of-equivalent `-moz-available`.)
(But also, to be clear, our WPT test failure with-that-pref-enabled doesn't actually indicate a new bug being introduced here as part of `stretch`. The test just happens to rely on `width:stretch`, which means it only does-the-interesting-stuff if you have `stretch` enabled. But the same issue reproduces in current and older Firefox versions if you use devtools to replace `stretch` with its vendor-prefixed inline-specific sort-of-equivalent `-moz-available`, as in testcase 1 here.)