This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 257 - Setting nodeValue when defined as null on a readonly node
Summary: Setting nodeValue when defined as null on a readonly node
Status: RESOLVED WONTFIX
Alias: None
Product: DOM TS
Classification: Unclassified
Component: DOM Level 1 (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: Curt Arnold
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-29 18:22 UTC by Curt Arnold
Modified: 2003-07-18 09:37 UTC (History)
0 users

See Also:

Attachments

Description Curt Arnold 2003-06-29 18:22:59 UTC 
From http://lists.w3.org/Archives/Public/www-dom-ts/2003Jun/0005.html

David Clover wrote:
 ---  Python discussion ---
Anyway, the imp passes L1 modulo the setting-a-readonly-node's-nodeValue-
when-it-is-defined-as-null tests, where I simply cannot agree with the TS's
strange interpretation of the spec.
 -- other bug --

Curt Arnold writes:

Would be good to double check that the tests under question actually reflect the
WG's intentions and adequately document the relavant statements.
Comment 1 Andrew Clover 2003-07-18 05:37:30 UTC 
The latest L3 Core draft codifies TS's interpretation of nodeValue setting on a 
read-only attribute, so I no longer object to it.