Closed Bug 184459 Opened 22 years ago Closed 22 years ago

Dynamic resizing of the WORKAREA should update accordingly screen.avail* properties

Categories

(Core :: DOM: Core & HTML, defect)

x86
Windows XP
defect
Not set
minor

Tracking

()

VERIFIED DUPLICATE of bug 62395

People

(Reporter: bugzilla, Assigned: jst)

Details

(Keywords: dom0)

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 When resizing the WORKAREA (as defined by Microsoft at http://www.microsoft.com/winlogo/accessibility/WinXP_params2.asp), the correspondant DHTML properties used in NS 4 and higher should be updated in real time. screen.availWidth and screen.availHeight are updated in real time under MSIE 6 for Windows and Opera 7 beta 1; not so in Mozilla 1.2.1. This bug comes from a discussion on this issue in bug 162090 http://bugzilla.mozilla.org/show_bug.cgi?id=162090#c34 Reproducible: Always Steps to Reproduce: 1. Move the window taskbar to the left of the screen and dock it there 2. Open MS-Magnifier (should be at the top of the user screen) Actual Results: All of the DHTML screen property values screen.availLeft screen.availWidth screen.availTop screen.availHeight are not updated in real time. More precisely: screen.availLeft should be > 0 screen.availWidth should be smaller screen.availTop should be > 0 screen.availHeight should be smaller than before the relocation of taskbar and opening of MS-Magnifier. Expected Results: These property values should be updated in real time. References ========== screen.availHeight: Specifies the height of the screen, in pixels, minus permanent or semipermanent user interface features displayed by the operating system, such as the Taskbar on Windows. http://developer.netscape.com/docs/manuals/js/client/jsref/screen.htm#1193206 screen.availTop: Specifies the y-coordinate of the first pixel that is not allocated to permanent or semipermanent user interface features. coming from Client-Side JavaScript Reference v1.3 at http://developer.netscape.com/docs/manuals/js/client/jsref/screen.htm#1195107 http://www.bekkoame.ne.jp/~hamba/mozilla/screen/availLeft.html http://www.bekkoame.ne.jp/~hamba/mozilla/screen/availTop.html availHeight: Retrieves the height of the working area of the system's screen, excluding the Microsoft® Windows® taskbar. http://msdn.microsoft.com/workshop/author/dhtml/reference/properties/availheight.asp availWidth: Retrieves the width of the working area of the system's screen, excluding the Windows taskbar. Also, "About the screen.availTop and screen.availLeft properties: Reader Robin Berjon reports that in some instances, these properties are not zero, as stated on page 706. In Windows, if you move the Taskbar to the top of the screen, screen.availTop is 28, meaning that the first available top coordinate of the screen is 28; likewise, if you move the Taskbar to the left edge of the screen, screen.availLeft is 60. When the Taskbar is at the right or bottom of the screen, the properties return zero, because available space is flush with the top and left screen edges in those cases." can be found at the end of this page: http://www.dannyg.com/support/update5.html
This demo case will work for MSIE 6 for Windows and Opera 7 beta 1: note that these browsers will update in real time the screen.availWidth and screen.availHeight property values thanks to an resize event type on the window or document object. Mozilla 1.2.1 does not update in real time all of the screen.avail* property values: these properties are the coordinates and dimensions of the WORKAREA for applications. More details, instructions are given in the demo case.
Keywords: dom0
You searched for dups, eh? This only has 10-15 or so... ;) *** This bug has been marked as a duplicate of 62395 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
I thought the summary of bug 62395 involved the screen resolution and changing it. Maybe I saw and read the summary of bug 62395 and concluded that changing screen resolution will never ever change the screen.availLeft nor the screen.availTop values. Why should it? This bug 184459 is about resizing the WORKAREA. The WORKAREA can be modified a lot by just shifting, moving, resizing os-dependent applications around and that, without changing one pixel of the screen resolution. That is what the submitted demo case was enlightening. I'm repeating myself here.
verified.
Status: RESOLVED → VERIFIED
Component: DOM: Mozilla Extensions → DOM
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: