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 about that specific 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). **That** work 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).
Bug 1495868 Comment 11 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
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). **That** work 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).
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).