New issue
Advanced search Search tips

Issue 831734 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Sep 10
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

[EventTiming] Use the first event-timestamp instead of the last for coalesced events in Event Timing

Project Member Reported by maxlg@chromium.org, Apr 11 2018

Issue description

Coalesed Events pose complexity for event timing. On deciding the start time in Event Timing for coalesed events, we should use the start time of the coalesced events. getCoalescedEvents API provides a way for us to obtain the first event in coalesced events. However, the API is only availble for pointerEvent:
https://developer.mozilla.org/en-US/docs/Web/API/PointerEvent/getCoalescedEvents

We want to do the same for other event types upon the availability of getCoalescedEvents API for other event types.
 

Comment 1 by maxlg@chromium.org, Apr 11 2018

Description: Show this description

Comment 2 by maxlg@google.com, May 22 2018

Owner: maxlg@chromium.org
@tdresser, coalesced events is only defined for pointer event, right? 

The bug has been fixed for pointer event.
https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/timing/event_timing.cc?rcl=7a6e2a989d288dbf97884a6fe0a0d5d7f71259c9&l=54

If there is no plan to define other coalesced events, i would suggest closing this bug.
Status: Fixed (was: Assigned)

Sign in to add a comment