Closed
Bug 283326
Opened 20 years ago
Closed 20 years ago
screen.availWidth not updated
Categories
(Toolkit Graveyard :: Error Console, defect)
Tracking
(Not tracked)
People
(Reporter: matthew, Assigned: bugs)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
<script type='text/javascript'>
<!--
document.write("<br>"+screen.width+'x'+screen.height+' '+screen.availwidth);
//-->
</script>
Reproducible: Always
Steps to Reproduce:
1.Stick this code in a web page
2.Browse to the page. Observe.
(If this doesn't reproduce the bug, change your screenmode and refresh the page.)
Actual Results:
1280x1024 undefined
Expected Results:
1280x1024 1280 (as observed in IE)i think you forget to shift your W
| Reporter | ||
Comment 2•20 years ago
|
||
You are right - it works better with "screen.availWidth" - Firefox recognises this (IE wrongly recognises screen.availwidth) ===HOWEVER=== I found "screen.availWidth" didn't work properly in Firefox either. Try this: Change the code to "screen.availWidth" [Refresh] the page Change the screenmode Browser [Back] and [Forwards], across links on your page, and back to the page with this code on it again. Oops! "screen.availWidth" doesn't reflect the new screenmode. You must actually "Refresh" the browser window to make Firefox report the new screenmode. I will try strengthening my code (belt & braces) with the "window.onResize" event, and see what happens.
Updated•20 years ago
|
Severity: minor → normal
Summary: screen.availwidth undefined → screen.availWidth not updated
Whiteboard: dupeme?
Comment 4•20 years ago
|
||
*** This bug has been marked as a duplicate of 62395 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Status: RESOLVED → VERIFIED
Updated•16 years ago
|
Product: Firefox → Toolkit
Updated•8 years ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•