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 26417 - i18n-ISSUE-343: Type attribute on ol
Summary: i18n-ISSUE-343: Type attribute on ol
Status: RESOLVED MOVED
Alias: None
Product: HTML.next
Classification: Unclassified
Component: default (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-23 13:34 UTC by i18n IG
Modified: 2016-05-05 14:56 UTC (History)
4 users (show)

See Also:


Attachments

Description i18n IG 2014-07-23 13:34:21 UTC
http://www.w3.org/TR/html5/grouping-content.html#the-ol-element
4.4.5 The ol element

The type attribute seems to be a presentational device that ought to be replaced by CSS, especially given that all major browsers support the styles described when they are specified by use of list-style-type (see http://www.w3.org/International/tests/repository/css3-counter-styles/predefined-styles/results-cstyles#simplenumeric for the roman styles). If it is truly presentational, perhaps we should deprecate it.

Or is this intentionally kept as a way to allow a minimal set of 'semantically' differentiated lists, that will work if CSS is not present? If so, perhaps we should add a brief note to explain that, and mention that you can do much more using CSS.
Comment 1 Charles McCathieNevile 2016-05-05 14:56:24 UTC
https://github.com/w3c/html/issues/341