Closed
Bug 138402
Opened 22 years ago
Closed 21 years ago
In <win011.html> JavaScript Testcase (failed): 'window.opener' return value is incorrect when run not from 'window.html' page (or in a new Tab)
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: aha, Assigned: jst)
References
()
Details
2002041711/RC1/Win2K Description Pass Actual Result Expected Result Read window.opener null failed null [object Window] If this bug will be duplicate, morph it to update test to contain bug #.
Comment 1•22 years ago
|
||
Same result on Linux RC1
Comment 2•22 years ago
|
||
Browser, not engine ---> DOM Level 0. I'm not familiar with how these tests are run. Can they be run as standalone URLs, or do they have to be run from a test driver URL? It doesn't seem to pass in IE6, either, when I run it as a standalone
Assignee: rogerl → jst
Component: JavaScript Engine → DOM Level 0
QA Contact: pschwartau → desale
Comment 3•22 years ago
|
||
window.opener can only be non-null if the window got opened via window.open(). If you just load that url, that is not the case. This test is not meant to run standalone.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
Comment 4•21 years ago
|
||
[Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.4a) Gecko/20030401] Confirming comment 3: *Click on link in <http://mozilla.org/quality/browser/standards/javascript/tcmatrix/window.html>: passed :-) *Click on link in this bug report: failed ('Actual Result' is 'null') :-( Could a warning be added to the bug source, or "Bug report required" replaced by "Bug# 138402" to point to this explanation ? Also, this testcase opens a new window: please add a warning. (see also bug 142649 comment 3, for this and the "new Tab" issue) Should this bug be reopened ?
Blocks: 142649
Summary: window.opener test: failed (win011.html) → In <win011.html> JavaScript Testcase (failed): 'window.opener' return value is incorrect when run not from 'window.html' page (or in a new Tab)
Comment 5•21 years ago
|
||
I added this bug as reference for that testcase when it fails. Should be ok now. VERIFIED invalid.
Status: RESOLVED → VERIFIED
Comment 6•21 years ago
|
||
Re comment 5: Changing: (S) V.Invalid -> "Reopen" Could you add a warning too, as you did for bug 47280: { this test is designed to be run from the main test window } Then resolve it as "Fixed". Thanks !
Status: VERIFIED → UNCONFIRMED
Resolution: INVALID → ---
Updated•21 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•21 years ago
|
Comment 7•21 years ago
|
||
Added the warning. Fixed for real this time.
Status: NEW → RESOLVED
Closed: 22 years ago → 21 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•