Bug 206374

Summary: Non-composed CustomEvent's target property is not retargeted to null
Product: WebKit Reporter: Ravi Jayaramappa <ravi.jayaramappa>
Component: DOMAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: cdumez, rniwa, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Safari 13   
Hardware: Mac   
OS: macOS 10.14   
Bug Depends on:    
Bug Blocks: 148695    

Ravi Jayaramappa
Reported 2020-01-16 14:20:07 PST
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
Attachments
Ravi Jayaramappa
Comment 1 2020-01-17 11:14:20 PST
Radar WebKit Bug Importer
Comment 2 2020-01-17 23:28:12 PST
Chris Dumez
Comment 3 2020-11-09 08:48:44 PST
*** This bug has been marked as a duplicate of bug 218638 ***
Note You need to log in before you can comment on or make changes to this bug.