li list numbered incorrectly when it contains ol lists
Categories
(Core :: Layout: Generated Content, Lists, and Counters, defect, P3)
Tracking
()
People
(Reporter: kdiment, Unassigned)
References
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
View https://www.wantageandgrove.org/constitution.php using FF71 to see incorrect numbering of the outer list. View the same file using Safari to see the list numbered correctly.
Actual results:
The outer list items are numbered A. B. C. etc, but when one of those contains a list numbered 1. 2. 3. etc the next letter in the outer list is the letter numbered alphabetically one higher than the last number of the inner list.
Expected results:
The letters of the outer list should not be affected by the numbering of the inner list.
Updated•4 years ago
|
Comment 1•4 years ago
|
||
I can reproduce this on Firefox Nightly 74.0a1 (MacOS 10.15.2).
Comment 3•4 years ago
|
||
Comment 4•4 years ago
|
||
So it is a bug that we don't give the correct order symbol on unordered list with list-style: upper-alpha;
.
I replaced ul
with ol
, and we still have the same issue anyway. Not sure what happen on the ::marker.
Comment 5•4 years ago
|
||
Perhaps this is related to Bug 1548753
Updated•4 years ago
|
Seeing same issue in Thunderbird 68.8.0
Are these related ?
Is same bad code been used in Thunderbird?
Suddenly impossible to create lists. See info reported in bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1611861
Reporter | ||
Comment 7•4 years ago
|
||
It seemed to me a though it might be a simple case of using the same variable to count the items in the outer list and in the inner list, where two separate variables should be used. But what do I know? It does seem to be taking a very long time to sort this out. You must have a lot of higher-priority bugs to deal with first. Also, I apologize if this lockdown business is making me sound a bit impatient.
Comment 8•4 years ago
|
||
This is "just" bug 1548753. It's a bit more tricky than that because that's not how CSS counters work, see the discussion in that bug.
Description
•