Bugzilla

Release Note Request (optional, but appreciated)
[Why is this notable]: This is one of the biggest basic editor behavior changes.
[Affects Firefox for Android]: Yes.
[Suggested wording]:
Starting from Firefox 113 (currently only in the Nightly channel or early beta builds), the builtin editor behaves similar to the other browsers when splitting a node (e.g., typing `Enter` to split a paragraph) and joining two nodes (e.g., typing `Backspace` at start of a paragraph to join the paragraph and the previous one). When a node is split, builtin editor creates new node after the original one, i.e., creates the right node. Similarly, when two nodes are joined, the builtin editor deletes the latter node and move its children to end of the preceding node.

This new behavior can be enabled by web apps themselves in all channels with a call of `document.execCommand("enableCompatibleJoinSplitDirection", false, "false")`. This command is available only when `designMode` is set to `"on"` or there is at least one editable element which has `contenteditable` attribute, **and** the builtin editor has not handled `insertParagraph`, `delete` nor `forwardDelete` command.
[Links (documentation, blog post, etc)]:
No documentation, no blog post, unfortunately.

Release Note Request (optional, but appreciated)
[Why is this notable]: This is one of the biggest basic editor behavior changes.
[Affects Firefox for Android]: Yes.
[Suggested wording]:
Starting from Firefox 113 (currently only in the Nightly channel or early beta builds), the builtin editor behaves similar to the other browsers when splitting a node (e.g., typing `Enter` to split a paragraph) and joining two nodes (e.g., typing `Backspace` at start of a paragraph to join the paragraph and the previous one). When a node is split, builtin editor creates new node after the original one, i.e., creates the right node. Similarly, when two nodes are joined, the builtin editor deletes the latter node and move its children to end of the preceding node.

This new behavior can be enabled by web apps themselves in all channels with a call of `document.execCommand("enableCompatibleJoinSplitDirection", false, "false")` (bug 1810663). This command is available only when `designMode` is set to `"on"` or there is at least one editable element which has `contenteditable` attribute, **and** the builtin editor has not handled `insertParagraph`, `delete` nor `forwardDelete` command.
[Links (documentation, blog post, etc)]:
No documentation, no blog post, unfortunately.

Release Note Request (optional, but appreciated)
[Why is this notable]: This is one of the biggest basic editor behavior changes.
[Affects Firefox for Android]: Yes.
[Suggested wording]:
Starting from Firefox 113 (currently only in the Nightly channel or early beta builds), the builtin editor behaves similar to the other browsers when splitting a node (e.g., typing `Enter` to split a paragraph) and joining two nodes (e.g., typing `Backspace` at start of a paragraph to join the paragraph and the previous one). When a node is split, builtin editor creates new node after the original one, i.e., creates the right node. Similarly, when two nodes are joined, the builtin editor deletes the latter node and move its children to end of the preceding node.

This new behavior can be enabled by web apps themselves in all channels with a call of `document.execCommand("enableCompatibleJoinSplitDirection", false, "false")` (introduced in bug 1810663). This command is available only when `designMode` is set to `"on"` or there is at least one editable element which has `contenteditable` attribute, **and** the builtin editor has not handled `insertParagraph`, `delete` nor `forwardDelete` command.
[Links (documentation, blog post, etc)]:
No documentation, no blog post, unfortunately.