206374 2020-01-16 14:20:07 -0800 Non-composed CustomEvent's target property is not retargeted to null 2020-11-09 08:48:44 -0800 1 1 1 Unclassified WebKit DOM Safari 13 Mac macOS 10.14 RESOLVED DUPLICATE 218638 InRadar P2 Normal --- 148695 1 ravi.jayaramappa webkit-unassigned cdumez rniwa webkit-bug-importer oldest_to_newest 1607664 0 ravi.jayaramappa 2020-01-16 14:20:07 -0800 When a non-composed CustomEvent is dispatched inside a shadow tree and the event finishes processing, the event's target is expected to be null. Instead, the event's target is pointing to the element on which it was dispatched. This behavior differs from the other browsers, where the event target is null. Repro steps: 1. Construct a DOM tree of this form <div> #shadow-root (open) <span></span> </div> 2. Dispatch an event on span element and access the event's target property const event = new CustomEvent('test', { bubbles: true }); span.dispatchEvent(event); console.log(event.eventPhase); // 0 console.log(event.target); // <span> in Safari; null in Chrome, Firefox, Edge; jsbin repro https://jsbin.com/likekis/edit?html,js,console 1608106 1 ravi.jayaramappa 2020-01-17 11:14:20 -0800 Found the relevant web platform tests to be failing. https://wpt.fyi/results/shadow-dom/event-post-dispatch.html?label=experimental&label=master&aligned 1608403 2 webkit-bug-importer 2020-01-17 23:28:12 -0800 <rdar://problem/58706920> 1705718 3 cdumez 2020-11-09 08:48:44 -0800 *** This bug has been marked as a duplicate of bug 218638 ***