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 28246 - [Shadow]: Disable event capturing through a ShadowRoot
Summary: [Shadow]: Disable event capturing through a ShadowRoot
Status: RESOLVED DUPLICATE of bug 26892
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Hayato Ito
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 15480
  Show dependency tree / graph
 
Reported: 2015-03-20 00:39 UTC by Daniel Freedman
Modified: 2015-04-23 18:21 UTC (History)
5 users (show)

See Also:

Attachments

Description Daniel Freedman 2015-03-20 00:39:12 UTC 
Bug 20247 is still an annoying thorn for development, as it is just *awkward* to see non-bubbling events dispatch to ShadowRoot hosts.

Given that this property is a compromise compliance for the event capturing phase, can we instead just drop the ability to capture events through a ShadowRoot boundary?

It seems rather unlikely that a developer using capturing events will handle events fired inside of a ShadowRoot correctly, and it seems a beneficial property of closed ShadowRoots to close another loophole through which information can leak.

WDYT?
Comment 1 Elliott Sprehn 2015-03-20 02:14:43 UTC 
Can you give an example?
Comment 2 Dimitri Glazkov 2015-03-20 03:43:19 UTC 
This is highly related to bug 26892. Elliott, the example is present there.
Comment 3 Hayato Ito 2015-04-22 22:33:22 UTC 
I am feeling that we should have one good idea which resolves this bug (bug 28246), bug  26892 and bug 20247, all together.
Comment 4 Dimitri Glazkov 2015-04-23 18:21:42 UTC 

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