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

Re: Suggested Solution for more RTL\LTR Agnostic Web

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 13 Mar 2015 14:07:11 -0700
Message-ID: <CAAWBYDAEPUPOkLtB9fGNgjH+ij9gG9NfA0xfckj3DGFBz3vCOQ@mail.gmail.com>
To: "Aharon (Vladimir) Lanin" <aharon@google.com>
Cc: Saad Alothman <me@saadalothman.com>, W3C style mailing list <www-style@w3.org>
On Thu, Mar 12, 2015 at 5:23 AM, Aharon (Vladimir) Lanin
<aharon@google.com> wrote:
> There was an attempt to do this at a W3C TPAC a while back (2010? not sure),
> but it got rejected. Fantasai may remember the exact reasons. But the part
> that always bothered me about this was this:
>> depending on the direction of the document, the browser should interpret
>> the start and end accordingly
> It does not really make sense to make it dependent on the direction of the
> document (i.e. direction of the topmost element): the direction could change
> any number of times between the topmost element in the document and the
> element with -start or -end property. So, the proposal referred instead to
> the direction of the element itself. The problem is that quite often, that's
> not what one wants, but the direction of the parent element (when the two
> are different). But this is not a hard-and-fast rule. In fact, what's most
> useful might depend on the exact property: text-align:start (which actually
> made it in and works in all browsers) refers to the direction of the element
> itself, while float:start would most probably need to refer to the parent,
> and padding-start probably needs to refer to the element itself, but who
> knows?

This is why the Alignment spec has both start/end and
self-start/self-end keywords.  Something similar could be done for the
logical properties.

Received on Friday, 13 March 2015 21:07:58 UTC

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