New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 771367 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 777882
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature

Blocking:
issue 775030



Sign in to add a comment

Viz: Consider using frame tokens to update selection handles.

Project Member Reported by fsamuel@google.com, Oct 3 2017

Issue description

Currently selection handles are updated synchronously in RenderWidgetHostViewAura::SubmitCompositorFrame.

This obviously cannot work with Viz where frames are received in a different process.

Perhaps we can use the existing frame token mechanism to update selection? 

This will not synchronize with scroll but that isn't a concern currently because Chrome OS currently hides selection handles on scroll.

Android needs a better mechanism though.
 

Comment 1 by ericrk@chromium.org, Oct 11 2017

Labels: -Type-Bug Type-Feature
Status: Available (was: Untriaged)

Comment 2 by samans@chromium.org, Oct 16 2017

Frame token involves extra process hops and complicates the code so it should be avoided whenever possible. Frame token ensures that the parent doesn't get ahead of the child, but it can still fall behind. In fact, it will fall farther behind than if we weren't using frame token at all because of the delay caused by extra IPC. So unless getting ahead is considered worse than falling behind (which I don't think is the case for scroll data), I think we shouldn't use frame token.
Blocking: -730193 775030
Mergedinto: 777882
Status: Duplicate (was: Available)

Sign in to add a comment