Closed Bug 138405 Opened 24 years ago Closed 22 years ago

win010.html: Read window.name test: failed

Categories

(Core :: DOM: Core & HTML, defect)

Product:
Core
Component:
DOM: Core & HTML
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED DUPLICATE of bug 47280

People

(Reporter: aha, Assigned: jst)

References

(
URL
)

Details

2002041711/RC1/Win2K Description Pass Actual Result Expected Result Read window.name testmatrix failed testmatrix If this bug will be duplicate, update test to contain bug #.
Confirming this bug. Build ID 2002041814 - WinXP.
Assignee: rogerl → jst
Component: JavaScript Engine → DOM Level 0
QA Contact: pschwartau → desale
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
The page looks at window.opener for data, and that's null in this case... this is not meant to be loaded as a standalone test.
Marking Invalid per Boris' observation above. These tests were written to be driven by a parent HTML page -
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
This looks like a duplicate of bug 47280. (marking 'depends on' for now) See bug 47280 comment 9 about warning the users.
Depends on: 47280
Summary: Read window.name test: failed (win010.html) → win010.html: Read window.name test: failed
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
*** This bug has been marked as a duplicate of 47280 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago → 22 years ago
No longer depends on: 47280
Resolution: --- → DUPLICATE
.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.