Bug 15207 - get-set-properties test incorrectly classifies window.name as read-only
Summary: get-set-properties test incorrectly classifies window.name as read-only
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 523.x (Safari 3)
Hardware: Mac OS X 10.4
: P3 Normal
Assignee: Nobody
URL:
Keywords: InRadar, LayoutTestFailure
Depends on:
Blocks:
 
Reported: 2007-09-13 14:40 PDT by Matt Perry
Modified: 2022-07-25 17:56 PDT (History)
6 users (show)

See Also:


Attachments
Test window.name (201 bytes, text/html)
2007-09-18 07:31 PDT, David Kilzer (:ddkilzer)
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Perry 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.
Comment 1 David Kilzer (:ddkilzer) 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

Comment 2 David Kilzer (:ddkilzer) 2007-09-18 07:31:16 PDT
Created attachment 16310 [details]
Test window.name
Comment 3 Vincent Ricard 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?
Comment 4 Ahmad Saleem 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!
Comment 5 Radar WebKit Bug Importer 2022-07-25 17:56:19 PDT
<rdar://problem/97579134>