Closed Bug 304083 Opened 19 years ago Closed 14 years ago

middle click on back doesn't use bfcache

Categories

(Firefox :: Tabbed Browser, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 271851
Firefox 3.7a1

People

(Reporter: ivan.icin, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050807 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050807 Firefox/1.0+

With bfcache enabled, back should be blazingly fast. But if you middle-clik on
back, new tab is reloaded again, not taken from the cache.

Reproducible: Always

Steps to Reproduce:
0. Enable bfcache
1. Go to page 1
2. Go to page 2
3. Middle click back

Actual Results:  
Page 1 is reloaded in new tab

Expected Results:  
Page 1 should be taken from the cache

This might be Core bug, but I think that it is not.
I'm really not sure if we could do this, bug I'll add it to the dependency list
of bug 236107 and see if anyone weighs in.
Status: UNCONFIRMED → NEW
Component: Toolbars → History: Session
Ever confirmed: true
OS: Windows XP → All
Product: Firefox → Core
QA Contact: toolbars → history.session
Hardware: PC → All
Version: unspecified → Trunk
Depends on: 236107
Depends on: blazinglyfastback
No longer depends on: 236107
Depends on: 271851
No longer depends on: blazinglyfastback
See bug 298571, comment 9:
"Actually, the clone window extension seems to do approximately what is wanted here:
http://extensionroom.mozdev.org/more-info/clonewindow"
Why is this a core bug?  This is just bug 271851 in another guise.  Core has no idea that history is involved in any way here -- it's just told to do a load of a URI, and does it...  
Component: History: Session → General
Product: Core → Firefox
QA Contact: history.session → general
dup to bug 448546
Component: General → Tabbed Browser
QA Contact: general → tabbed.browser
Target Milestone: --- → Firefox 3.7a1
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.