Closed Bug 272459 Opened 20 years ago Closed 20 years ago

enabling Full Screen mode with no open window results in blank window covering entire desktop

Categories

(Firefox :: General, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

()

RESOLVED INVALID
Firefox1.5

People

(Reporter: netknightx, Assigned: bugzilla)

Details

(Keywords: polish)

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

After closing all open windows, going to the menu -> View -> Full Screen results
in a large white window covering the entire desktop (menu remains visible though).

In addition, going to menu -> Toolbars, shows a submenu that only has a divider
and Customize... option (no Navigation Toolbar or Bookmark Toolbar).

To remove the white screen, go to menu -> View -> Full Screen again.

Reproducible: Always
Steps to Reproduce:
1. Close all browser windows.
2. Go to the menu -> View -> Full Screen

Actual Results:  
A blank window/screen with no controls covered the entire desktop.

Expected Results:  
With no windows open, the Full Screen option should be greyed out or a new
window in Full Screen mode should open.
Confirmed in the trunk (0.9.1+)
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a6) Gecko/20041129
Firefox/0.9.1+
Should be a pretty simple thing to disable the menu item if there's no open windows.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: polish
Target Milestone: --- → Firefox1.1
(In reply to comment #2)
> Should be a pretty simple thing to disable the menu item if there's no open
windows.

well, not that simple (by the way, it isn't just fullscreen) it requiers a
rewrite of hiddenWindow.xul which is pretty broken lately (it just inlcudes
b'-menubar.inc, b'-sets, b'.js).
the "full screen" menu item is disabled now (when no window is open).
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.