Closed
Bug 579301
Opened 14 years ago
Closed 14 years ago
In Firefox window.statusbar.visible always returns true if status bar is hidden
Categories
(Core :: General, defect)
Tracking
()
People
(Reporter: saraltoms, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.2) Gecko/20100316 Firefox/3.6.2 Build Identifier: window.statusbar will return the statusbar object of the window. And window.statusbar.visible will return true, if the status bar is visible. The issue here is , even if the status bar is hidden in my current window, the window.statusbar.visible returns true. My requirement is to identify if the status bar is visible or hidden in firefox using javascript. Reproducible: Always Steps to Reproduce: 1.Open a URL in Firefox and enter. 2.Hide the status bar. 3.Open console and test window.statusbar.visible Actual Results: It returns true Expected Results: actual result is false. If we set false to window.statusbar.visible, the status bar is not hidden.Similarly if we set to true, the status bar is not visible.
Updated•14 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Since the HTML specifications suggests that window.statusbar.visible should return true when the statusbar is visible and false when the statusbar is hidden, it must be an essential parameter of the window object. If it is not feasible , please suggest how to identify if the status bar is hidden or visible in Firefox. In Safari, we are able to determine the existence of statusbar using window.statusbar.visible.
Comment 5•14 years ago
|
||
It may be possible to do from a web page in a web browser. It isn't possible in Firefox. If it's really important, you could write an extension that exposes this information to the web page.
Comment 6•14 years ago
|
||
> It may be possible to do from a web page in a web browser.
Er, read: It may be impossible to get the information about the browser's UI from a web page. It is in fact impossible in Firefox currently.
You need to log in
before you can comment on or make changes to this bug.
Description
•