Closed Bug 424763 Opened 17 years ago Closed 17 years ago

Print preview loses navigation buttons

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED FIXED

People

(Reporter: nhickman, Unassigned)

Details

(Keywords: qawanted, regression)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5pre) Gecko/2008032005 Minefield/3.0b5pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5pre) Gecko/2008032005 Minefield/3.0b5pre From any website, click file->print preview. This opens the preview in the same tab. If I change any aspect of the printing (landscape/portrait or zoom) and then close the preview I lose the back buttons and also the alt + left arrow navigation. The History->back menu still works. This was tested on: 2008032005 Minefield/3.0b5pre 2008032305 Minefield/3.0b5pre Reproducible: Always Steps to Reproduce: 1. Visit two websites in the same tab. 2. Click the File menu then Print preview while on the new website. 3. Change something like portrait or landscape or zoom levels. 5. Click the close button. 6. Try clicking the now disabled back button or alt+left arrow to go back to the old website. Actual Results: Back button is disabled and so is the alt + left arrow functionality. Clicking on History->back in the file menu still works. Expected Results: Navigation to still be enabled to go back to the source website. Default everything.
Severity: normal → major
Running 2008060709 Minefield/3.0pre and it is still doing it!
Flags: blocking-firefox3?
Flags: blocking-firefox3.1?
Getting a regression range and a confirmation would help. Doesn't block the final ship of Firefox 3.
Component: Menus → General
Flags: blocking-firefox3?
Keywords: qawanted, regression
QA Contact: menus → general
Found this bug to be related to IE Tab plugin. After disabling the plug-in then exiting print preview the navigation works as expected.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Flags: blocking-firefox3.1?
You need to log in before you can comment on or make changes to this bug.