- From: Simon Pieters <simonp@opera.com>
- Date: Wed, 17 Dec 2014 12:36:10 +0100
- To: "www-style list" <www-style@w3.org>, public-i18n-bidi@w3.org, "Koji Ishii" <kojiishi@gmail.com>
On Wed, 17 Dec 2014 11:56:36 +0100, Koji Ishii <kojiishi@gmail.com> wrote: > Can bi-di & CSS experts help us to figure out what to do with > unicode-bidi and Shadow DOM? > > I’m thinking, at the Shadow DOM boundaries, the ‘unicode-bidi’ property > should be set to ‘isolate’ since that’s the value for bi-di to suffice > the philosophy of components IIUC. Is this correct? In Bidi Rules for > HTML4[1], I see <div>, <form>, etc. sets this, but I don’t see <input> > or <textarea>, so I’m not confident on this point and would appreciate > any advices. Maybe https://html.spec.whatwg.org/multipage/rendering.html#bidi-rendering is more relevant than the "for HTML4" appendix. (Can we drop those appendices? Why do we have them?) > The next question is, assuming so, what is the best way to force that. > Looking at Inheritance section of CSS Scoping[2], since top-level > elements of a shadow tree inherit from their host element, so I guess we > should let the computed value of ‘unicode-bidi’ of the host elements to > ‘isolate’. Is this correct approach? > > And the third and the last, I can’t find any other properties for the > Shadow DOM to handle differently than normal inheritance. Can someone > find any? > > [1] http://dev.w3.org/csswg/css-writing-modes/#bidi-html > [2] http://dev.w3.org/csswg/css-scoping/#inheritance > > /koji > > -- Simon Pieters Opera Software
Received on Wednesday, 17 December 2014 11:36:52 UTC