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 9634 - Most enumerated attributes are not limited to only known values
Summary: Most enumerated attributes are not limited to only known values
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://dev.w3.org/html5/spec/infrastr...
Whiteboard:
Keywords:
Depends on: 10289
Blocks: 9635 9636 9741
  Show dependency treegraph
 
Reported: 2010-05-01 15:12 UTC by Mounir Lamouri
Modified: 2010-10-04 14:30 UTC (History)
5 users (show)

See Also:


Attachments

Description Mounir Lamouri 2010-05-01 15:12:12 UTC
At the moment, according to the specs, if the IDL attribute of an enumerated attributes isn't limited to only known values, the IDL attribute should reflect the content attribute.
In most case, it sounds better to have the IDL attribute reflecting the current state instead of reflecting the content attribute. It would prevent the caller to guess the current state depending on the value. This is a lost of time and effort and it is clearly not future-proof.

At the moment, only three attributes are limited to only known values:
- document.dir
- keygen.keytype
- area.shape

Maybe other attributes could be limited to only known values ?
Even, couldn't we image having a different default: every IDL attribute of an enumerated attribute could be limited to only known value except if the opposite is specified. IMO, it sounds natural to have IDL attributes returning the current state instead of the content attribute value.
Comment 1 Ian 'Hixie' Hickson 2010-09-10 01:35:02 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: Accepted
Change Description: no spec change
Rationale: This seems to have been fixed already.
Comment 2 Ian 'Hixie' Hickson 2010-09-10 01:35:52 UTC
(Specifically, most are now so limited.)