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

NEW
Unassigned

Status

()

enhancement
P3
normal
10 months ago
5 days ago

People

(Reporter: boris, Unassigned)

Tracking

(Depends on 1 bug, Blocks 4 bugs, {dev-doc-needed, site-compat})

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Webcompat Priority:P2, firefox64 affected)

Details

(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
See Also: → 1322780
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.
Depends on: 567039
Blocks: 1514264

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

Flags: webcompat?
Whiteboard: [webcompat]

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

Webcompat Priority: --- → ?

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

Webcompat Priority: ? → P2
Flags: webcompat?
You need to log in before you can comment on or make changes to this bug.