291270 - Setting window.innerWidth (js) causes window to be positioned back to the original position

Status: RESOLVED EXPIRED

(Firefox :: Shell Integration, defect)

Description

[Philipp Ringli]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 StumbleUpon/1.9994
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 StumbleUpon/1.9994

This bug only shows on OS X.

This function is called in the body tag (onload):

function wiggle() {
	window.innerWidth +=1; 
	window.innerWidth -=1;
}

I also tested this issue on FF 1.0.3 on Windoze XP and none of the issues I'm
having on OS X occur.

Reproducible: Always

Steps to Reproduce:
1. open http://workloft.ch/ueberuns/
2. change the windows position
3. klick any other link on that page

Actual Results:  
The window doesn't stay at the current position. It moves back to where it has
ben originally opened.

Expected Results:  
The window's position should not be influenced by setting window.innerWidth nor
window.innerHeight.


I had to use this hack (i.e. the wiggle()) to circumvent a problem in Firefox
wich has to do with adjusting the height of divs, after content has been loaded
into them (like pictures, that need most time to load).
When content is loaded into .contentHolder and the content contains images,
which load after the page has been rendered, #logoMenu 's height is not adjusted
correctly. One has to resize the window to get FF to adjust the #logoMenu's height.
This problem can be seen, when turning off js, emtpying the cache and loading
http://www.workloft.ch/standorte/schoenenberg/

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.