The latest Webkit release (affecting Safari v17.4) is not setting the target and currentTarget attributes of a customEvent. Reproduction: https://codepen.io/graham_saunders/pen/jORKGJe Testing on <= v17.3 works as expected.
Created attachment 470876 [details] rendering in safari, firefox, chrome currentTarget is null in the 3 browsers. target and srcElement are different: * Firefox and Chrome: <input id="name" name="name"> * Safari: null Note that Firefox has also originalTarget and explicitOriginalTarget Tested in Safari Technology Preview 17.4 19619.1.8.1 Firefox Nightly 126.0a1 12624.4.11 Google Chrome Canary 125.0.6413.0 6413.0
<rdar://problem/126311287>
https://searchfox.org/wubkat/rev/8ce70fa03821ea1c7a19a3913730ffe6b8a522ed/Source/WebCore/dom/Event.cpp#126 https://searchfox.org/wubkat/rev/8ce70fa03821ea1c7a19a3913730ffe6b8a522ed/Source/WebCore/dom/CustomEvent.cpp#50
In Safari 16.1 on Ventura 13 I get target and srcElement initialized to <input id="name" name="name"> and currentTarget to null.
Regression range gives me: https://commits.webkit.org/compare/272803@main...272798@main I have the feeling it was broken by Bug 267188 https://github.com/WebKit/WebKit/commit/490b4fdda464141c8eedb0ec367dbf76c6077a77
Created attachment 470882 [details] Reduction
Pull request: https://github.com/WebKit/WebKit/pull/27184
Committed 277435@main (5b488a0a1b57): <https://commits.webkit.org/277435@main> Reviewed commits have been landed. Closing PR #27184 and removing active labels.