Enable 'layout.css.webkit-fill-available.enabled' (support -webkit-fill-available in 'height' and 'width')
Categories
(Core :: CSS Parsing and Computation, enhancement)
Tracking
()
People
(Reporter: dholbert, Assigned: dholbert)
References
(Blocks 7 open bugs)
Details
(Keywords: dev-doc-complete, webcompat:platform-bug)
Attachments
(1 file)
Filing this bug to enable the layout.css.webkit-fill-available.enabled pref, to support -webkit-fill-available in 'height' and 'width' properties.
| Assignee | ||
Comment 1•5 months ago
|
||
WPTs exist in the css/css-sizing/stretch wpt-subdirectory, with naming
"stretch-alias-*". We pass most of these (enough that enabling this legacy
keyword is a net win for webcompat) - this pref-flip doesn't impact their
.ini files because the pref has already been default-enabled for that directory
up until this point.
| Assignee | ||
Updated•5 months ago
|
Backed out for causing reftest failures @grid-item-auto-min-size-clamp-007.html.
| Assignee | ||
Comment 6•5 months ago
|
||
For the part of that testcase that's changing its rendering here:
- it was essentially falling back to
height:autobehavior (but now actually does something more interesting, with support for this keyword) - Chrome agrees with our new rendering.
I'm going to add an annotation to disable this pref specifically for that test, and I'll file a followup on fixing up the test (and removing the annotation).
| Assignee | ||
Comment 7•5 months ago
|
||
I'm going through the webcompat bugs that we've got hanging off of bug 1872755 and similar bugs; and for those that are fixed by my patch here (enabling the keyword in 'width' or 'height'), I'm moving them to depend on this bug rather than the other one.
| Assignee | ||
Updated•5 months ago
|
Comment 9•5 months ago
|
||
| bugherder | ||
Comment 10•4 months ago
|
||
Is that something worth mentioning in the tech section of our general release notes or is the documentation in MDN enough? Thanks
| Assignee | ||
Comment 11•4 months ago
|
||
Yeah, it's probably worth mentioning.
Release Note Request (optional, but appreciated)
[Why is this notable]: We now support a nonstandard CSS sizing keyword that's used in-the-wild, and our lack-of-support has previously caused site breakage.
[Affects Firefox for Android]: Yes
[Suggested wording]: Firefox now supports the legacy "-webkit-fill-available" keyword as a value for the CSS "width" and "height" properties, to improve rendering of content on the web that uses this keyword. This keyword is an alias for the recently standardized "stretch" keyword (which isn't shipping in Firefox yet).
[Links (documentation, blog post, etc)]: https://developer.mozilla.org/en-US/docs/Web/CSS/width#stretch
(That's the MDN snippet on the standard stretch value; it mentions -webkit-fill-available as a prefixed alias in the compatibility section. I couldn't find any more-specific MDN page on specifically the alias itself.)
Comment 12•4 months ago
|
||
Thanks, note added to our Nightly-only release notes as the stretch keyword isn't shipping yet. here is the Nightly note wording:
Starting with Firefox 145, we now supports the legacy
-webkit-fill-availablekeyword as a value for the CSSwidthandheightproperties, to improve rendering of content on the web that uses this keyword. This keyword is an alias for the recently standardizedstretchkeyword (which isn't shipping in Firefox yet).
| Assignee | ||
Comment 13•4 months ago
|
||
Thanks! Looks like that's at https://www.firefox.com/en-US/firefox/145.0a1/releasenotes/
Minor typo, "we now supports" should say "support" (no trailing "s"). Mind fixing?
Comment 14•4 months ago
|
||
(In reply to Daniel Holbert [:dholbert] from comment #13)
Thanks! Looks like that's at https://www.firefox.com/en-US/firefox/145.0a1/releasenotes/
Minor typo, "we now supports" should say "support" (no trailing "s"). Mind fixing?
Fixed, will be live in 20mn
Comment 15•4 months ago
|
||
This is riding to beta/release, resetting the flag to keep on the radar for final release notes.
Comment 16•3 months ago
|
||
MDN docs changes can be tracked in the following GitHub issue: https://github.com/mdn/content/issues/41502
| Assignee | ||
Comment 17•3 months ago
|
||
pascal: could we back this bug's patch (comment 9) out from 145beta?
(This feature has at least one bug (bug 1990034) and possibly another (bug 1989365) that need fixing before it hits release. I'd been hoping to fix+uplift those to 145beta, but probably at this point the safer option is to turn this off for 145.)
Comment 18•3 months ago
|
||
| uplift | ||
Comment 19•3 months ago
|
||
(In reply to Daniel Holbert [:dholbert] from comment #17)
pascal: could we back this bug's patch (comment 9) out from 145beta?
(This feature has at least one bug (bug 1990034) and possibly another (bug 1989365) that need fixing before it hits release. I'd been hoping to fix+uplift those to 145beta, but probably at this point the safer option is to turn this off for 145.)
Done, I'll update our release notes documents to remove it from 145 new features
Updated•3 months ago
|
| Assignee | ||
Comment 20•3 months ago
|
||
Thanks!
Comment 21•3 months ago
|
||
Removed from Firefox 145 beta notes (and our draft final 145 notes). Added to 146 nightly notes as a carry over note from 146.
Given that it is still activated by default to ride the trains in 146, I am putting the relnote flag back to make sure we have it on our radar for the next beta/releaser cycle
Updated•3 months ago
|
Updated•3 months ago
|
Updated•3 months ago
|
Updated•2 months ago
|
Description
•