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 24269 - Allow <ul type="none"> and <ol type="none">
Summary: Allow <ul type="none"> and <ol type="none">
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P1 enhancement
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL: http://www.w3.org/TR/html51/grouping-...
Whiteboard: whatwg-resolved
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-10 22:19 UTC by Leif Halvard Silli
Modified: 2016-04-26 23:01 UTC (History)
6 users (show)

See Also:


Attachments

Description Leif Halvard Silli 2014-01-10 22:19:55 UTC
Both UL and OL should permit the @type attribut with the value of "none", the purpose of which should be to set the list style type to none.

Here is a demo that shows this effect:

http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=2730

This behavior is already implemented in Webkit and Firefox (and hence probably in Chromium too)
Comment 1 Michael[tm] Smith 2015-06-16 11:33:58 UTC
Raising priority and noting as requiring a minor "feature tweak" to an existing feature.
Comment 2 Chris Rebert 2015-09-21 22:00:13 UTC
This is already specified for <ul> in 
https://html.spec.whatwg.org/multipage/rendering.html#decohints

As for <ol type="none">, it only seems to work in Firefox, not in Edge, Safari, or Chrome.
Testcase: http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=3636
Comment 3 Travis Leithead [MSFT] 2016-04-26 23:01:09 UTC
HTML5.1 Bugzilla Bug Triage: Won't Fix

The spec (both WHATWG and now HTML5.1) do not specify 'type' for UL or OL anymore, rather then consider that attribute legacy (obsolete) and recommend using CSS instead.

If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks!