Closed
Bug 292938
Opened 20 years ago
Closed 19 years ago
Slight hitch when using back/forward with bfcache/fastback
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: stevee, Unassigned)
References
Details
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050504
Firefox/1.0+ after landing of bug 274784
browser.sessionhistory.max_viewers 20
1. New profile, start firefox.
2. Open a page. eg: www.neowin.net
3. Click on a link so the new page loads in the same tab (eg: the Forums link)
4. Click back arrow
5. Click refresh
6. Click forwards
7. Click back
Notice when you click back on step 7 that there is a slight hitch before the
page renders. I don't think this is expected.
Comment 1•20 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050504
Firefox/1.0+ 18:08 pdt
confirming
this is caused by the ad system neowin uses, the intellitext or whatever its
called. You can see the address in the bar while the page is rendering.
Reporter | ||
Comment 3•20 years ago
|
||
No, it happens on all pages. eg:
1. Load https://bugzilla.mozilla.org/show_bug.cgi?id=292938
2. Click on 'Search page' at the top left.
3. Click back.
4. Click refresh.
5. Click forward
6. Click back.
There's a hitch when doing step 6.
Updated•19 years ago
|
Summary: Slight hitch when using back/forward → Slight hitch when using back/forward with bfcache/fastback
Comment 4•19 years ago
|
||
This sounds exactly like the problem I fixed in my checkin for 292954 and
292950, where we were examining the wrong load type when deciding whether the
presentation in cacheable. Because of the refresh, we would fail to cache the
page when going forward in step 6 (of the original report).
Marking FIXED.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 5•19 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b3) Gecko/20050710
Firefox/1.0+ ID:2005071017
This is indeed fixed for me too.
Status: RESOLVED → VERIFIED
Component: History: Session → Document Navigation
QA Contact: history.session → docshell
You need to log in
before you can comment on or make changes to this bug.
Description
•