Closed
Bug 181436
Opened 23 years ago
Closed 23 years ago
Incorrect window borders appear during window.open()
Categories
(SeaMonkey :: UI Design, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: sinchi, Assigned: samir_bugzilla)
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021121
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021121
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021121
When I open window by JavaScript window.open function, I see opened window
without borders and borders separately with inproper size and position.
See testcase.
Reproducible: Always
Steps to Reproduce:
JS Console report:
Error: uncaught exception: [Exception... "" nsresult: "0x804b0012 (<unknown>)"
location: "JS frame ::
http://bugzilla.mozilla.org/attachment.cgi?id=107134&action=view :: show :: line
41" data: no]
Oh, sorry, line 41 contains:
windowObjectRef.location=stringValue;
Removing this line supresses exception, but bug still persists.
windowObjectRef.location=stringValue
is correct construction. And even windowObjectRef.location.href= causes the same
exception. Should I fill another bug for this?
Comment 4•23 years ago
|
||
not JS engine.
Assignee: rogerl → sgehani
Component: JavaScript Engine → XP Apps
QA Contact: pschwartau → paw
Comment 5•23 years ago
|
||
Worksforme in a current win2k trunk build. I don't see a problem with window
borders, although I'm not clear on exactly what you are trying to describe.
Perhaps a screenshot attached to this bug would help.
Note 1: the JS error occurs if you specify no URL, so effectively you do
|window.location = "";|, which is an error (and you should get an alert dialog).
Note 2: as far as I know, mozilla does not support the 'fullscreen' windowfeature
string in the window.open call.
Fixed in 1.2 release. All is OK.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Updated•21 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•