Closed Bug 761096 Opened 13 years ago Closed 13 years ago

Don't preload history in new tab

Categories

(Firefox :: Tabbed Browser, defect)

13 Branch
x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: cmhofman, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0) Gecko/20100101 Firefox/13.0 Build ID: 20120601045813 Steps to reproduce: Open a new tab Actual results: A tab with some items from the history is opened. When I load another page in it, the initial tab remains in its history. Expected results: An *empty* tab should be opened, and when I load an actual page in that tab that page (and not the initial junk) should be the first item in the history of that tab. At the least, this should be controlled in the preferences if continued.
Component: Untriaged → Tabbed Browser
(In reply to Christiaan Hofman from comment #0) > At the least, this should be controlled in the preferences if continued. Did you mean like at about:config?filter=browser.newtabpage.enabled or in the UI?
(In reply to Christiaan Hofman from comment #0) > when I load an actual page in that tab > that page (and not the initial junk) should be the first item in the history > of that tab. This is bug 724239
(In reply to Mardeg from comment #1) > (In reply to Christiaan Hofman from comment #0) > > At the least, this should be controlled in the preferences if continued. > Did you mean like at about:config?filter=browser.newtabpage.enabled or in > the UI? UI is bug 729063
(In reply to Christiaan Hofman from comment #0) > Expected results: > > An *empty* tab should be opened The decision to turn this on by default was in bug 716538. So far the triage options for this bug are: 1. Resolve WONTFIX due to bug 716538 2. Resolve DUPLICATE of bug 724239 3. Resolve DUPLICATE of bug 729063 4. Resolve INVALID for not keeping to a single issue.
Resolving as INVALID as all the reported problems are tracked as individual bugs.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.