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 9798 says that @type for <ol> and <ul> should be permitted. This bug suggests the syntax for the type attribute, SOLUTION: General: change from HTML4 values to CSS values For <ul> the HTML4 values are indentical with CSS2, and thus can remain. In addition the CSS value "none" should also be permitted. FOr <ol>, the HTML4 values should become deprecated/obsoleted: The HTML4 values for ol@type: 1,a,A,i,I New values from CSS2: decimal | decimal-leading-zero | lower-roman | upper-roman | lower-greek | lower-latin | upper-latin | armenian | georgian | lower-alpha | upper-alpha | none The value "inherit" should not be permitted. JUSTIFICATION: It is practical to have just one value set - namely that of CSS. USER AGENT SUPPORT: Webkit: the CSS synonyms for the HTML4 values, are already supported - other CSS values are not supported. (Interaction with default CSS may cause bugs, however). In Gecko: The CSS synonyms for the HTML4 values are already supported. But disabling CSS removes support for @type, regardless of whether it contains CSS values or HTML4 values. Opera: supports the HTML4 values - but not the CSS values. Doesn't matter if CSS is enabled or if one disables CSS (to disable CSS, I disable any styling in "user mode" - see the Stylesheet menu under the View menut - I don't know if there is a way to disable CSS more fundamentally). IE: Only support the HTML4 values. The support is not affected if one disables CSS for the current page.
I doubt we'll be able to do this, given back-compat, but we should probably at least investigate.
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: I looked into this but on balance I think we're better off not doing this (yet). I'm loathe to introduce synonyms, so for <ol type> I'm skeptical about doing it at all. For <ul type> the only addition at this point would be "none" and I don't see the use of that. Maybe once CSS3 Lists is more complete, we can revisit this, though.
*** Bug 11001 has been marked as a duplicate of this bug. ***
This bug was cloned to create HTML WG bug 19022.
Tab, what's the status of CSS lists? And what do you think of this suggestion?
(In reply to comment #5) > Tab, what's the status of CSS lists? And what do you think of this > suggestion? This doesn't need anything particular from Lists. If you want to reference some counter styles, the Counter Styles spec is going to be LC in a week or two. <http://w3c-test.org/csswg/css-counter-styles-3/> I have no particular opinion on this bug. It looks like its compat information is wrong - WebKit doesn't seem to recognize any of the CSS names in the type attribute.
(In reply to comment #6) > (In reply to comment #5) > It looks like its compat information is wrong - WebKit > doesn't seem to recognize any of the CSS names > in the type attribute. Pedantic: I understand why you read me that way - it is probably the word "other" that creates that impression. But, actually, I only claimed it to work in Gecko, and only for the values that have paralell HTML4 values.
Tab: Sorry, yeah, I meant the counter styles spec. I'm reluctant to do this unless there's a compelling reason. I haven't really seen one so far.
I'm marking this WONTFIX. There doesn't seem to really be a compelling use case and it introduces a lot of redundancy.