Open
Bug 646474
Opened 15 years ago
Updated 3 years ago
When printing page, navigation data is erased, cannot go back.
Categories
(Firefox :: Toolbars and Customization, defect)
Tracking
()
NEW
People
(Reporter: martinalejandrozudaire, Unassigned)
References
(
URL
)
Details
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0) Gecko/20100101 Firefox/4.0
When clicking on Full Page and then Print link, the history and navigation data gets erased. Cannot move backwards or forwards. I own an EPSON Stylus C79, never had a problem with drivers before. History and navigation data are set to be erased at the end of the session (when i close firefox).
Reproducible: Always
Actual Results:
click full page then click Print link.
Expected Results:
printing came out fine, but history was deleted.
i should have been able to go back if i wanted.
Mozilla/5.0 (Windows NT 6.1; rv:2.2a1pre) Gecko/20110330 Firefox/4.2a1pre
Works fine for me.
Does the issue still occur if you start Firefox in Safe Mode?
http://support.mozilla.com/en-US/kb/Safe+Mode
How about with a new, empty profile?
http://support.mozilla.com/en-US/kb/Basic+Troubleshooting#Make_a_new_profile
Updated•15 years ago
|
Version: unspecified → 4.0 Branch
I can confirm this with Firefox 4.0.1 on Linux. After printing the page (I choosed a PDF writer, hope it does not make a difference), the back/forward buttons really get disabled. However, after changing to other tab and back, the buttons become active and history works. Reporter, can you confirm this workaround?
I could not reproduce it with FF 5.0a2, maybe it is fixed. Reporter, can you try this version?
Status: UNCONFIRMED → NEW
Component: General → XP Toolkit/Widgets: Menus
Ever confirmed: true
Product: Firefox → Core
QA Contact: general → xptoolkit.menus
Version: 4.0 Branch → 2.0 Branch
Component: XP Toolkit/Widgets: Menus → Toolbars
Product: Core → Firefox
QA Contact: xptoolkit.menus → toolbars
Updated•3 years ago
|
Severity: minor → S4
You need to log in
before you can comment on or make changes to this bug.
Description
•