[Bug 27359] [Shadow]: Need to define interaction with directionality

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

--- Comment #7 from Hayato Ito <hayato@chromium.org> ---
(In reply to Boris Zbarsky from comment #6)
> Ah, there's some interesting subtlety here.
> 
> There's the inherent element directionality, but also the CSS
> directionality.  They both, separately, inherit.  The element directionality
> can affect the CSS directionality.
> 
> So it's possible that what's going on in terms of layout in Gecko and Blink
> is that the CSS directionality inherits.  That would explain the layout
> behavior.  But that leaves the question of element directionality open, of
> course.  I'd be interested in a way to directly query that in Blink.

I'm afraid that I don't have any idea how we should resolve this potential
conflict situation.

That reminds me of the similar issue I've encountered, 'contenteditable'
attribute in blink. WebKit has a CSS property that is similar to
contentEditable: `-webkit-user-modify`.

WebKit/Blink treats contenteditable attribute to something like as if the
element had 'user-modify' css property so that contenteditable were processed
as if it were css property.

To avoid the complex situation, I hope that we should treat both worlds,
'element attribute' and 'css property' in the same way as possible as we can.

My initial thought is that we should use a composed tree based tree walking for
both worlds, which would explain the layout behavior and match the parent/child
relationship which is used by a style inheritance.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 19 November 2014 09:40:25 UTC