Event timing has added interactionId attribute to all entries, but to most entry types, its value would be 0. Currently it's only exposed to [pointerdown, pointerup, click, keydown, keyup] with non-trivial values.
Issue:
Keypress is possible to have the longest duration among all the entries from the same interaction, but having an interactionId 0 makes it not being counted towards INP and makes INP not reflecting the real user experience.
Proposed solution:
Event timing assign valid interactionId to keypress entry, and match it with the same interactionId of the keydown & keyup entries from the same interaction.
Context:
Event timing has added interactionId attribute to all entries, but to most entry types, its value would be 0. Currently it's only exposed to [pointerdown, pointerup, click, keydown, keyup] with non-trivial values.
Issue:
Keypressis possible to have the longest duration among all the entries from the same interaction, but having an interactionId 0 makes it not being counted towards INP and makes INP not reflecting the real user experience.Proposed solution:
Event timing assign valid interactionId to
keypressentry, and match it with the same interactionId of thekeydown&keyupentries from the same interaction.