1495868 - Unprefix -moz-fit-content and -moz-available keywords

Status: NEW

(Core :: Layout, task, P3)

Description

[Boris Chiou [:boris]]

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

Comment 1

[Boris Chiou [:boris]]

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

[Thomas Wisniewski [:twisniewski]]

The lack of unprefixed fit-content is causing cosmetic layout issues on dns.google.com (which only specifies the unprefixed variant).

Comment 3

[Firefox Bug Husbandry Bot]

Migrating Webcompat whiteboard priorities to project flags. See bug 1547409.

Comment 4

[Firefox Bug Husbandry Bot]

See bug 1547409. Migrating whiteboard priority tags to program flags.

Comment 6

[Karl Dubost💡 :karlcow]

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

[Karl Dubost💡 :karlcow]

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.

Comment 10

[Philip Jägenstedt [:foolip]]

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.