This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 20633 - [Shadow]: Events that are Always Stopped
Summary: [Shadow]: Events that are Always Stopped
Status: RESOLVED DUPLICATE of bug 20247
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 14978
  Show dependency tree / graph
 
Reported: 2013-01-10 13:38 UTC by Anne
Modified: 2013-04-01 23:21 UTC (History)
1 user (show)

See Also:

Attachments

Description Anne 2013-01-10 13:38:47 UTC 
1. What does shadow boundary mean here? If you have <a> and a child <b> and <a> has an associated shadow tree with an insertion point for <b>. If I dispatch load on <b>, surely it should still reach <a>?

2. If I dispatch in <a>'s associated shadow tree, how does the current definition ensure <a> does not get it during capture?
Comment 1 Dimitri Glazkov 2013-04-01 23:21:12 UTC 

*** This bug has been marked as a duplicate of bug 20247 ***