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 17705 - Getting unsigned long only returns values in the range 0 to 2^31-1, but setting allows 0 to 2^32-1. Why this assymetry?
Summary: Getting unsigned long only returns values in the range 0 to 2^31-1, but setti...
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-06 04:57 UTC by contributor
Modified: 2012-08-27 23:00 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2012-07-06 04:57:30 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/common-dom-interfaces.html
Multipage: http://www.whatwg.org/C#reflecting-content-attributes-in-idl-attributes
Complete: http://www.whatwg.org/c#reflecting-content-attributes-in-idl-attributes

Comment:
Getting unsigned long only returns values in the range 0 to 2^31-1, but
setting allows 0 to 2^32-1. Why this assymetry?

Posted from: 85.227.152.47 by simonp@opera.com
User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.7.3; U; en) Presto/2.10.229 Version/11.64
Comment 1 contributor 2012-07-18 17:57:20 UTC 
This bug was cloned to create bug 18283 as part of operation convergence.
Comment 2 Ian 'Hixie' Hickson 2012-08-27 22:22:00 UTC 
What do browsers do?
Comment 3 Ian 'Hixie' Hickson 2012-08-27 22:59:57 UTC 
To answer my question, there is sod-all interoperability here.

Anyway, turns out this was just an incomplete fix of bug 10352.
Comment 4 contributor 2012-08-27 23:00:34 UTC 
Checked in as WHATWG revision r7288.
Check-in comment: Finish fixing bug 10352.
http://html5.org/tools/web-apps-tracker?from=7287&to=7288