Sprehn; public-webapps
Subject: Re: [shadow-dom] Counters and list item counting
On Thu, Mar 7, 2013 at 1:43 AM, Andrei Bucur abu...@adobe.com wrote:
Hello,
I want to clarify a certain situation:
ol
liA/li
li id=host
ShadowRoot
liX/li
liY/li
On Thu, Mar 14, 2013 at 12:47 PM, Andrei Bucur abu...@adobe.com wrote:
Thanks for diving into the conversation Tab! I guess I just need to wait for
Elliott to confirm shadow roots create counter scopes.
I talked with him about this at lunch, and he's fine with it.
~TJ
A kind reminder this question still requires an answer. I'd like to know if
it's OK to implement lists to act as shown in the first rendering of the
example (i.e counting doesn't cross upper-boundary encapsulation).
Thanks,
Andrei.
On Mar 7, 2013, at 11:43 AM, Andrei Bucur abu...@adobe.com
On Thu, Mar 7, 2013 at 1:43 AM, Andrei Bucur abu...@adobe.com wrote:
Hello,
I want to clarify a certain situation:
ol
liA/li
li id=host
ShadowRoot
liX/li
liY/li
ShadowRoot
/li
liC/li
/ol
How is this case supposed to
Hello,
I want to clarify a certain situation:
ol
liA/li
li id=host
ShadowRoot
liX/li
liY/li
ShadowRoot
/li
liC/li
/ol
How is this case supposed to be rendered?
1. A
2. 1. X
2. Y
3. C
or
1. A
2,3. X
4. Y
5. C
Basically,
Currently in Webkit list item counting is done on the render tree, but we
are looking at making it use the DOM instead so that ordered lists work
properly in regions. This raises an interesting question about if they
should use the composed shadow tree, or the original tree.
ex.
x-widget
ol
li
On 2/19/13 2:20 PM, Elliott Sprehn wrote:
Currently in Webkit list item counting is done on the render tree, but
we are looking at making it use the DOM instead so that ordered lists
work properly in regions.
Why wouldn't they work properly even if done on the render tree?
Note that if you do
On Tue, Feb 19, 2013 at 11:38 AM, Boris Zbarsky bzbar...@mit.edu wrote:
On 2/19/13 2:20 PM, Elliott Sprehn wrote:
Currently in Webkit list item counting is done on the render tree, but
we are looking at making it use the DOM instead so that ordered lists
work properly in regions.
Why
On 2/19/13 2:43 PM, Tab Atkins Jr. wrote:
There's some layer-breaching intrinsic to this. You do have to
examine your styles to see if you generate a box.
Well, your styles and the styles of all your ancestors in the flattened
tree, yes?
I wouldn't want it to rely on the box tree, though,
On Tue, Feb 19, 2013 at 11:49 AM, Boris Zbarsky bzbar...@mit.edu wrote:
On 2/19/13 2:43 PM, Tab Atkins Jr. wrote:
There's some layer-breaching intrinsic to this. You do have to
examine your styles to see if you generate a box.
Well, your styles and the styles of all your ancestors in the
On 2/19/13 3:02 PM, Tab Atkins Jr. wrote:
For example, if you intend for the component to contain a ul
Oh, effects with components in particular.
Yeah, ignoring the rearrangement done by components for purposes of
counters makes sense to me.
-Boris
11 matches
Mail list logo
