311667 2026-04-07 12:20:18 -0700 [WPE] EventSenderProxy is sending separate events with identical timestamps 2026-04-09 08:19:37 -0700 1 1 1 Unclassified WebKit WPE WebKit WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED P2 Normal --- 1 lmoura lmoura bugs-noreply oldest_to_newest 2197721 0 lmoura 2026-04-07 12:20:18 -0700 Since 225273@main (6e8572e9fa63c), WPE's EventSenderProxy captures its creation time in EventSenderProxy::m_time, reusing it as the timestamp of its synthesized events. In order to "advance" events in time, this approach requires the tests to call EventSenderProxy::leapForward() through the InjectedBundle, as seen in several tests in fast/events, and fast/editing. This approach does not work when the test relies on actual wall time separation between the events without calling leapForward(). For example, this is the pattern used in some WPT tests like imported/w3c/web-platform-tests/event-timing/gap-keydown-keyup.html and imported/w3c/web-platform-tests/event-timing/gap-pointerdown-pointerup.html, mentioned in bug301110: ``` await new test_driver.Actions().keyDown('a').send() await something() await new test_driver.Actions().keyUp('a').send() // expect different timestamps ``` With the current approach, WPE's EventSenderProxy sends both keyDown and keyUp events with the same timestamp, despite being actually separated in time. Patch incoming. 2197759 1 lmoura 2026-04-07 14:37:13 -0700 Pull request: https://github.com/WebKit/WebKit/pull/62219 2198370 2 ews-feeder 2026-04-09 08:19:34 -0700 Committed 310845@main (fd4c158c5768): <https://commits.webkit.org/310845@main> Reviewed commits have been landed. Closing PR #62219 and removing active labels.