Bug 15207

Summary: get-set-properties test incorrectly classifies window.name as read-only
Product: WebKit Reporter: Matt Perry <mpComplete>
Component: Tools / TestsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: ahmad.saleem792, ap, bfulgham, oliver, rniwa, webkit-bug-importer
Priority: P3 Keywords: InRadar, LayoutTestFailure
Version: 523.x (Safari 3)   
Hardware: Mac   
OS: OS X 10.4   
Attachments:
Description Flags
Test window.name none

Matt Perry
Reported 2007-09-13 14:40:47 PDT
window.name should be read/write, and it is, but it is listed in this test as read-only. The test passes because the way we test whether a property can be set is incorrect, apparently.
Attachments
Test window.name (201 bytes, text/html)
2007-09-18 07:31 PDT, David Kilzer (:ddkilzer) 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
David Kilzer (:ddkilzer)
Comment 1 2007-09-18 07:25:19 PDT
Test: LayoutTests/fast/dom/Window/get-set-properties.html http://trac.webkit.org/projects/webkit/browser/trunk/LayoutTests/fast/dom/Window/get-set-properties-expected.txt#L244
David Kilzer (:ddkilzer)
Comment 2 2007-09-18 07:31:16 PDT
Created attachment 16310 [details] Test window.name
Vincent Ricard
Comment 3 2008-04-06 12:46:44 PDT
Is this bug still valid? According to http://trac.webkit.org/projects/webkit/browser/trunk/LayoutTests/fast/dom/Window/get-set-properties-expected.txt#L289 the property is listed at the right place, isn't it?
Ahmad Saleem
Comment 4 2022-07-25 17:02:43 PDT
I am unable to reproduce this bug in Safari 15.6 on macOS 12.5 and it shows "PASS: window.name is writable" in the test case and it matches with all other browsers (Chrome Canary 106 and Firefox Nightly 104). Is anything further needed here or this can be marked as "RESOLVED CONFIGURATION CHANGED". Thanks!
Radar WebKit Bug Importer
Comment 5 2022-07-25 17:56:19 PDT
<rdar://problem/97579134>
Note You need to log in before you can comment on or make changes to this bug.