Closed Bug 417762 Opened 12 years ago Closed 12 years ago

Back button takes 2 clicks to go back one page in gmail when previously linking from igoogle

Categories

(Firefox :: General, defect, minor)

x86
All
defect
Not set
minor

Tracking

()

RESOLVED FIXED

People

(Reporter: dmistofsky, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3) Gecko/2008020514 Firefox/3.0b3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3) Gecko/2008020514 Firefox/3.0b3

Tested on several different machines, one w/ XP Pro and one w/ Vista from different physical locations.  When logged into igoogle, click into gmail from the standard included gmail gadget by clicking either "GMAIL" or "Inbox".  Once in gmail, attempt to click back once to go back one page but it will not take you back, rather it takes two clicks on the back button to go back one page to igoogle.  When clicking back once, firefox provides the green highlighted forward button as if you have gone back one page even though you haven't.  Easy to duplicate.

Reproducible: Always

Steps to Reproduce:
1. Log into google
2. Switch ti igoogle
3. Click on the "GMAIL" or "Inbox" link part of the gmail gadget to go into your gmail client
4. Try hitting the "Back" button 1 time, see if you go back to igoogle.

Actual Results:  
* Notice 2 clicks on back button takes you back 1 page*
* Notice 1 click provides option to go forward 1 page even though you have gone nowhere*

Expected Results:  
Should have gone back to igoogle page w/ 1 click like any other page
Yeah, I see this as well, and it doesn't just take two clicks, you actually have to quickly double click on the back button to get you back.
Happens the same to me... exactly the same, on windows XP and with the latest firefox..
Depends on: 386782
Version: unspecified → Trunk
Fixed by patch for bug 430624.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.