8046 2009-10-25 00:11:18 +0000 Reflecting floats: The IDL attribute types include +/-Infinity, so it doesn't make sense to talk about floats being "out of range" because everything is within the infinite range 2010-10-04 14:33:02 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other CLOSED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#reflecting-content-attributes-in-idl-attributes P3 normal LC 1 contributor ian excors ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 28942 0 contributor 2009-10-25 00:11:18 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#reflecting-content-attributes-in-idl-attributes Comment: Reflecting floats: The IDL attribute types include +/-Infinity, so it doesn't make sense to talk about floats being "out of range" because everything is within the infinite range Posted from: 212.183.134.209 28980 1 ian 2009-10-25 08:24:03 +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: Rejected Change Description: no spec change Rationale: What terminology would you suggest instead? 28987 2 excors 2009-10-25 09:07:38 +0000 I'd just remove all the range-related references, i.e. delete the phrases "and the value is in the range of the IDL attribute's type" and "or returns an out of range value". (I'm assuming the string "1e+400" will be converted into the floating point value Infinity, because that's how large values are meant to be handled in floating point, and assuming there should be no special handling for out-of-finite-range values here.) 28989 3 ian 2009-10-25 09:20:32 +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: Rejected Change Description: no spec change Rationale: None of the places that use this want infinite values — they all want finite values. I've made the spec explicitly exclude infinities from the "range" comment, but making numbers map to Infinity seems wrong, and would screw up the places that are using this. In fact, 1e+400 is not Infinity, it is infinitely far away from Infinity. 0 would be a better approximation, in terms of the absolute error (100% error if it was rounded to zero, ∞‬% error if it was rounded to infinity...).