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

Re: [css-logical-properties] the 'inline-{start,end}' values for 'float' and 'clear'

From: Johannes Wilm <johanneswilm@vivliostyle.com>
Date: Fri, 13 Nov 2015 23:09:33 +0100
Message-ID: <CABkgm-QZQUpHha4+JpAFQ70-GxCjopaq8M3=mhxnL-0zDhsy_w@mail.gmail.com>
To: Jonathan Kew <jfkthame@gmail.com>
Cc: Koji Ishii <kojiishi@gmail.com>, Brad Kemper <brad.kemper@gmail.com>, Florian Rivoal <florian@rivoal.net>, www-style list <www-style@w3.org>, fantasai <fantasai.lists@inkedblade.net>, Rossen Atanassov <ratan@microsoft.com>, "Elika J. Etemad" <fantasai@inkedblade.net>, "Tab Atkins Jr." <jackalmage@gmail.com>
On Fri, Nov 13, 2015 at 9:55 PM, Jonathan Kew <jfkthame@gmail.com> wrote:

> On 13/11/15 19:20, Koji Ishii wrote:
>> Back up a bit, the original request was "is it safe to ship
>> 1-dimensional floats with logical directional values?" and while it'd
>> be ideal to figure out the final syntax for 2-dimensional floats to
>> answer to that question, I don't think it's absolutely required, as
>> long as we can agree that:
>> 1. If no other 2-dimensional-related properties are set (e.g.,
>> float-reference), and
>> 2. If either 'start' or 'end' is specified
>> we will handle it as 1-dimensional logical direction.
>> I think this makes sense given the consistency with 1-dimensional
>> properties such a text-align, and shipping 1-dimensional logical
>> directional values before we finalize 2-dimensional syntax is
>> beneficial. Tab's response reads to me that Tab and fantasai are fine
>> with this.
>> Can we conclude on this point first?
If I understand the browser implementers correctly, they would prefer
"start"/"end" over "inline-start"/"inline-end", but we are not sure whether
that will work with the 2D model.

I think we can agree on start/end without resolving all the other things,
under one of these two circumstances:

1. We decide that start/end is only used for the inline-direction.  For the
block-direction we will potentially use block-start/block-end. If this is
not too confusing/inconsistent, then that should work.


2. We decide that the current, "inline" floats will always be 1
dimensional. If we want to have a 2D float within a container of some kind
at some point in the future, we will have to have a difference
float-reference value for that. Also, we may end up using
inline-start/inline-end for those other types of floats instead of
"start"/"end", and we are OK with this inconsistency.

My understanding from Fantasai's latest emails is that her and Tab still
have to spend some time looking at floats more in depth, so it is too early
to get a final word from them on what they believe the logical directions
should be called.

> Thanks for reminding us of the original question. :)
> Just for reference, what I have recently landed in Gecko (currently on
> track for Firefox 45) is an implementation of the logical values as found
> in the current text of CSS Logical Properties (Editor’s Draft, 26 October
> 2015), i.e. 'inline-start' and 'inline-end'.
> But because of the lack of clarity here -- despite Tab's message, it
> wasn't clear to me that there's anything like consensus in the WG -- these
> properties are behind a runtime preference that will be OFF by default on
> the Beta and Release channels, so the logical properties will only be
> enabled (by default) for Nightly and Developer Edition builds.
> (They'll also be enabled -- for both nightly and release builds -- in
> FirefoxOS, because the FxOS UI wants to start using them. But as long as
> they're not shipping on the desktop browser release channel, exposure to
> the Web in general remains very limited.)
> JK
Received on Friday, 13 November 2015 22:10:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:58 UTC