8598 2010-01-03 19:11:08 +0000 API return values listed as upper case, should be lowercase? 2010-10-04 13:57:53 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC Windows NT RESOLVED NEEDSINFO http://dev.w3.org/html5/spec/Overview.html#apis-in-html-documents P2 normal --- 1 brutzman ian annevk brutzman hsivonen ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 30330 0 brutzman 2010-01-03 19:11:08 +0000 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? 30347 1 hsivonen 2010-01-04 07:57:31 +0000 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. 30456 2 annevk 2010-01-05 07:18:48 +0000 We should probably add a note to make that clear. 30661 3 ian 2010-01-06 12:07:07 +0000 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?