Open Bug 452621 Opened 16 years ago Updated 2 years ago

only one back/forward history "recent pages" dropdown works if several on toolbars

Categories

(Firefox :: General, defect)

x86
Linux
defect

Tracking

()

People

(Reporter: tuukka.tolvanen, Unassigned)

Details

20080826020557 Minefield/3.1a2pre on linux

steps:
 1. open new fx window
 2. use location bar to go to http://www.mozilla.org/
expected:
 back button enabled, dropdown enabled
results:
 back button enabled, dropdown remains disabled
(In reply to comment #0)
> steps:
>  1. open new fx window
>  2. use location bar to go to http://www.mozilla.org/

This assumes you have a home page that isn't about:blank, presumably?

I can't reproduce this - the dropdown is updated correctly for me.
Component: Places → General
QA Contact: places → general
> >  2. use location bar to go to http://www.mozilla.org/
> 
> This assumes you have a home page that isn't about:blank, presumably?

Anything that isn't http://www.mozilla.org/ should do; mine is about:

Turns out I have two back-forward-dropdown sets -- someone's stealthily added one in the hidden (or removed "Navigation Toolbar" where the dropdown works; and the one that doesn't work is on a "whateverbar". Toolbar customization appears to be broken (20080828020858 Minefield/3.1a2pre) so testing in another profile if the problem is the number of shistory dropdowns (likely I suppose) or the bar it sits on (less likely I suppose) is a bit challenging atm.

I don't know who put the back-forward-dropdown item on the hidden "Navigation Toolbar", but I guess it wasn't me since afair it's not possible to have more than one via the ui ;)

Looking at the screenshots of earlier cases where multiple back-forward-dropdown items have appeared, only one dropdown is enabled if any.
Summary: back/forward history recent pages dropdown always disabled → only one back/forward history "recent pages" dropdown works if several on toolbars
May be similar to bug 453088, "recent pages" doesn't work in spawned pages.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.