Notably, I'm *not* testing tables in these tests, because I found some interop differences between the behavior of my work-in-progress patch stack vs. WebKit (with -webkit-fill-available) vs. Blink. It's not entirely clear what's correct there (since tables are underspecified and often involve at least one content-measuring pass, and many table-part sizes are just a starting suggestion, etc.), so I'm going to add those tests separately as `.tentative` or in the mozilla private WPT directory, since I have less confidence about what expectations are correct there.
Bug 1933288 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Notably, I'm *not* testing tables in these tests, because I found some interop differences between the behavior of `stretch` in tables, in my work-in-progress patch stack vs. WebKit (with -webkit-fill-available) vs. Blink. It's not entirely clear what's correct there (since tables are underspecified and often involve at least one content-measuring pass, and many table-part sizes are just a starting suggestion, etc.), so I'm going to add those tests separately as `.tentative` or in the mozilla private WPT directory, since I have less confidence about what expectations are correct there.
Notably, I'm *not* testing tables in these tests, because I found some interop differences between the behavior of `stretch` in tables, in my work-in-progress patch stack, vs. Blink, vs. WebKit (with -webkit-fill-available since they don't yet handle `stretch`). It's not entirely clear what's correct there (since tables are underspecified and often involve at least one content-measuring pass, and many table-part sizes are just a starting suggestion, etc.), so I'm going to add those tests separately as `.tentative` or in the mozilla private WPT directory, since I have less confidence about what expectations are correct there.
Notably, I'm *not* testing tables in these tests, because I found some interop differences between the behavior of `stretch` in tables, in my work-in-progress patch stack, vs. Blink, vs. WebKit (with -webkit-fill-available since they don't yet handle `stretch`). It's not entirely clear what's correct for `stretch` in various table scenarios (since tables are underspecified and often involve at least one content-measuring pass where `stretch` would fall back to content-sizing; and many table-part CSS sizes are really just a starting suggestion; etc.), so I'm going to add those tests separately as `.tentative` or in the mozilla private WPT directory, since I have less confidence about what expectations are correct there.