Issue metadata
Sign in to add a comment
|
Viz: Consider using frame tokens to update selection handles. |
||||||||||||||||||||||||
Issue descriptionCurrently 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.
,
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. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ericrk@chromium.org
, Oct 11 2017Status: Available (was: Untriaged)