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 8937 - setAttribute should specify the parameters (at least how many, but probably also a short description of each)
Summary: setAttribute should specify the parameters (at least how many, but probably a...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-10 11:09 UTC by contributor
Modified: 2010-10-04 14:33 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-02-10 11:09:11 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#apis-in-html-documents

Comment:
setAttribute should specify the parameters (at least how many, but probably
also a short description of each)

Posted from: 64.134.222.102
Comment 1 Ian 'Hixie' Hickson 2010-02-17 08:02:36 UTC 
Why just setAttribute()?

The reason the methods in that section aren't explicitly described is that they're defined in DOM Core and I didn't want to risk contradiction DOM Core (e.g. if DOM Core adds more arguments or something).
Comment 2 Ian 'Hixie' Hickson 2010-02-23 09:32:22 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: see comment 1.