Bug 173186

Summary: Delete second list item inside a single table cell should not delete the whole table
Product: WebKit Reporter: Javier Fernandez <jfernandez>
Component: HTML EditingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: ahmad.saleem792, jfernandez, rniwa, wenson_hsieh
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=173117
https://bugs.chromium.org/p/chromium/issues/detail?id=731913
Attachments:
Description Flags
Test case to reproduce the issue none

Javier Fernandez
Reported 2017-06-09 15:03:12 PDT
Created attachment 312495 [details] Test case to reproduce the issue What steps will reproduce the problem? (1) Load the attached test case (2) Place the cursor at the list item 2. (3) Hit backspace to the list item is removed What is the expected result? The list item 2 is removed but the list still holds the item 1. What happens instead? The whole table is deleted.
Attachments
Test case to reproduce the issue (251 bytes, text/html)
2017-06-09 15:03 PDT, Javier Fernandez 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Javier Fernandez
Comment 1 2017-06-09 15:04:58 PDT
Maybe related to bug #173117 ?
Javier Fernandez
Comment 2 2018-02-26 08:14:32 PST
The Blink bug (731913) has been already fixed, so perhaps we try a similar approach with this bug.
Ahmad Saleem
Comment 4 2022-11-16 13:39:49 PST
(In reply to Ahmad Saleem from comment #3) > Blink Commit - > https://chromium.googlesource.com/chromium/src.git/+/ > 5961ff06240e30a18405608f06d8eea4730c7b8f > > Webkit GitHub Source - > https://github.com/WebKit/WebKit/blob/ > 8a344c3387b2bfe58dc8c8a94b1683187effef2e/Source/WebCore/editing/ > DeleteSelectionCommand.cpp#L112 > > !IsListItem(position.xxx > > Still haven't figured out xxx yet. Thanks! Although before that I am not able to reproduce this bug and only 2. bullet get destroyed and 1. remains. So I think the test case attached is working fine in Safari 16.1. Do we need anything else or we can close this? Thanks!
Ryosuke Niwa
Comment 5 2022-11-17 11:49:31 PST
No longer reproduces.
Note You need to log in before you can comment on or make changes to this bug.