Closed Bug 1638349 Opened 4 years ago Closed 4 years ago

With Firefox (76.0.1), Ordered list numbering is not resumed when exiting from a sublist

Categories

(Core :: Layout: Generated Content, Lists, and Counters, defect)

Product:
Core
Component:
Layout: Generated Content, Lists, and Counters
Version:
76 Branch
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1548753

People

(Reporter: fsx.rwt, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:76.0) Gecko/20100101 Firefox/76.0

Steps to reproduce:

<ol>
	<li>Level #1 Item #1.</li>
	<li>Level #1 Item #2.</li>
	<li>Level #1 Item #3.</li>
	<ol>
		<li>Level Item #2 #1.</li>
		<li>Level Item #2 #2.</li>
	</ol>	
	<li>Level #1 Item #4.</li>
	<li>Level #1 Item #5.</li>
</ol>

Actual results:

  1. Level #1 Item #1 "
  2. Level #1 Item #2 "
  3. Level #1 Item #3 "
    1. Level #2 Item #1 "
    2. Level #2 Item #2 "
  4. Level #1 Item #4 "
  5. Level #1 Item #5 "

Expected results:

  1. Level #1 Item #1
  2. Level #1 Item #2
  3. Level #1 Item #3
    1. Level #2 Item #1
    2. Level #2 Item #2`
  4. Level #1 Item #4
  5. Level #1 Item #5

The actual results was automatically reformatted because of the number actually the actual result is this I am adding ---- to prevent reformatting:

--- 1. Level #1 Item #1
--- 2. Level #1 Item #2
--- 3. Level #1 Item #3
--- 1. Level #2 Item #1
--- 2. Level #2 Item #2
--- 3. Level #1 Item #4
--- 4. Level #1 Item #5

Actual Results : Hopefully this time you won't remove the indent
--- 1. Level #1 Item #1
--- 2. Level #1 Item #2
--- 3. Level #1 Item #3
--------- 1. Level #2 Item #1
--------- 2. Level #2 Item #2
--- 3. Level #1 Item #4
--- 4. Level #1 Item #5

Component: Untriaged → Layout: Generated Content, Lists, and Counters
Product: Firefox → Core

Thanks for submitting the bug report. The given nested list markup is invalid, so this is a duplicate of bug 1548753. List numbering recovery with invalid markup (<ol> should not be a child of another <ol>) is currently broken.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE

Sean,
thanks for the reply, and the html lesson. I see my error now and recognize the logic in the syntax.

It is too bad that not all browser ( Chrome, Edge) are not as purist. I just came back to Firefox in recent weeks (because of all the new security features), after a few years of chrome and Edge, and my code was always formatted correctly, in spite of my error. And apparently it was the case with Firefox before release 68.

So for backward compatibility, I am not sure if it should be accepted or not. In my case in order to be compatible with Firefox I am going to have to change many thousand lines of code in many thousand of files.

Gilbert

You need to log in before you can comment on or make changes to this bug.