Closed
Bug 274458
Opened 20 years ago
Closed 20 years ago
Print Preview will not close
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: kopelli, Assigned: bugzilla)
Details
When clicking Print Preview to view a web page before printing, everything loads fine. The Close button however seems to not be workings. It could be one of my plugins, so here's what I have installed at the time I noticed the error: tabextensions_en.xpi tabprefs_0.6.14.xpi textlink.xpi Adblock v.5 d2 * nightly 39 Plain Text Links 0.2 Tabbrowser Extensions 1.11.2004110502 Even when I switch between tabs, it's still in print preview mode. The only way to get out of it is to restart the browser.
Comment 1•20 years ago
|
||
"Preview Mode" seems to be confused when/after starting the "Print" dialog.
This behaviour is reproducable with following steps:
1. Open one (or more) tabs, follow at least one link so you have a page
you can go back by ALT+LEFT.
2. Start Print Preview (Menu: File -> Print Peview).
3. Start "Print" Dialogue (click [Print] buttom or press ALT+P).
4. Now you can back out with pressing ESC (or click Cancel])
or you may start a real print - the result will be the same.
5. Once the Print Dialogue is away, while still in Preview Mode,
press ALT+LEFT = page backward or if applicable: ALT+RIGHT = page forward.
6. Press ESC or click [Close] buttom - the browser shows the web page(s)
in normal mode (incl. tabs) ...
7. But the TOP of the Window still shows the Preview Toolbar
instead of the Menu bar, Navigation bar, Bookmark Toolbar, etc.
My conclusion is that there is some internal "status", "flag" or "pointer"
changed during step 3 (start and/or return from Print dialogue).
This change makes the browser to accept ALT+LEFT or ALT+RIGHT when
coming back from the Print dialogue but while still being in Preview Mode.
------------------------------------
Running Firefox 1.0 on WinNT4 :
Mozilla/5.0 (Windows; U; WinNT4.0; rv:1.7.3) Gecko/20041001 Firefox/0.10.1)
------------------------------------
In the setting of the standard, this problem never occurs. Perhaps, installed Extensions does the conflict.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•