On long pages with heavy content, the progress detection throbber sometimes spinning, which gives the perception the full page has completed loading the content. However, thats not always true, as if you try scrolling to the bottom, it seems as the content has paused loading. Eventually, the page continues to load content, but the throbber doesnt make that obvious. If a user tries to quickly kinectly pan to the bottom, the rubber band sling will bounce the page back to its clipped content. Progress indicator should continue to spin the throbber if the page is still loading. Example websites: techcrunch.com, icanhazcheeseburger.com Repro: 1) install Fennec 20111111 native nightly, samsung galaxy s 2 2) visit a webpage with long scrolling content (eg. URL) 3) watch progress detection spinner spin, but when it stops, pan to the bottom of the content. Verify the articles looks clipped and feels like there are more pages to come 4) if you wait for a bit... the rest of the page will load; but the initial throbber pausing makes it feel like the pageload was done Expected: - page throbber should continue until the page load is completed. or at least dont clip the content halfway through if page still needs loading.
The network is done. This seems to be a async scrolling bug. Should be fixed by pcwalton patches
Priority: -- → P2
Summary: Progress detection doesnt always detect the content has been fully loaded → Updating the unrendered area at bottom of a long page takes too long
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.