[Webkit-unassigned] [Bug 188752] New: slotchange event does not fire with initial content
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Aug 20 11:44:48 PDT 2018
https://bugs.webkit.org/show_bug.cgi?id=188752
Bug ID: 188752
Summary: slotchange event does not fire with initial content
Product: WebKit
Version: Safari 11
Hardware: Macintosh
OS: macOS 10.13
Status: NEW
Severity: Normal
Priority: P2
Component: HTML DOM
Assignee: webkit-unassigned at lists.webkit.org
Reporter: jan at component.kitchen
CC: cdumez at apple.com
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.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180820/c1046111/attachment.html>
More information about the webkit-unassigned
mailing list