New issue
Advanced search Search tips
Starred by 1 user

Issue metadata

Status: Available
Owner: ----
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Feature

Sign in to add a comment

Issue 811746: Backspacing a tripple nested list leaves stray items

Reported by, Feb 13 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.51 Safari/537.36

Steps to reproduce the problem:
Have a nested list that goes three levels deep, selecting such a tree and backspacing it leads to a stray list item.

Please see the attached file for an interactive example.

1. A
2. B
  1. C
    1. D
3. E

Select B to D and hit backspace.

What is the expected behavior?
1. A
3. E

What went wrong?
1. A
3. E

The item "1." inside "2." should be gone entirely.

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 65.0.3325.51  Channel: beta
OS Version: 10.0
Flash Version:
466 bytes View Download

Comment 1 by, Feb 13 2018

The same behavior occurs when deleting an item with the [DEL] key, so this isn't exclusive to backspacing.

It can also be somewhat reproduced using `getSelection().getRangeAt(0).deleteContents()`, but this has yields a slightly more erroneous DOM that appears to be the result of the attempts to generate valid HTML.

This leads me to the assumption, that each of these operations use a common code to handle the deletion of nested lists.

Comment 2 by, Feb 13 2018

The same issue ocurrs in Microsoft Edge, although it causes both nested lists to remain afterwards.

Comment 3 by, Feb 13 2018

Labels: Needs-Triage-M65

Comment 4 by, Feb 14 2018

Components: -Blink>Editing Blink>Editing>Command
Labels: -Type-Bug -Pri-2 Pri-3 Type-Feature
Status: Available (was: Unconfirmed)
Demo page:

Chrome and Edge behave same. Firefox behaves as expected result in #c1.

Comment 5 by, Feb 14 (5 days ago)

Project Member
Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit - Your friendly Sheriffbot

Comment 6 by, Feb 15 (4 days ago)

Status: Available (was: Untriaged)

Sign in to add a comment