110682 2013-02-22 22:02:41 -0800 Deletion of selection in contenteditable node results in incorrect DOM ordering 2022-08-30 16:00:17 -0700 1 1 1 Unclassified WebKit HTML Editing 528+ (Nightly build) Unspecified Unspecified RESOLVED CONFIGURATION CHANGED https://bugs.webkit.org/show_bug.cgi?id=244559 http://persistent.info/webkit/test-cases/selection-deletion.html HasReduction P2 Normal --- 1 mihaip webkit-unassigned ahmad.saleem792 rniwa oldest_to_newest 840305 0 mihaip 2013-02-22 22:02:41 -0800 Test case: http://persistent.info/webkit/test-cases/selection-deletion.html 1. Press the "Select '1. One'" button (or select the text "1. One" without the trailing newline) 2. Press the "execCommand('delete')" button (or press the delete key) Expected result: The "1. One" text is gone, but the contenteditable is otherwise unaffected, i.e.: <empty line> 2. Two 3. Three Actual result: The latter two lines are combined into one, and the order is reversed: <empty line> 3. Three2. Two There appear to be several contributing factors in the test case: - The lines all have "position: relative" - There's a contenteditable=false "toolbar" div before before the first line - There can't be any intervening whitespace in the DOM between the first two lines (see the lack of newline in the test case) Bug 108987 may be related (in that it also involve contenteditable="false" elements) 840469 1 ap 2013-02-23 15:16:04 -0800 Not a regression from Safari 6. 1894971 2 ahmad.saleem792 2022-08-30 16:00:17 -0700 I am not able to reproduce this bug in Safari Technology Preview 152 and it does not misalign list item as mentioned in "Actual Result" and it matches with other browsers (Chrome Canary 107 and Firefox Nightly 107). Here is DOM View post steps for all browsers: <div id='editable' contenteditable='true'> '&#10;' <div class='toolbar'> 'Toolbar' </div> '&#10;' <div class='section' id='one'> <br/> </div> <div class='section'> '2. Two' </div> '&#10;' <div class='section'> '3. Three' </div> '&#10;' </div> I am going to mark this as "RESOLVED CONFIGURATION CHANGED", since original bug is not reproducible and all browsers match. Thanks!