- From: <bugzilla@jessica.w3.org>
- Date: Tue, 12 Oct 2010 11:19:30 +0000
- To: public-i18n-bidi@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10815 --- Comment #11 from Martin Dürst <duerst@it.aoyama.ac.jp> 2010-10-12 11:19:30 UTC --- (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. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You reported the bug.
Received on Tuesday, 12 October 2010 11:19:33 UTC