Bug 188752
| Summary: | slotchange event does not fire with initial content | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Jan Miksovsky <jan> |
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | cdumez, rniwa, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari 11 | ||
| Hardware: | Mac | ||
| OS: | macOS 10.13 | ||
| Bug Depends on: | |||
| Bug Blocks: | 148695 | ||
Jan Miksovsky
See http://jsbin.com/wirubeq/edit?html,console,output.
In Chrome/Firefox, when a component with light DOM content is attached to the document, and a slot is created with a slotchange listener, the slot will raise an initial slotchange event. Safari does not do this.
The Chrome/Firefox behavior is useful because it allows a component to concentrate its initial content processing in a slotchange handler. To get consistent behavior, we have to normalize the slotchange behavior across browsers, which is cumbersome.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/43544149>
Ryosuke Niwa
This is a duplicate of webkit.org/b/169718.
*** This bug has been marked as a duplicate of bug 169718 ***