[whatwg] seamless iframes and event propagation

[Anne van Kesteren]

On Wed, Dec 5, 2012 at 12:37 PM, Hayato Ito <hayato at chromium.org> wrote:
> Some kinds of events should be always stopped at the shadow boundaries.
> See http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/shadow/index.html#events-that-are-always-stopped

It's not entirely clear to me what that means. If an <img> ends up
interleaved in a shadow tree through a <content> element, surely the
node tree ancestors of <img> should still get the load event? Does the
shadow tree not want to know this too?

Also, is input missing from that list? A short explanation along with
that list would probably be good so we know what the criteria are.


> The Shadow DOM spec does not require adjusting mouse coodinates. I
> think every shadow trees in one document *share* the same x-y
> coodinates.

There are coordinates relative to the target though, see:
http://dev.w3.org/csswg/cssom-view/#extensions-to-the-mouseevent-interface

I suppose if you do not initialize those on the object but instead
compute them on getting it might work without having to adjust
matters.


> I don't have a clear idea about what should be cloned when crossing
> boundaries. That's unclear for me.

Okay, I guess that remains then.


-- 
http://annevankesteren.nl/