Can we unprefix min/max-width/height keywords?

[alanc...@chromium.org]

The following keywords that apply to the min-width, max-width, min-height and max-height properties are currently prefixed:

-webkit-min-content                                                              

-webkit-max-content                                                              

-webkit-fill-available                                                           

-webkit-fit-content                                                              

Is there a tracking bug for unprefixing these properties?

Where do we deviate from spec (http://dev.w3.org/csswg/css-box-3/#min-max) in supporting these keywords?

I ask because min-content and max-content keywords are unprefixed in CSS Grid properties which is causing a round trip inconsistency with getComputedStyle(): http://jsfiddle.net/rLbq5vn0/

It's trivial to patch this issue up in getComputedStyle() but I was wondering if there was anything blocking us from just unprefixing the keywords instead.

[PhistucK]

You should probably coordinate with davve as he is "Working on content sizing/intrinsic size for HTML and SVG" -

https://groups.google.com/a/chromium.org/forum/#!searchin/blink-dev/davve/blink-dev/Gmiodt2RZ7w/iL9qTyXeyh4J

I think this specification might be sort of a successor to the one you mentioned (updated about a week ago, while yours was updated in 2014) -

http://dev.w3.org/csswg/css-sizing-3/

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "style-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to style-dev+...@chromium.org.
To post to this group, send email to styl...@chromium.org.
To view this discussion on the web, visit https://groups.google.com/a/chromium.org/d/msgid/style-dev/346e8a4e-ac08-4db4-8f45-ee31b8d05c68%40chromium.org.

[David Vest]

On Fri, Jun 5, 2015 at 9:39 AM, PhistucK <phis...@gmail.com> wrote:
> You should probably coordinate with davve as he is "Working on content
> sizing/intrinsic size for HTML and SVG" -
> https://groups.google.com/a/chromium.org/forum/#!searchin/blink-dev/davve/blink-dev/Gmiodt2RZ7w/iL9qTyXeyh4J

What I most recently looked at in this area was what to do with the
unprefixed intrinsic and min-intrinsic keywords. There are now
usecounters:

https://www.chromestatus.com/metrics/feature/timeline/popularity/751
https://www.chromestatus.com/metrics/feature/timeline/popularity/752

They missed the M43 branch point, so I'll be waiting for the stable
results a while longer.

>> It's trivial to patch this issue up in getComputedStyle() but I was
>> wondering if there was anything blocking us from just unprefixing the
>> keywords instead.

Unprefixing them would be nice indeed but I don't know off hand how
close we currently are to the spec. Christian and I briefly discussed
some differences in:

https://groups.google.com/a/chromium.org/d/msg/blink-dev/Gmiodt2RZ7w/5r2jRow18fsJ

David

[Christian Biesinger]

On Thu, Jun 4, 2015 at 8:21 PM, <alanc...@chromium.org> wrote:
> The following keywords that apply to the min-width, max-width, min-height
> and max-height properties are currently prefixed:
> -webkit-min-content
> -webkit-max-content
> -webkit-fill-available
> -webkit-fit-content
>
> Is there a tracking bug for unprefixing these properties?
> Where do we deviate from spec (http://dev.w3.org/csswg/css-box-3/#min-max)
> in supporting these keywords?

The spec in question is an editor's draft only, and most of the spec
is not very mature. We should get an opinion of the CSSWG on the
maturity of those specific values before we consider unprefixing.

-christian

[alanc...@chromium.org]

On Saturday, 6 June 2015 05:58:26 UTC+10, cbiesinger wrote:

Sounds like there's still a few stages to go before we're ready to unprefix. I'll alter getComputedStyle() to return prefixed values instead.

Thanks! 

[Christian Biesinger]

To follow up on this (two months later...), I emailed www-style and
talked to Tab and Elika about this.

https://lists.w3.org/Archives/Public/www-style/2015Aug/0039.html

They told me that the CSSWG approves of unprefixing these keywords;
they don't expect them to change. They will resolve the remaining
issues marked in that doc (by removing repudiate-floats and not
changing the spec for the others).

So, I think it's time to send an Intent to Ship. I will do that.

-christian

> --
> You received this message because you are subscribed to the Google Groups

> "layout-dev" group.

> To unsubscribe from this group and stop receiving emails from it, send an

> email to layout-dev+...@chromium.org.
> To post to this group, send email to layou...@chromium.org.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/layout-dev/817fc121-fa08-4eb6-901b-d2d244277a5d%40chromium.org.

[alanc...@google.com]

Thanks for moving this forward. (: