- From: <bugzilla@jessica.w3.org>
- Date: Mon, 06 Aug 2012 15:15:13 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18490 Aharon Lanin <aharon.lists.lanin@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aharon.lists.lanin@gmail.co | |m --- Comment #1 from Aharon Lanin <aharon.lists.lanin@gmail.com> 2012-08-06 15:15:13 UTC --- IMO, this is the correct approach for new pages. (In fact, I would even say unicode-bidi:isolate for elements with the dir attribute, and unicode-bidi:plaintext for elements with the lang attribute but lacking dir.) And in fact it is easy to do that in your (new) page's own CSS. However, one has to keep in mind that isolation is not implemented in IE9, and may or may not be implemented in the final release of IE10. So, if you need to have your page work bidi-wise for a high percentage of users, this just isn't good enough, not for a long while yet. :-( The other major concern here is backward compatibility. That is why I said above "new" pages. Applying bidi isolation to all elements with the dir attribute *will* break some existing pages. On the other hand, my guess is that applying bidi isolation to something with the lang attribute (and lacking a dir attribute) is unlikely to break existing pages, so it is probably a good idea. -- Configure bugmail: https://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 Monday, 6 August 2012 15:15:19 UTC