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 26596 - Attr.value cannot be readonly
Summary: Attr.value cannot be readonly
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: DOM (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
: 25086 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-08-18 12:09 UTC by Philip Jägenstedt
Modified: 2014-08-18 14:21 UTC (History)
7 users (show)

See Also:


Attachments

Description Philip Jägenstedt 2014-08-18 12:09:13 UTC
http://www.chromestatus.com/metrics/feature/timeline/popularity/299
http://www.chromestatus.com/metrics/feature/timeline/popularity/303

The use counters for the setter are a bit too high, even if only counting when actually attached to an element.

:(

Background:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21986#c9
Comment 1 Anne 2014-08-18 13:33:49 UTC
Also need to add Attr.prototype.textContent as alias per http://www.chromestatus.com/metrics/feature/timeline/popularity/349
Comment 2 Philip Jägenstedt 2014-08-18 14:06:40 UTC
First I think we should determine if making Attr not inherit Node and not have child nodes is going to fly. Unfortunately there are lots of APIs that expose the fact that Attr is a Node and has children, at least:

childNodes
firstChild
lastChild
insertBefore
replaceChild
removeChild
appendChild
hasChildNodes
cloneNode
normalize
contains

... and probably more. The best I can think of is to try to separate these into buckets AttrChildNodeAccess and AttrChildNodeModification and see if usage is low enough. Am I missing something?
Comment 3 Anne 2014-08-18 14:13:52 UTC
That seems correct. Whether Attr needs to be a Node we should probably track separately from whether Attr should have a settable value and textContent though. Would be really sad if that was required.
Comment 4 Anne 2014-08-18 14:17:38 UTC
*** Bug 25086 has been marked as a duplicate of this bug. ***