Search results

Consider decoupling first-input logic from <code>set event timing entry duration</code>

Status: Open.

#159 In w3c/event-timing;

· francovs opened on Sep 19, 2025

"has dispatched input event" wording is misleading

Status: Open.

#158 In w3c/event-timing;

· smfr opened on Sep 10, 2025

Consider documenting the INP algorithm (as a non-normative section of Event Timing spec)

Status: Open.

#157 In w3c/event-timing;

· mmocny opened on Jul 23, 2025

Spec "fallbackTime" for cases where we don't need to wait for paint (modal dialog, visibilitychange...)

Status: Open.

#154 In w3c/event-timing;

· mmocny opened on Apr 30, 2025

Change the <code>pendingKeydowns</code> list and change keyboard <code>interactionId</code> assignment to be eager.

Status: Open.

#153 In w3c/event-timing;

· mmocny opened on Apr 16, 2025

Consider supporting native drag &amp; drop as an interactionId (and first-input candidate).

Status: Open.

#152 In w3c/event-timing;

· mmocny opened on Apr 14, 2025

<code>keypress</code> doesn't expose an <code>interactionId</code> but there is a web platform test for it

Status: Open.

#149 In w3c/event-timing;

· canova opened on Mar 3, 2025

<code>interactionId</code>s of keyboard simulated clicks are not spec'd

Status: Open.

#147 In w3c/event-timing;

· canova opened on Feb 24, 2025

"first-input" dispatch logic doesn't update the <code>interactionId</code> of <code>pointerdown</code> entries

Status: Open.

#146 In w3c/event-timing;

· canova opened on Feb 24, 2025

Delayed dispatch mechanism of <code>pointerdown</code> and <code>keydown</code> events doesn't work well

Status: Open.

#145 In w3c/event-timing;

· canova opened on Feb 24, 2025

"first-input" dispatch logic in the spec doesn't match the tests and the Chromium implementation

Status: Open.

#142 In w3c/event-timing;

· canova opened on Feb 17, 2025

Expose interactionId to keypress

Status: Open.

#134 In w3c/event-timing;

· zuoaoyuan opened on Jun 7, 2023