Closed Bug 598391 Opened 11 years ago Closed 11 years ago
Page does not update and panning/clicking is incorrect after scrolling by content
Steps to reproduce: 1. Open the attached test case. 2. Click on "test 1" which uses href=#bottom, or "test 2" which uses scrollTo. Expected results: The page pans to the bottom, where you can see the text "bottom" Actual results: The page fail to repaint (gray screen), and you can still get a tap highlight or contextmenu by tapping on the screen where the "test 1" and "test 2" links used to be.
Comment on attachment 477228 [details] [diff] [review] listen for scroll events There still seems to be a platform bug, looking into it.
Attachment #477228 - Flags: review?(mbrubeck)
Comment on attachment 477228 [details] [diff] [review] listen for scroll events The code is fine here, though it's hard to tell if it's correct until we pin down the platform behavior.
Attachment #477228 - Flags: review?(mbrubeck) → review+
With the dependency bug, things seems to work perfectly.
I noticed one problem with these patches: If the urlbar or sidebars are showing when the scroll happens, then they remain there after the scroll, even if the page scrolls away from the top or sides. Here's a fix for that problem.
Attachment #477528 - Flags: review?(webapps)
Comment on attachment 477528 [details] [diff] [review] part 2: Hide browser chrome on scroll r+ (without the dump of course)
Attachment #477528 - Flags: review?(webapps) → review+
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
verified FIXED on builds: Mozilla/5.0 (Maemo; Linux armv71; rv:2.0b6pre) Gecko/20100924 Namoroka/4.0b7pre Fennec/2.0b1pre and Mozilla/5.0 (Android; Linux armv71; rv:2.0b6pre) Gecko/20100924 Namoroka/4.0b7pre Fennec/2.0b1pre
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.