Unprefix -moz-available keyword
Categories
(Core :: Layout, task, P3)
Tracking
()
People
(Reporter: boris, Unassigned)
References
(Depends on 2 open bugs, Blocks 5 open bugs, )
Details
(Keywords: dev-doc-needed, site-compat, Whiteboard: [webcompat])
We'd like to unprefix -moz-max-content and -moz-min-content in Bug 1322780. For -moz-fit-content and -moz-available, we should also unprefix them after the css sizing level 4 addresses them. This bug should also include renaming "-moz-available" to "stretch" [1]. [1] https://drafts.csswg.org/css-sizing/#sizing-values
Reporter | ||
Comment 1•6 years ago
|
||
From Bug 1322780 Comment 3 There are two test files for image fill: 1. attachment 8820716 [details] 2. attachment 8820886 [details] It seems Gecko only support -moz-available in the inline-direction though. We should probably not unprefix -moz-available before we support it in both.
Comment 2•5 years ago
|
||
The lack of unprefixed fit-content is causing cosmetic layout issues on dns.google.com (which only specifies the unprefixed variant).
Updated•5 years ago
|
Comment 3•5 years ago
|
||
Migrating Webcompat whiteboard priorities to project flags. See bug 1547409.
Comment 4•5 years ago
|
||
See bug 1547409. Migrating whiteboard priority tags to program flags.
Updated•5 years ago
|
Updated•4 years ago
|
Comment 6•4 years ago
|
||
Instead of unprefixing -moz-available
, It would be probably better to have an alias for -webkit-fill-available
.
And even before that it would be better to check if there is any attempt at using available as a term.
Comment 7•4 years ago
|
||
Philip,
I don't see any counters on Chromium for -webkit-fill-available
https://www.chromestatus.com/features#fill-available
And no specific issue about its future, apart issues such as
https://bugs.chromium.org/p/chromium/issues/detail?id=807708
I didn't find a bug for implementing stretch
keyword too.
Updated•4 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•2 years ago
|
Comment 10•1 year ago
|
||
I can confirm there's no use counter for this in Chrome, since it's a property value, and we only generate use counters automatically for properties.
Comment 11•22 days ago
•
|
||
I noticed this bug in a list of "WebCompat Priority: P2" bugs -- adding some notes:
(In reply to Boris Chiou [:boris] from comment #0)
[...]
For -moz-fit-content [...] we should also unprefix
(In reply to Thomas Wisniewski [:twisniewski] from comment #2)
The lack of unprefixed fit-content is causing cosmetic layout issues on dns.google.com (which only specifies the unprefixed variant).
Note, we fixed this specific part (unprefixing fit-content
) in bug 1732759.
These associated webcompat issues were all cases where a website depended on that specific unprefixed keyword:
https://webcompat.com/issues/22494
https://github.com/webcompat/web-bugs/issues/59967
https://github.com/webcompat/web-bugs/issues/73095
The other two associated webcompat issues seem to have been associated with this bug due to a site depending on -webkit-fill-available
:
https://webcompat.com/issues/56698
https://github.com/webcompat/web-bugs/issues/92483
...which we should perhaps consider supporting as an alias (per comment 6) independently of the bundle of unprefixing work that this bug proposes to eventually do (in comment 0 here). The bug to alias -webkit-fill-available
should perhaps have some associated WebCompat Priority assigned to it, but I'm not sure there's any particular webcompat priority for the other unprefixing work here (outside of fit-content
which we've already unprefixed).
Comment 12•22 days ago
|
||
[And I guess we already have bug 1872755 on file to support -webkit-fill-available. --> Adding that as a dependency, and transferring the WebCompat Priority status to that bug.]
[And while I'm editing things, I'll remove " -moz-fit-content" from the bug title here, since we're already done with that unprefixing as noted above.]
Comment 13•22 days ago
|
||
[moving two see-also webcompat bug associations to bug 1872755, too]
Updated•22 days ago
|
Comment 14•22 days ago
|
||
(In reply to Daniel Holbert [:dholbert] from comment #11)
The bug to alias
-webkit-fill-available
should perhaps have some associated WebCompat Priority assigned to it, but I'm not sure there's any particular webcompat priority for the other unprefixing work here (outside offit-content
which we've already unprefixed).
--> resetting WebCompat Priority for this bug here, after moving the former value over to bug 1872755
Description
•