410888 - Javascript popup

Status: RESOLVED FIXED

(Mozilla Labs :: Prism, defect)

Description

[Anders]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; da; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11
Build Identifier: Prism/0.8

I use this function to open a popup in prism;
function popUp(URL) {
day = new Date();
id = day.getTime();
eval("page" + id + " = window.open(URL, '" + id + "', 'toolbar=0,scrollbars=0,location=0,statusbar=0,menubar=0,resizable=0,width=200,height=300');")
};

When i create a profile and i runs for the first time the popup looks nice an has the correct size.

If i run the app from the desktop shortcut and use the exact same popup - it does not open in the desired size; it shows in full screen. Other javascript code works like close()... 

Reproducible: Always

Steps to Reproduce:
1. Make page that generates a small new popup window
2. Make a new shortcut on the desktop
3. The new page shows (just after creation) and the popup runs fine ie. with correct size
4. Open the shortcut from the desktop
5. the popup will show in "full" and not in the desired size
Actual Results:  
The popup will show in "full" and not in the desired size

Expected Results:  
Popup in correct size

Comment 1

[Dave Seymour-King]

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b4pre) Gecko/2008030208 Prism/0.9

This bug is still present in the above version:
function popwin(wname,url,w,h) {
    var sw = screen.width;var sh = screen.height;var left = (sw - w)/2;var top = (sh - h)/2;
    var siz = "width="+w+",height="+h+",top="+top+",left="+left+",screenX="+left+",screenY="+top
    siz += ",scrollbars,resizable";
    var wp=window.open(url, wname, siz);wp.focus();
}

Actual Results:
The popup seems to first attempt to honour the specified size and position then  resizes to the same size as the parent and  moves to an apparently arbitrary position on the desktop.

Expected results:
Prism should honour the specified size and position attributes for the popup.

Comment 2

[Matthew Gertner]

This should be fixed in 0.9.1. Please reopen if it isn't.