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

Re: [css-writing-modes][css-scoping] unicode-bidi in Shadow DOM, and possibly other properties?

From: Koji Ishii <kojiishi@gmail.com>
Date: Fri, 23 Jan 2015 11:21:26 +0900
Message-ID: <CAN9ydbVg81vmWMewWB8jUxZqO_g8BDLjsYcGiCxHw+6HRqzocQ@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: "Asmus Freytag (t)" <asmus-inc@ix.netcom.com>, Simon Pieters <simonp@opera.com>, www-style list <www-style@w3.org>, "public-i18n-bidi@w3.org" <public-i18n-bidi@w3.org>
Yeah, I was looking for "isolate" and that made me forget about the case
insensitive flag.

Updates on the original topic, there were some back and forth since last
discussed here, but the current idea is to change the "dir" attribute to
inherit into shadow tree to keep it in sync with direction/unicode-bidi.
It's currently tracked in webapps bug 27359[1].

[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=27359

On Fri, Jan 23, 2015 at 11:02 AM, Tab Atkins Jr. <jackalmage@gmail.com>
wrote:

> On Thu, Dec 18, 2014 at 6:20 AM, Asmus Freytag (t)
> <asmus-inc@ix.netcom.com> wrote:
> > On 12/17/2014 4:34 AM, Koji Ishii wrote:
> >> What's more interesting to me is that this section uses dir="i", which
> >> is not defined in either HTML spec[3][4].
> >
> > Just  a guess: "i" would seem a possible abbreviation of "implicit" -- in
> > that case "unicode-bidi" is a good substitute.
>
> No, Simon Pieters replied with the answer to this - Koji was
> misreading the CSS.  He was looking at the "i" flag, which indicates
> that an attribute selector should be case insensitive.
>
> ~TJ
>
Received on Friday, 23 January 2015 02:21:53 UTC

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