Thanks for diving into the conversation Tab! I guess I just need to wait for
Elliott to confirm shadow roots create counter scopes.
Andrei.
From: Tab Atkins Jr. [jackalm...@gmail.com]
Sent: Monday, March 11, 2013 12:53 PM
To: Andrei Bucur
Cc: Elliott
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
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,
event. The reason is to allow smooth updates of the layout when the user
resizes the browser window.
Thoughts?
Thanks,
Andrei.
Begin forwarded message:
From: Andrei Bucur abu...@adobe.com
Subject: Re: Scheduling multiple types of end-of-(micro)task work
Date: October 19, 2012 5:53:27 PM GMT+03
Hello,
I agree using micro-tasks for the regionLayoutUpdate event is not a very good
option and we should respecify the event behaviour.
One idea that comes in my mind is to specialize the regionLayoutEvent into
something more measurable (basically, having a better answer to what are the
Hi!
I was wondering if it would make sense to use supplemental interfaces as a
way to generate union types, like in this example:
X implements S
Y implements S
Z implements S
interface someInterface
{
NewSyntaxGeneratingUnionTypeFrom(S) someMethod();
}
The example assumes the user agent
It's not impossible in IDL. In fact, it's remarkably easy to define in IDL.
We
just don't want to implement multi-inheritance in WebKit because it's slow.
However, I don't see how Andrei's proposal makes the implementation any
more efficient.
The proposal tries to reduce the issue this
Hello,
This is a cross-post from the www-style discussion list in case anyone is
interested about this subject:
Currently the CSS Regions spec doesn't mention what happens with regions
that are part of a shadow tree. The NamedFlow interface exposes the
getRegions API that returns the sequence of
