ladybird/Tests/LibWeb/Text/expected/Editing/execCommand-delete.txt

--- a ---
Before: foobar
After: fobar
--- b ---
Before: foo👩🏼‍❤️‍👨🏻bar
After: foobar
--- c ---
Before: foo<div contenteditable="">bar</div>
After: foobar
-												LibWeb: Delete entire graphemes when the delete/backspace key is pressed

We currently delete a single code unit. If the user presses backspace on
a multi code point emoji, they are going to expect the entire emoji to
be removed. This now matches the behavior of Chrome and Firefox.

											
										
										
											2025-08-14 15:25:19 -04:00
+								--- a ---
-												LibWeb: Add test for document.execCommand("delete")

Anchor the minimum functionality for this. WPT has an extensive suite
to test editing functionalities, but they all take a long time to
execute - so let's have a simple regression test in-tree for now.

											
										
										
											2024-11-30 12:20:44 +01:00
+								Before: foobar
 								After: fobar
-												LibWeb: Delete entire graphemes when the delete/backspace key is pressed

We currently delete a single code unit. If the user presses backspace on
a multi code point emoji, they are going to expect the entire emoji to
be removed. This now matches the behavior of Chrome and Firefox.

											
										
										
											2025-08-14 15:25:19 -04:00
+								--- b ---
 								Before: foo👩🏼‍❤️‍👨🏻bar
 								After: foobar
-												LibWeb: Merge nested editing hosts

If a node with `contenteditable=true/plaintextonly` is the child of an
editable node or an editing host, we should make it editable instead of
an editing host. This effectively merges nested editing hosts together,
which is how other browsers deal with this as well.

Gains us 5 WPT subtest passes in `editing`.

											
										
										
											2025-09-03 16:53:18 +02:00
+								--- c ---
 								Before: foo<div contenteditable="">bar</div>
 								After: foobar