[Webkit-unassigned] [Bug 169718] New: Changes to slot children should trigger slotchange

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Mar 15 16:31:32 PDT 2017


            Bug ID: 169718
           Summary: Changes to slot children should trigger slotchange
    Classification: Unclassified
           Product: WebKit
           Version: Safari Technology Preview
          Hardware: Macintosh
                OS: macOS 10.12
            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/pimijip/edit?html,console,output.

This adds a child node to a `slot`.
Expect: this triggers a `slotchange` event. Blink does this as expected.
Actual: this doesn't trigger `slotchange`.

Rationale: If no nodes are assigned to a slot, then invoking `assignedNodes` on the slot will return any children of the slot itself. That is, the slot's own children serve as default content. Those children will be returned when asking for `assignedNodes`. Changes in the slot's children will be reflected in subsequent requests for `assignedNodes`. Since the set of `assignedNodes` is changing, the slot should be raising `slotchange`.

(If nodes *are* assigned to a slot, changes in the slot's direct children will not affect `assignedNodes`, and hence should *not* raise `slotchange`. Blink gets this right.)

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170315/78951fb3/attachment.html>

More information about the webkit-unassigned mailing list