Repository navigation
Update dependency slate-react to v0.147.6 - #786
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
GitLab Pipeline ActionGeneral informationLink to pipeline: https://gitlab.com/code0-tech/development/pictor/-/pipelines/3085839690 Status: Passed Job summariesstorybook:buildStorybook available at https://code0-tech.gitlab.io/-/development/pictor/-/jobs/18157970158/artifacts/storybook-static/index.html |
renovate
Bot
force-pushed
the
renovate/slate-react-0.x
branch
from
November 11, 2026 18:32
5cd317f to
7a6650c
Compare
renovate
Bot
force-pushed
the
renovate/slate-react-0.x
branch
from
November 18, 2026 19:08
7a6650c to
6413784
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^0.125.0→^0.125.0 || ^0.147.0^0.125.1→^0.147.6Release Notes
ianstormtaylor/slate (slate-react)
v0.147.6Compare Source
Patch Changes
6f00413Thanks @dannelundqvist! - Copy and cut now use the selection the user just made. Selection changes reacheditor.selectiona little later than they happen, and copy and cut wrote the clipboard fromeditor.selection, so a copy straight after selecting, such as Ctrl+A followed at once by Ctrl+C, could copy the previous selection or nothing at all. Copy and cut now process any pending selection change first, before anonCopyoronCuthandler runs.v0.147.5Compare Source
Patch Changes
a25994bThanks @dylans! - On Android, a keyboard correction whose target range points outside the editor now replaces the word before the caret instead of inserting the corrected word after itv0.147.3Compare Source
Patch Changes
b34e312Thanks @dylans! - Firefox for Android no longer splits a word across blocks when a keyboard suggestion is accepted in an empty paragraph. Firefox commits the word as oneinsertTextper character at offsets it computed first; once the first character re-rendered the empty leaf, the rest of the word went into the next block. A character that arrives within 25 ms of the previous one and targets somewhere other than the editor's selection is now inserted at the selection instead (#6343).v0.147.2Compare Source
Patch Changes
18f1927Thanks @dylans! - Chrome's Writing Direction menu command no longer breaks the editor. The command changes the DOM without abeforeinputevent, wrapping text in adirectionspan, so React later threwNotFoundErroronremoveChildand the editor unmounted. Slate now undoes the DOM changes of anyformat*input it was not asked to handle first and keeps the selection.v0.147.1Compare Source
Patch Changes
ca37117Thanks @dylans! - Report an element whoserenderElementdidn't render itschildrenthrougheditor.onDOMErrorwhen it mounts, naming the element'stypeand path. Before, nothing was reported, and lookups into the element returnednullwith no hint why.v0.147.0Compare Source
Minor Changes
6c4cab5Thanks @dylans! - AddresolveDOMNode,resolveSlateNode,resolveSlatePointandresolveSlateRange, which returnnullinstead of throwing, likeresolveDOMPointandresolveDOMRange. UnlikesuppressThrow: true,resolveSlatePointandresolveSlateRangealso returnnullbeforeEditablemounts and for a selection with no range. Thetolookups andsuppressThroware unchanged.v0.146.1Compare Source
Patch Changes
#6334
0f99057Thanks @dylans! -resolveDOMPointandresolveDOMRangeno longer report a miss througheditor.onDOMError. A miss is often ordinary: a layout effect that measures the selection runs before the edited text's DOM is attached, and replacingeditor.childrencan leave the selection past the end of the new text, so these were reported as broken rendering when nothing was wrong. Slate no longer callseditor.onDOMErroritself; the hook stays for apps and plugins.resolveDOMRangealso returnsnullinstead of throwing when the editor's window isn't registered yet, for example from a layout effect inside the first render, and checks the focus only when the anchor resolves. Scrolling the selection into view no longer throws when the unhung range ends in an element that doesn't render its children.v0.145.1Compare Source
Patch Changes
3d7b2faThanks @dylans! - A click inside the editor whose handler changes the clicked node, for example a<select>that callssetNodeson its element or a suggestion that inserts text, no longer throws "Unable to find the path for Slate node".Editable's click handling now returns when the clicked node is no longer in the document, which its existing check intended butfindPathstarted throwing before it since 0.142.v0.145.0Compare Source
Minor Changes
89a74deThanks @dylans! - Add a controlledvalueprop toSlate. Pass the value fromonValueChangeback in, and Slate recognizes that exact object and doesn't apply it again. Any other value is applied as a change from outside the editor througheditor.setChildren, in a layout effect, so the selection and history stay valid. Values passed in aren't reported throughonValueChange. Updates wait while the user is composing text or Android has pending input, and only the latest is applied.valueandinitialValuetogether throw.Patch Changes
6cb0eb4Thanks @dylans! - A DOM selection change made just before the editor loses focus now reacheseditor.selection. Selection changes are processed a little later than they happen, and since 0.142 changes processed after blur were ignored, so for example clicking an element whose handler blurs the editor could leaveeditor.selectionwhere it was before the click. Blur now processes any pending selection change first.v0.142.0Compare Source
Minor Changes
342facfThanks @dylans! -createEditortakes an optional type parameter.createEditor()still returnsEditor;createEditor<BaseEditor>()returns a plainBaseEditor, so a plugin chain is type-checked against the plugins actually applied rather than the fully extendedCustomTypeseditor.v0.141.0Compare Source
Minor Changes
#6311
a1852f8Thanks @dylans! - Add opt-ininlineEdgeAffinityandleafEdgeAffinityeditor hooks andEditor.insertionPointfor consistent insertion at inline and mark boundaries. Implicit text, fragment and inline-node insertion at collapsed carets follows the configured rules, andEditor.marksreports the receiving leaf’s marks. Both hooks default tonull, preserving existing behavior.BaseEditornow requires the two affinity hooks and theinsertionPointquery. Editors created throughcreateEditorreceive them automatically; structurally constructed editors and editor mocks must supply them. Slate React disables native insertion when affinity changes the receiving point, while retaining compatibility with older supported Slate peers that lack the helper.Committed Android typing that changes receiving leaves uses the existing action reconciliation path, so a native mutation does not remain rendered in the old leaf. Active composition retains its existing diff path.
#6310
407a066Thanks @dylans! - Add afilteroption toinsertFragment. It is called for each node in the fragment with the destination block entry and returnsfalseto skip that node.Patch Changes
428fd70Thanks @kinaluo! -insertFragmentnow splits the block when block-level nodes such as a void image are pasted mid-block, so they land between the two halves instead of above the block, and the cursor moves to the start of the second half. Dropping a dragged block void onto the middle of a paragraph splits it the same way. Schemas that don't allow blocks inside a structure (for example a list item's text wrapper) should overrideinsertFragmentto move those nodes elsewhere before calling the original.v0.140.1Compare Source
Patch Changes
dcae734Thanks @a-y-ibrahim! - Keep the DOM and Slate value in sync when an insertText override rejects native text input, including insertions at decoration boundaries.v0.140.0Compare Source
Patch Changes
#6105
a07df52Thanks @janpaepke! - Stop drops from throwing when the browser resolves the drop position outside of the editor.<Editable>resolved the target range from the drop coordinates viacaretRangeFromPoint, which can land on a DOM node outside of the editor even though the event's target is inside it (e.g. when the page scrolled between the lastdragoverand thedrop); the resulting "Cannot resolve a Slate point from DOM point" error escaped the event handler and the drop was lost. The dropped data now goes to the current selection instead (the end of the document without one), and internally dragged content stays where it is.DOMEditor.findEventRangegained asuppressThrowoption for this and returnsnullwhen the range cannot be resolved.#6306
c4c990eThanks @dylans! - Expose the placeholder to assistive technology asaria-placeholderon the editor root while it is shown, and mark the visual placeholderaria-hiddenso it isn't read as content.v0.138.3Compare Source
Patch Changes
#6295
2d2a520Thanks @dylans! - Restore an existing editor selection when Tab or Shift+Tab focuses Editable. Keep the browser's initial placement when no selection exists, and preserve mouse-based caret placement.#6294
acca98fThanks @dylans! - Call caller-provided Editable event handlers in read-only mode while skipping Slate's editing behavior. Read-only editors remain outside the tab order unless a tabIndex is provided.#6290
ee31c77Thanks @dylans! - Acceptundefinedexplicitly in the optionalEditable,Slate,useSelectedandcreateHyperscriptoptions, so their published types stay compatible withexactOptionalPropertyTypesafter the TypeScript 6 upgrade.v0.138.1Compare Source
Patch Changes
b0462a1Thanks @dylans! - Limit whole-block deletion of a hanging selection, and native triple-click selections, to top-level blocks. Nested blocks such as table cells and list items keep the previous behavior, so cutting or dragging across cells in editors withouteditor.isIsolatedno longer removes cells. After undoing a whole-block deletion, the defaultscrollSelectionIntoViewscrolls to the restored text instead of the start of the following block.v0.138.0Compare Source
Patch Changes
#6280
b397417Thanks @dylans! - CallscrollSelectionIntoViewwhen keyboard navigation moves a selection already synchronized with the DOM, including native movement between text lines. Custom callbacks can keep the caret clear of sticky headers. Renders and edits without user input remain excluded from this additional scrolling path.#6282
f64a47fThanks @dylans! - Keep the browser's native triple-click selection outsideeditor.isIsolatedelements, so Backspace and cut after a triple-click in Chrome and Safari remove the whole block as in a plain contenteditable. Inside isolated elements, triple-click still selects only the current block's contents. Firefox keeps its native non-hanging selection.#6279
dabbab7Thanks @dylans! - Use native selection word boundaries for word-navigation shortcuts so Option/Ctrl+Arrow respects native punctuation and language boundaries while synchronizing Slate's selection in the same key event. Fall back to Slate's word transform when native selection movement is unavailable.v0.136.0Compare Source
Minor Changes
#6268
1e9e7e1Thanks @dylans! - AddEditor.word, which returns the range of the word around a point within its block. Words can cross mark changes and inline links but stop at voids, andisWordCharacterlets you define your own word characters.ReactEditor.getWordalso includes text an input method is still composing.The
'word'unit (word deletion, word movement, andEditor.before/after/positions) now usesIntl.Segmenter, where available, to split runs of word characters. Chinese, Japanese and Thai text without spaces now deletes and moves one word at a time instead of a whole phrase. Text with spaces between words is unaffected.v0.134.1Compare Source
Patch Changes
d5b2fbdThanks @nabbydude! - Speed up tree-altering operations by using faster array functions when copying and replacing children.v0.134.0Compare Source
Patch Changes
#6250
b70a400Thanks @dylans! - Fix typing on Android right after toggling a mark with a collapsed selection. The first letter no longer moves the caret past the end of the previous leaf, which closed the soft keyboard and scattered the following letters, and a composition into the new marked text is no longer interrupted by a re-render.#6248
f9b0cbfThanks @dylans! - Fix an Android crash ("Failed to execute 'removeChild' on 'Node'") when typing starts in an empty editor just as the placeholder appears. The DOM restore that runs before Android renders no longer undoes React's own placeholder changes.#6243
56aa3c4Thanks @dylans! - Remove the source void when it is dragged to a new position, preventing duplicate voids when the dragged selection is collapsed.#6249
d879fc1Thanks @dylans! - Fix composed text appearing twice in Chrome when the caret sits at the start of a leaf that follows marked text. Chrome composes into the end of the previous leaf, so its copy is removed before Slate inserts the text into the selected leaf.#6251
927c228Thanks @dylans! - Remove text an IME composes into a selected void element. Slate doesn't insert text into voids, so the browser's copy was left in the void's DOM.v0.133.8Compare Source
Patch Changes
#6238
468b58dThanks @dylans! - Scroll the caret into view when an edit changes the selection even if the DOM selection already matches the editor, including Backspace between empty paragraphs.#6235
22ede7fThanks @dylans! - Move the caret into an adjacent empty text node when an arrow key leaves an editable inline, so padding does not leave the caret drawn inside the inline.v0.133.7Compare Source
Patch Changes
a0bcf70Thanks @dylans! - Sync the selection from the DOM before calling anEditableonClickhandler, soeditor.selectionin the handler reflects the click instead of the previous selection.v0.133.6Compare Source
Patch Changes
#6229
c486badThanks @dylans! - Move the caret to the empty last line of a block that ends with a newline when pressing ArrowUp from the block below in Chrome and Safari, which skipped that block natively.#6226
a8329a2Thanks @dylans! - CopyinitialValuenodes that another editor is already using, so twoSlatecomponents given the same value render and edit independently instead of throwing "Unable to find the path for Slate node". Requires slate-dom 0.133.6 or newer.#6225
cb788f8Thanks @dylans! - Extend the selection from a selected void when Shift-clicking text, instead of leaving it collapsed in the void in Chromium.v0.133.5Compare Source
Patch Changes
#6224
84f047cThanks @dylans! - Replace an expanded selection correctly when an IME composition starts right after selecting it. The selection is now synced before the composition starts, and Firefox no longer crashes or leaves the replaced text in the document.#6222
c333eedThanks @dylans! - Render an empty block right-to-left when the nearest sibling block with text is right-to-left, so a new line after Hebrew or Arabic text starts on the right.#6220
3eed905Thanks @dylans! - Keep input, selection and history events from native contenteditable regions nested inside non-editable containers out of the surrounding Slate editor. Preserve Slate text and event hosts inside custom editable islands.#6223
8c929a8Thanks @dylans! - Keep the Firefox caret on the new line after a trailing soft break without adding zero-width characters to the document. Preserve selection offsets and copied text around the extra rendering newline.Requires slate-dom 0.133.5 or newer for the matching DOM selection mapping.
#6219
8e8cf36Thanks @dylans! - Stop re-rendering every text node in a block when only one of them changes. Text and leaf components now compare what they use from the parent (its properties, whether the text is its last child, and whether the block is empty) instead of the parent object itself.#6221
270a4a0Thanks @dylans! - Call deletion overrides in WebKit when Backspace at the start or Delete at the end of a document does not emit beforeinput.v0.133.4Compare Source
Patch Changes
ce3faf8Thanks @dylans! - Read the DOM selection when abeforeinputevent arrives, so input that follows a selection change before the browser firesselectionchangegoes where the caret is.v0.133.3Compare Source
Patch Changes
e86bcd3Thanks @dylans! - Strip Babel's__selfand__sourcedevelopment metadata from hyperscript attributes so generated documents remain serializable and do not contain local source paths.v0.133.2Compare Source
Patch Changes
#5985
5eeea5eThanks @wljray! - Flush Android backward text deletions without waiting for another input event, retain the typing delay when no action is pending, cancel superseded flush timers, and avoid an extra change notification when restoring unchanged marks.#6207
906eafeThanks @dylans! - Restore Chromium's structural DOM changes before applying multiline composition commits, preventing duplicated text while preserving intervening React updates.v0.133.0Compare Source
Minor Changes
dd6d37fThanks @GaurangTandon! - Revert "Ignore input events dispatched by script" (#6117). Input, paste and drop events dispatched by script are handled again, as in 0.127.1.v0.132.0Compare Source
Minor Changes
d8cdecdThanks @dylans! - AddRange.direction(range), which returns'forward','backward'or'collapsed'.Range.isForwardandRange.isBackwardare unchanged; a collapsed range still counts as forward, which is now documented.Patch Changes
63134d0Thanks @cpruijsen! - Fix thePropsMergetype forTransforms.setNodesso themergeoption can return scalar property values, not just objects.v0.131.0Compare Source
Minor Changes
7850c31Thanks @dylans! -Transforms.wrapNodesandTransforms.unwrapNodesnow unhang a range by default and accepthanging, likesetNodes,insertNodes,mergeNodesandremoveNodes. A selection that ends at the start of the next block no longer wraps or unwraps that block. Passhanging: trueto keep the old behavior.Patch Changes
#6177
fdc3dacThanks @dylans! - Only refill an emptied editor when a delete runs at the selection. In 0.130,Transforms.delete(editor, { at: path })also inserted an untyped empty block when it removed the last node, which left an extra block behind in code that deletes every block and then inserts new content. Programmatic deletes with an explicitatnow act likeremoveNodesagain.#6176
22cf872Thanks @dylans! - FixinsertFragmentinto an editor whose only block is empty, which left an extra untyped empty block before the inserted content (a regression in 0.130).#6181
ec75af0Thanks @dylans! - Backspace at the start of a block that follows a list or table no longer pulls that block into the list or table. An empty previous block is now only removed in place of the merge when it's a sibling; otherwise the block merges into it as usual.v0.130.2Compare Source
Patch Changes
7843bd5Thanks @dylans! - Moving whole lines by dragging or cutting no longer adds an empty line. Whole top-level blocks are now moved as blocks. Nested content, like list items and table cells, is moved without its trailing line break, so no containers get merged. Dropping text back onto its own selection is now a no-op, and drag-and-drop deletes througheditor.deleteFragment, like cut does, so plugins that guard deletion apply to both.v0.130.1Compare Source
Patch Changes
4a96e69Thanks @dylans! - MakeNode.fragmentonly walk the top-level blocks the range covers, so copying or cutting in a large document no longer takes time proportional to the whole document.v0.130.0Compare Source
Minor Changes
c760f06Thanks @dylans! - Deleting the only node in the editor, such as a lone image, now leaves an empty block instead of an editor with no children. An empty editor had no start point, so focusing or typing threw "Cannot get the start point in the node at path [] because it has no start text node".v0.129.0Compare Source
Minor Changes
1604e5fThanks @dylans! - Deleting a character or word from an empty block next to a block void now removes the empty block and selects the void, instead of deleting the void. This matches native editors. The previous behaviour deleted the image when pressing Backspace in an empty paragraph after it.Patch Changes
ff63fadThanks @dylans! - Deleting a single character next to, or inside, an empty non-void inline now removes the inline, instead of skipping over it and deleting the character on its other side.v0.128.0Compare Source
Patch Changes
#6115
52f05bf8Thanks @giaBaoJS! - - When deleting a void element backward from a cursor inside it, place the cursor before the removed void instead of moving it into the following node#6003
50cdf5e9Thanks @nabbydude! - Changed type signature ofEditor#setSelectionto allow non-Range properties of Selections (functionality unchanged)v0.127.1Compare Source
Patch Changes
fbe8e50bThanks @unrevised6419! - Declare@types/react(>=18.0.0) and@types/lodash(^4.14.0) as optional peer dependencies. The shipped type declarations import fromreactandlodashin type positions, but the typings packages were only listed indevDependencies. Under a hoistednode_moduleslayout that resolves by accident; under pnpm's isolated linker with a global virtual store it does not, and consumers getTS7016implicit-any errors (or silently degradedanyprops) for the editor components. Both entries are optional, so JavaScript-only consumers do not get unmet-peer warnings.v0.126.4Compare Source
Patch Changes
ad04f91cThanks @BetterAndBetterII! - SkipSelection.collapseToEnd()during composition selection-sync when the live DOM selection has no ranges, so a cleared selection no longer throwsInvalidStateErrorand unmounts the editor.v0.126.3Compare Source
Patch Changes
b96028a5Thanks @melodysdreamj! - Fix IME composition being cancelled on the first character typed into an empty leaf on Android, which left the first character behind as a separate, uncomposed character (typing 안녕 in Korean produced ㅇ안녕).v0.126.0Compare Source
Patch Changes
c5ea32eaThanks @greymoth-jp! - Treat Indic conjunct clusters as a single grapheme ingetCharacterDistance, implementing Unicode UAX #29 rule GB9c. Character-by-character cursor movement (Editor.positionswithunit: 'character', and theEditor.before/Editor.afterit powers) over scripts such as Devanagari and Bengali no longer stops inside aConsonant + virama + Consonantconjunct.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.