New issue
Advanced search Search tips

Issue 708520 link

Starred by 1 user
Status: Assigned
Owner:
nzolghadr@chromium.org
Cc:
dtapu...@chromium.org
tdres...@chromium.org
Components:
EstimatedDays: ----
NextAction: 2018-06-28
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

LatencyInfo not populated correctly on Mac

Project Member Reported by tdres...@chromium.org, Apr 5 2017 
In RenderWidgetHostViewMac, we aren't correctly assigning the LatencyInfo's original component to the timestamp from the NSEvent.

Comment 1 by tdres...@chromium.org, Oct 3 2017

Cc: nzolghadr@chromium.org dtapu...@chromium.org tdres...@chromium.org
Owner: ----
Status: Available (was: Assigned)
Dave, do you think someone on the input team could take this?

Comment 2 by dtapu...@chromium.org, Oct 3 2017

Labels: -Pri-3 Pri-2
Owner: dtapu...@chromium.org
Status: Assigned (was: Available)

Comment 3 by mfomitchev@chromium.org, Nov 21 2017

Cc: -mfomitchev@chromium.org

Comment 4 by dproy@chromium.org, Mar 15 2018 

Bug triage ping: no update in the last 100 days. 

Any update on this?

Comment 5 by nzolghadr@chromium.org, Mar 19 2018

Cc: -nzolghadr@chromium.org
Owner: nzolghadr@chromium.org
Let me park this on my plate.

Comment 6 by npm@chromium.org, Jun 27 2018 

Is this still an issue? This was changed from Pri3 to Pri2 but no updates in a while.

Comment 7 by nzolghadr@chromium.org, Jun 27 2018

NextAction: 2018-06-28
Tim, what part were you referring to at the time that you filed the bug?
We do seem to be setting the timestamp from the timestamp of the NSEvent:
https://cs.chromium.org/chromium/src/content/browser/renderer_host/input/web_input_event_builders_mac.mm?type=cs&sq=package:chromium&g=0&l=335

Let me know if you had something else in mind.

Comment 8 by tdres...@chromium.org, Jun 27 2018 

Sorry, should have linked to the code...

I might have been thinking of:
https://cs.chromium.org/chromium/src/content/browser/renderer_host/render_widget_host_view_mac.mm?rcl=f248c98b766e21597b584faef1dee3b6f66137f8&l=1444

We set the UI_COMPONENT but not the ORIGINAL_COMPONENT.

Comment 9 by monor...@bugs.chromium.org, Jun 28 2018 

The NextAction date has arrived: 2018-06-28

Comment 10 by npm@chromium.org, Nov 26 

Ping! This bug has been flagged as stale by Chrome Speed Metrics bug triage, and it has an owner. Any update on this issue?
►

Sign in to add a comment