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 13597 - Remove reverse attribute from ol
Summary: Remove reverse attribute from ol
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-03 08:26 UTC by Jirka Kosek
Modified: 2011-08-19 02:44 UTC (History)
6 users (show)

See Also:

Attachments

Description Jirka Kosek 2011-08-03 08:26:38 UTC 
HTML5 spec introduces new reverse attribute on ol element.

This attribute should be removed from the spec because it doesn't adhere to "Degrade Gracefully" design principle. Namely in legacy browsers numbering of list items will be wrong. This is more harm then necessity to manually number items for rare cases where list has to ordered in descending manner.
Comment 1 Aryeh Gregor 2011-08-03 17:22:29 UTC 
Yeah, the use-cases for this seem really weak.  Is anyone actually interested in implementing it?
Comment 2 Michael[tm] Smith 2011-08-04 05:36:22 UTC 
mass-move component to LC1
Comment 3 Ian 'Hixie' Hickson 2011-08-19 02:44:27 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: Rejected
Change Description: no spec change
Rationale: This is requested moderately often and is pretty easy to add. The degradation isn't fantastic but it's not horrible either  it's feature testable, and it's not a huge problem if it isn't used during the transition.