Closed Bug 901339 Opened 11 years ago Closed 11 years ago

Panning & zooming does still not work well on Browser after bug 866232


(Core :: Graphics: Layers, defect)

25 Branch
Gonk (Firefox OS)
Not set





(Reporter: julienw, Assigned: kats)




(1 file)

I tried applying patches in bug 899810 and bug 900742 but zooming/panning on is still wrong:

* sometimes it just doesn't work
* sometimes the gesture to panning does zooming instead
* when zooming, the focal point is also still not right
(In reply to Julien Wajsberg [:julienw] from comment #0)
> * sometimes the gesture to panning does zooming instead

This one should be fixed by bug 898443. I will look into the other two parts of this.
Blocks: 866232
Depends on: 898443
No longer depends on: 866232
Version: 22 Branch → 25 Branch
Assignee: nobody → bugmail.mozilla
I have repro steps for this bug:

1. Launch the browser and navigate to a site, espacially one with lots of content (eg
2. Scroll down and up the page.

The page will eventually freeze and become unresponsive, forcing the user to close the browser completely and reload it.  The length of time varies, but it's never more than a minute.
Attached patch PatchSplinter Review
This fixes a screwup on my part in bug 866232, part 8 ( The original code had mFrameMetrics.mScrollOffset multiplied by "paintedScale" which was actually the CSSToLayerScale of the painted frame metrics rather than the APZC's internal frame metrics. In my refactoring I accidentally changed it to use the APZC's internal frame metrics instead. This fixes that and also factors out the multiplication.
Attachment #786955 - Flags: review?(bgirard)
:bbondy, can you also verify if the attached patch fixes the focal point when zooming for you?
Comment on attachment 786955 [details] [diff] [review]

Review of attachment 786955 [details] [diff] [review]:

Yes this works a million times better now :)
Attachment #786955 - Flags: review?(bgirard) → review+
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla26
Blocks: 903498
You need to log in before you can comment on or make changes to this bug.