10380 2010-08-16 23:19:52 +0000 Description of IDL sets for enumerated attributes does not appear to match reality 2010-10-04 14:46:34 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other CLOSED FIXED http://www.whatwg.org/specs/web-apps/current-work/#reflecting-content-attributes-in-idl-attributes P3 normal --- 1 contributor ian ayg ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 37533 0 contributor 2010-08-16 23:19:52 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#reflecting-content-attributes-in-idl-attributes Comment: "the content attribute must be set to the conforming value associated with the state that the attribute would be in if set to the given new value". Does this imply in canonical case? Browsers seem to preserve the case when you do an IDL set. This alerts "tExT" in Firefox, Chrome, and Opera: data:text/html,<!doctype html><script>var el = document.createElement("input"); el.type = "tExT"; alert(el.getAttribute("type"));</script> Posted from: 68.175.61.233 37534 1 ayg 2010-08-16 23:26:52 +0000 Don't forget to say what happens to case if you set the IDL attribute to a non-conforming value. Then presumably you'd need to use canonical case. I don't think any browser actually limits any enum with non-conforming values to known values only -- the only one of those seems to be area.shape, and Firefox/Chrome/Opera seem not to limit it to known values -- so I guess you'll have to make something up there. 39087 2 ayg 2010-09-17 18:01:35 +0000 The simple way to fix this would be to just change """ on setting, if the new value is an ASCII case-insensitive match for one of the keywords given for that attribute, then the content attribute must be set to the conforming value associated with the state that the attribute would be in if set to the given new value, otherwise, if the new value is the empty string, then the content attribute must be removed, otherwise, the content attribute must be set to the given new value. """ to """ on setting, the content attribute must be set to the given new value. """ This seems to match what browsers do a lot more closely. I don't notice browsers implementing the magic behavior required for the empty string, either. 39826 3 ian 2010-09-28 23:10:45 +0000 Looks like you're right. The only browser I could find that does the empty string thing is Chrome, which removes the attribute for <input type> and e.type = ''. Other than that you seem right. 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: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. 39827 4 contributor 2010-09-28 23:11:24 +0000 Checked in as WHATWG revision r5537. Check-in comment: Match UAs better for 'limited to known values' reflection. http://html5.org/tools/web-apps-tracker?from=5536&to=5537