New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 847979 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: May 2018
Cc:
█ kochi@chromium.org
hayato@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 2
Type: Bug

Blocking:
issue 738611



Sign in to add a comment

<dialog> 'close' event not bubbling in Shadow DOM v1

Project Member Reported by dpa...@chromium.org, May 30 2018 
The 'close' event fired from a <dialog> used to cross the Shadow DOM boundary in v0. This is no longer the case for v1. Is this intentional?


v0 minimal example: https://jsfiddle.net/b4ohr7s1/
v1 minimal example: https://jsfiddle.net/mn10za9x/1/

This is affecting issue 738611, since the code currently relies on 'close' bubbling across Shadow DOM boundaries.

Comment 1 by dpa...@chromium.org, May 30 2018

Blocking: 738611

Comment 2 by hayato@chromium.org, May 31 2018

Status: WontFix (was: Untriaged)
The behavior is correct. Yup, it's the intentional change in v1.

The Event got a new attribute, composed.
https://dom.spec.whatwg.org/#dom-event-composed

- https://github.com/w3c/webcomponents/issues/513.
- https://github.com/w3c/webcomponents/issues/614.

The workaround would be to catch the event manually in the shadow tree, and re-dispatch in the host or other elements.

Comment 3 by dpa...@chromium.org, May 31 2018 

Thanks for the links. I filed  issue 848518  to further track work needed for cr-dialog, such that the 'close' events bubbles.
►

Sign in to add a comment