docs/slate-issues/open-issues-dossiers/4839-4742.md
instadrewbug7The caret cannot reliably land to the right of a line-ending inline void, which makes inline void boundaries behave like traps.
The thread has workarounds, related regressions, and a likely regressing PR, so this is strong runtime signal.
Strong enough.
Acceptable.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it open and scoped to the actual failing seam instead of letting it dissolve into vague frustration.
Direct.
Ready now.
jasontlourobug0Using the left arrow to move up the document scrolls far more aggressively than the equivalent up-arrow path.
The report is concise but the repro is clear and based on official examples.
Strong enough.
Poor.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it open and scoped to the actual failing seam instead of letting it dissolve into vague frustration.
Indirect.
Ready now.
ElizavetaKorolevabug0A translation browser extension mutates the DOM around selection and Slate breaks.
That is exactly the kind of external DOM mutation Slate cannot reasonably own.
Strong enough.
Strong.
Invalid.
This is mostly unsupported or invalid current-contract behavior.
close-invalid
Close it as unsupported or out-of-contract behavior instead of pretending it is core debt.
None.
Not a direct test candidate.
mariasimobug, ⚑ cross platform0The hovering toolbar example regressed so that blur outside the editor no longer hides the toolbar.
This is a clean example/runtime regression, not a vague question.
Strong enough.
Poor.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it open and scoped to the actual failing seam instead of letting it dissolve into vague frustration.
Indirect.
Ready now.
jaykou25bug1Backward multi-element delete leaves the wrong formatting context because it preserves the anchor element instead of the focus element.
The thread even points at the suspicious line, so this is good current test fodder.
Strong enough.
Poor.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it open and scoped to the actual failing seam instead of letting it dissolve into vague frustration.
Direct.
Ready now.
ShafSpecsbug1There seems to be a Firefox-specific line-height regression in Editable where cursor movement jumps multiple lines.
The maintainer comment makes it plausible, but the issue still needs a tighter repro before it carries much more weight.
Weak.
Poor.
Likely valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it open and scoped to the actual failing seam instead of letting it dissolve into vague frustration.
Indirect.
Blocked on a tighter repro.
laufeyrutbug1Inline void content like mentions does not round-trip cleanly through copy-paste.
There is at least one plausible workaround note, but the default behavior still looks wrong enough to track.
Strong enough.
Acceptable.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it open and scoped to the actual failing seam instead of letting it dissolve into vague frustration.
Indirect.
Ready now.
laufeyrutbug3Copying Slate content with inline voids into other editors inserts bogus newlines and formatting artifacts.
The thread actually narrows likely causes, so this is a useful serialization/export issue, not just user annoyance.
Strong enough.
Poor.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it open and scoped to the actual failing seam instead of letting it dissolve into vague frustration.
Indirect.
Ready now.
cansonkaibug0Importing package internals from local source paths is unsupported and predictably explodes on missing built exports.
This is integration misuse, not product debt.
Strong enough.
Strong.
Invalid.
This is mostly unsupported or invalid current-contract behavior.
close-invalid
Close it as unsupported or out-of-contract behavior instead of pretending it is core debt.
None.
Not a direct test candidate.
Perfecto-alwaysbug3Text-limit plugins cannot reliably veto insertion because native beforeinput flows differ by character class and can bypass the intended constraint logic.
This is strong plugin seam signal, not just one consumer plugin bug.
Strong enough.
Poor.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it open and scoped to the actual failing seam instead of letting it dissolve into vague frustration.
Direct.
Ready now.
quoctienktfeature1This is a request for richer external deserializers and format-preserving paste, not a clean current-core bug.
The maintainer answer already points at deserializers and ecosystem solutions, which is the right bucket.
Strong enough.
Acceptable.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
share-status
Reply with the current contract and the right ownership boundary instead of overpromising a fix.
None.
Not a direct test candidate.
DominikSerafinbug2Starting selection outside the editor and ending inside can desync DOM and model state badly enough to throw or render unsaved text.
This is one of the better bridge issues in the batch because it exposes a real partial-state failure, not just a cursor annoyance.
Strong enough.
Poor.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it open and scoped to the actual failing seam instead of letting it dissolve into vague frustration.
Direct.
Ready now.
Nefcantoimprovement4Users still want JS versions of the examples instead of forcing everyone through TSX and transpilation tools just to prototype.
The thread is constructive and points at automation, so this is real docs friction, not random anti-TypeScript whining.
Strong enough.
Acceptable.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
share-status
Reply with the current contract and the right ownership boundary instead of overpromising a fix.
None.
Not a direct test candidate.
jackow98bug0Dragging nested blocks with react-beautiful-dnd can race with Slate path bookkeeping and crash on stale child paths.
There is a real repro, but ownership still spans consumer DnD behavior and Slate’s runtime assumptions.
Strong enough.
Poor.
Unclear.
The report is not sharp enough yet to carry strong architecture weight.
share-status
Reply with the current contract and the right ownership boundary instead of overpromising a fix.
Indirect.
Ready with minor setup.
wanglophilebug4The paste HTML example is too simple to preserve the nested blockquote formatting users expect, especially around whitespace and nested tags.
This belongs in example/docs scope, not as a claim that Slate core should magically deserialize every external HTML shape.
Strong enough.
Acceptable.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
share-status
Reply with the current contract and the right ownership boundary instead of overpromising a fix.
None.
Not a direct test candidate.
gingraybug0Deleting the last node can leave Slate chasing a descendant path that no longer exists and crash.
The timeout workaround smell and linked PR context make this worth keeping in current core correctness work.
Strong enough.
Poor.
Likely valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it open and scoped to the actual failing seam instead of letting it dissolve into vague frustration.
Direct.
Ready now.
jameshfisherbug3Windows emoji insertion at the end of an inline can duplicate the emoji and leave the editor in a broken state.
The issue is detailed and compares Slate against plain contenteditable, which makes it a strong input-boundary bug.
Strong enough.
Poor.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it open and scoped to the actual failing seam instead of letting it dissolve into vague frustration.
Direct.
Ready with minor setup.
luzzardikbug, ⚑ cross platform2Safari dead-key composition with ^ can send the caret to the wrong place and reverse or dislocate inserted text.
The thread shows keyboard-layout sensitivity, so this is real but still awkward to reduce into a stable test seam.
Weak.
Poor.
Likely valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it open and scoped to the actual failing seam instead of letting it dissolve into vague frustration.
Indirect.
Blocked on a tighter repro.
ahoislbug0EditableProps advertises textarea-style props that the component does not actually support, which is a type-surface lie.
This is a good typing/API cleanup issue, not a runtime bug.
Strong enough.
Acceptable.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it open and scoped to the actual failing seam instead of letting it dissolve into vague frustration.
Direct.
Not a direct test candidate.
zhugexinxinbug0This is basically a support question about measuring DOM height in a custom table implementation.
There is not enough issue detail here to turn it into architecture signal.
Weak.
Poor.
Unclear.
The report is not sharp enough yet to carry strong architecture weight.
ask-for-repro
Ask for a tighter reduced repro before letting it influence architecture or roadmap work.
None.
Blocked on a tighter repro.
Hashemian01bug5RTL list items do not follow the same bidi behavior users see in other block types in the demo.
The thread is half bug report and half product-expectation argument, so it should not be overweighted without a more precise contract.
Strong enough.
Acceptable.
Unclear.
The report is not sharp enough yet to carry strong architecture weight.
share-status
Reply with the current contract and the right ownership boundary instead of overpromising a fix.
Indirect.
Not a direct test candidate.
gaoyuan1223mbug, ⚑ cross platform1This is old iOS browser support drift, not a target worth reshaping modern Slate around.
The maintainer reply already frames it correctly: unsupported old platform unless someone wants to contribute a non-invasive fix.
Strong enough.
Acceptable.
Stale candidate.
This likely belongs in stale-history cleanup, not active architecture work.
close-stale
Close it as stale history unless someone can still reproduce it on a current release.
None.
Not a direct test candidate.
Editor.marks(editor) returns only the first selected leaf marksobeckmanbug3Editor.marks(editor) only reflects the first selected leaf, but many consumers want an aggregated answer across the whole selection.
The workaround exists, but the request is really for a different API contract, not a tiny bugfix.
Strong enough.
Acceptable.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
v2-roadmap
Capture it as roadmap input instead of treating it like routine bug debt.
Direct.
Not a direct test candidate.
jackow98bug0setNodes with a match predicate can silently miss inline nodes after a reload even though a direct path still works.
The workaround is clear, but the issue still needs a tighter reduced repro before pretending the root cause is obvious.
Strong enough.
Acceptable.
Likely valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it open and scoped to the actual failing seam instead of letting it dissolve into vague frustration.
Direct.
Ready with minor setup.
gitcatratfeature0This is a request for a public support-detection hook so consumers can fall back to a textarea on unsupported environments.
Reasonable idea, but it belongs in support-matrix discussion, not as proof that the core model is wrong.
Strong enough.
Acceptable.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
share-status
Reply with the current contract and the right ownership boundary instead of overpromising a fix.
None.
Not a direct test candidate.