Closed Bug 1426703 Opened 7 years ago Closed 3 years ago

Special `list-item` counter is not available

Categories

(Core :: Layout, defect, P3)

58 Branch
defect

Tracking

()

RESOLVED DUPLICATE of bug 288704

People

(Reporter: kizmarh, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 YaBrowser/17.10.0.2052 Yowser/2.5 Safari/537.36

Steps to reproduce:

1. Go to https://codepen.io/kizu/pen/QaKjmJ

or

1. Create an ordered list with a `start` attribute.
2. Add custom styles for the list items by using `counter(list-item)`.



Actual results:

List items rendered with 0 counter.


Expected results:

List items should be rendered with a proper list-item based on the `start` attribute.

The specifications: https://www.w3.org/TR/css-lists-3/#declaring-a-list-item — say:

> Additionally, list items automatically increment the special list-item counter. Unless the counter-increment property manually specifies a different increment for the list-item counter, it must be incremented by 1 on every list item, at the same time that counters are normally incremented. (This has no effect on the values of the counter-* properties.)

And Chrome, Safari and Edge all support this already.
Actually, start attribute is not needed, it is just the case web developers would need this behaviour, as otherwise its easy to emulate lists, but not when there is a `start` or `value` attributes on list or list-items.
Opened in Nightly the page you linked, the displayed list starts at 30. Not sure what it should display if not that? Can you make screenshot of incorrect and correct display?
Component: Untriaged → Layout
Flags: needinfo?(kizmarh)
Product: Firefox → Core
The first number for each item is a default list marker, the second one, in parens, is the generated in CSS.

Here is an image with a comparison of the same part of the example in Firefox Nightly (59.0a1 (2017-12-21), Mac OS) and Edge 16, Win 10.
Flags: needinfo?(kizmarh)
OK, I understand better. Indeed the bug is still present in latest nightly
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Unspecified → All
Hardware: Unspecified → All
[ Triage 2017/02/20: P3 ]
Priority: -- → P3
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: