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 8598 - API return values listed as upper case, should be lowercase?
Summary: API return values listed as upper case, should be lowercase?
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://dev.w3.org/html5/spec/Overview...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-03 19:11 UTC by Don Brutzman
Modified: 2010-10-04 13:57 UTC (History)
7 users (show)

See Also:


Attachments

Description Don Brutzman 2010-01-03 19:11:08 UTC
3.3 APIs in HTML documents

states
        Element.tagName and Node.nodeName
        These attributes must return element names converted to
        ASCII _uppercase_, regardless of the case with which they
        were created.

and then
        The canonical form of HTML markup is all-lowercase;

also in section 3.3 APIs in HTML documents
        when looking at HTML elements, the argument must first be
        converted to ASCII lowercase

This seems inconsistent.  Should the first _uppercase_ instead be lowercase?
Comment 1 Henri Sivonen 2010-01-04 07:57:31 UTC
The spec text is correct here. The DOM-internal form is lower case. Hence, the setter lower cases. For legacy reasons, .tagName and .nodeName need to return in upper case.
Comment 2 Anne 2010-01-05 07:18:48 UTC
We should probably add a note to make that clear.
Comment 3 Ian 'Hixie' Hickson 2010-01-06 12:07:07 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: Did Not Understand Request
Change Description: no spec change
Rationale: I would be happy to add a note explaining this, but it's not clear exactly where the note should go or what it should say. Don, could you clarify where in the spec it was you were reading when you first thought there was a mistake?