[f10s] Move content panning code into content process

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
9 years ago
9 years ago

People

(Reporter: mbrubeck, Assigned: mbrubeck)

Tracking

Details

(Assignee)

Description

9 years ago
Move the code in HTML/XUL overflow- and frame-scrolling code from Browser.MainDragger to an e10s-compatible content script.  It should pass a message back to chrome when all content elements are done scrolling, so the remaining scroll offset can be applied to chrome elements.
(Assignee)

Updated

9 years ago
Blocks: 579628
I think content scrolling will still happen in chrome. Bug 570620 is part of the solution for panning.
We might change this bug to "Use new shadow layers system to do panning and zooming in Fennec chrome"
tracking-fennec: --- → ?
We do not want any panning/scrolling code in the content process. Closing this bug.
Status: ASSIGNED → RESOLVED
tracking-fennec: ? → ---
Last Resolved: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.