W3C home > Mailing lists > Public > www-style@w3.org > January 2015

Re: [css-logical-props] handling values that are valid in one orientation but invalid in another

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 9 Jan 2015 15:35:49 -0800
Message-ID: <CAAWBYDBV65fQ9nVCJBG6mrpaZz0WnXbYHQ_xYQ5ce7QSr2d1vA@mail.gmail.com>
To: Cameron McCormack <cam@mcc.id.au>
Cc: www-style list <www-style@w3.org>
On Tue, Jan 6, 2015 at 10:48 PM, Cameron McCormack <cam@mcc.id.au> wrote:
> This might be a hypothetical question for now.  How do we handle logical
> properties whose corresponding physical properties don't take the same set
> of values?  Will we have a general rule to handle cases like this?
>
> Gecko currently supports prefixed versions of {min,fit,max}-content values
> on the width property but not on the height property.  If I want to continue
> that arrangement, and I want to implement the new {block,inline}-size
> logical properties, how should I handle for example:
>
>   div { writing-mode: horizontal-tb; block-size: -moz-min-content; }
>
> Presumably this parses OK and you can inspect the block-size property's
> value on the declaration.  But at computation time, what value should the
> height property get?
>
> One answer would be to make it the initial value; this is what happens with
> properties that have variables that don't resolve to a valid value.

The Sizing spec does not limit the *-content properties to just
'width'.  Fix your implementation. ^_^

~TJ
Received on Friday, 9 January 2015 23:36:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:51:56 UTC