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

Issue 761917 link

Starred by 1 user
Status: Fixed
Owner:
█ elkurin@google.com
Last visit > 30 days ago
Closed: Sep 2017
Cc:
█ kochi@chromium.org
hayato@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

slotchange event doesn't fire when a slot element is added after host children are added

Project Member Reported by elkurin@google.com, Sep 5 2017 
Chrome Version: 60.0.3112.113 (Official Build) (64-bit)
OS: Linux OS


JS code: http://jsbin.com/hicusulajo/1/edit?html,output

Expected result:
eventCount should be 1 because slotchange event should fire on a slot element (a host child 'span' is assigned to a slot).

Actual result:
eventCount is 0, which means slotchange event doesn't fire.

If host children are added after a slot node is added (like following JS code), then slotchange event succesfully fires.
http://jsbin.com/hicusulajo/3/edit?html,output

Comment 1 by hayato@chromium.org, Sep 5 2017 

Thanks. There is an existing wpt for that: http://w3c-test.org/shadow-dom/slotchange-event.html

I think this was already fixed by ToT. Could you verify the behavior in ToT build?

Comment 2 by elkurin@google.com, Sep 5 2017

Status: Fixed (was: Assigned)
I checked and it seems to be already fixed in 
Chrome Version: 63.0.3206.0 (Developer Build) (64-bit)

Comment 3 by yawano@chromium.org, Aug 24

Cc: sarakato@chromium.org

Comment 4 by yawano@chromium.org, Aug 24

Cc: -sarakato@chromium.org
►

Sign in to add a comment