build(deps): bump jodit from 4.15.8 to 4.15.13

[dependabot]

Bumps jodit from 4.15.8 to 4.15.13.

Release notes

Sourced from jodit's releases.

4.15.13

🚀 New Feature

• #1423 New toolbar-navigation plugin: the toolbar is now reachable from the keyboard. Alt+F10 moves the focus from the editable area into the toolbar, the arrow keys walk the buttons (wrapping at the ends, reversed in RTL), Home/End jump to the ends, Enter/Space activate a button and Escape gives the focus back to the editor; disabled buttons are skipped. This follows the WAI-ARIA authoring practices for a role="toolbar" widget, and the focus is moved programmatically, so it also works with the default allowTabNavigation: false, where the buttons take no part in the page tab order. On a button with a dropdown, ArrowDown opens it and focuses the first item, ArrowDown/ArrowUp walk the items, and Escape or ArrowUp on the first item close it and return to the button. Reaching the toolbar is the regular focusToolbar command, so it can be remapped like any other (commandToHotkeys: { focusToolbar: 'alt+0' }) or called with execCommand. Requested by @​cut2run.

🐛 Bug Fix

• A toolbar button focused from the keyboard right after a mouse click showed no highlight in Chrome: a modifier shortcut such as Alt+F10 does not switch the browser to keyboard modality, so :focus-visible never matched. Toolbar buttons are never focused by the mouse (mousedown is prevented to keep the selection), so they now highlight plain :focus.

4.15.10

🐛 Bug Fix

• #1184 Clicking an image wrapped in a contenteditable="false" element (for example <picture contenteditable="false"><img></picture>) left the caret stuck: the arrow keys could not move it past the image. Selecting a node put the range inside that non-editable island — the browser cannot place a caret there, so there was nothing for the arrow keys to move. select() now selects the outermost non-editable ancestor instead, so the range stays in editable content and the caret steps over the element as usual. Selecting an editable node, and select(node, true), are unchanged.

4.15.9

🐛 Bug Fix

• #1485 In inline mode the change event fired on every value synchronisation, even when nothing had changed: the source element is the editor container there, so the editor compared the value with its own markup and the difference never went away. Among other effects, clicking a button in the table cells popup closed the popup (select-cells hides it on change) before the button's click arrived. The value last synchronised to an inline container is now tracked separately, so change fires only on a real change; standard mode is unchanged. Thanks to @​brendon (#1486).

Changelog

Sourced from jodit's changelog.

4.15.13

🚀 New Feature

• #1423 New toolbar-navigation plugin: the toolbar is now reachable from the keyboard. Alt+F10 moves the focus from the editable area into the toolbar, the arrow keys walk the buttons (wrapping at the ends, reversed in RTL), Home/End jump to the ends, Enter/Space activate a button and Escape gives the focus back to the editor; disabled buttons are skipped. This follows the WAI-ARIA authoring practices for a role="toolbar" widget, and the focus is moved programmatically, so it also works with the default allowTabNavigation: false, where the buttons take no part in the page tab order. On a button with a dropdown, ArrowDown opens it and focuses the first item, ArrowDown/ArrowUp walk the items, and Escape or ArrowUp on the first item close it and return to the button. Reaching the toolbar is the regular focusToolbar command, so it can be remapped like any other (commandToHotkeys: { focusToolbar: 'alt+0' }) or called with execCommand. Requested by @​cut2run.

🐛 Bug Fix

• A toolbar button focused from the keyboard right after a mouse click showed no highlight in Chrome: a modifier shortcut such as Alt+F10 does not switch the browser to keyboard modality, so :focus-visible never matched. Toolbar buttons are never focused by the mouse (mousedown is prevented to keep the selection), so they now highlight plain :focus.

4.15.10

🐛 Bug Fix

• #1184 Clicking an image wrapped in a contenteditable="false" element (for example <picture contenteditable="false"><img></picture>) left the caret stuck: the arrow keys could not move it past the image. Selecting a node put the range inside that non-editable island — the browser cannot place a caret there, so there was nothing for the arrow keys to move. select() now selects the outermost non-editable ancestor instead, so the range stays in editable content and the caret steps over the element as usual. Selecting an editable node, and select(node, true), are unchanged.

4.15.9

🐛 Bug Fix

• #1485 In inline mode the change event fired on every value synchronisation, even when nothing had changed: the source element is the editor container there, so the editor compared the value with its own markup and the difference never went away. Among other effects, clicking a button in the table cells popup closed the popup (select-cells hides it on change) before the button's click arrived. The value last synchronised to an inline container is now tracked separately, so change fires only on a real change; standard mode is unchanged. Thanks to @​brendon (#1486).

Commits

• f7caa82 New version 4.15.13 Read more https://github.com/xdan/jodit/blob/main/CHANGEL...
• 27640fa ci(release): count the toolbar-navigation plugin in the ESM check
• 258bc4a New version 4.15.12 Read more https://github.com/xdan/jodit/blob/main/CHANGEL...
• 98020b3 build(esm): count the toolbar-navigation plugin in PLUGINS_COUNT
• d4ced1c New version 4.15.11 Read more https://github.com/xdan/jodit/blob/main/CHANGEL...
• 7a049e6 ci(screenshots): don't install the jodit package into the Playwright image
• 127a424 New version 4.15.10 Read more https://github.com/xdan/jodit/blob/main/CHANGEL...
• ee859a7 fix(selection): select the non-editable island instead of a node trapped insi...
• efcc4ba New version 4.15.9 Read more https://github.com/xdan/jodit/blob/main/CHANGELO...
• 3cb63aa docs(changelog): 4.15.9 — inline mode no longer fires change on every sync (#...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 2c4e84cd-facc-4f41-bb32-3c2472afbddd

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}