W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2010

[Bug 10815] i18n comment 10 : block elements with display:inline should get ubi instead of default dir

From: <bugzilla@jessica.w3.org>
Date: Wed, 13 Oct 2010 19:55:42 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1P67QM-0002tp-Rx@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10815

--- Comment #12 from Aharon Lanin <aharon.lists.lanin@gmail.com> 2010-10-13 19:55:42 UTC ---
(In reply to comment #11)
> (In reply to comment #10)
> > I'm happy to spec whatever browsers do.
> > 
> > Previously I was told (by fantasai) to say 'unicode-bidi:embed' for all
> > non-'inline' elements, to avoid the problem described above.
> > 
> > Should I change this to 'unicode-bidi:isolate'? Would that resolve this bug?
> 
> I hope somebody can check the details, but to give some more historical
> background, when we were designing the bidi features in HTML (RFC 2070, taken
> over in HTML4) and CSS, we were not aware of the fact that bidi embeddings were
> as 'leaky' and 'promiscuous' as it later turned out they were. So it's very
> much possible that we would have choosen isolating behavior from the start if
> we knew about that.

Making them all 'unicode-bidi:isolate' sounds right to me. Fantasai?

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 13 October 2010 19:55:44 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:30:59 UTC