docs/slate-issues/open-issues-dossiers/5479-5403.md
These dossiers cover issues #5479 through #5403 from the pilot set. Use the top-level index for the range map and the ledger for the canonical structured cache.
fernanda-getselectstarbug3GitBook paragraph-only paste failed in older Slate, but the thread says 0.98.3 works again.
The only real signal in the thread is that this was fixed in a later version, which knocks it down from active architecture pressure to stale clipboard history.
Strong enough.
Acceptable.
Stale candidate.
Treat this as stale or upstream-owned history, not active architecture pressure.
close-stale
Point at the likely resolution or upstream fix and close it if nobody can still reproduce.
Indirect.
edsyangfeature0This is a support request for React 15 compatibility, not a modern Slate bug.
No meaningful follow-up yet.
Strong enough.
Strong.
Invalid.
This is more about docs, support, or consumer expectations than a clean current core bug.
close-invalid
Point at the current contract or ownership boundary and close it.
None.
namfalbug0Deleting the only void node leaves the editor in an invalid empty-state path and then throws on the next focus/typing.
No meaningful follow-up yet.
Strong.
Poor.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it in the active queue and narrow the exact failing seam with a repro or test.
Direct.
PibeGimprovement0Deleting empty paragraphs does not trigger scroll recovery even when the caret leaves the viewport.
No meaningful follow-up yet.
Strong enough.
Poor.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it in the active queue and narrow the exact failing seam with a repro or test.
Indirect.
anneYanSiqianbug, ⚑ cross platform1This looks like an iOS layout quirk around editable paragraph display, not a well-owned Slate runtime failure.
Thread adds a few confirmations and small hints, but no deeper maintainer decision yet.
Strong enough.
Poor.
Likely invalid.
This is more about docs, support, or consumer expectations than a clean current core bug.
close-invalid
Point at the current contract or ownership boundary and close it.
None.
ReactEditor.hasDOMNode() returns incorrect?sws797none0This is a semantics question about ReactEditor.hasDOMNode, not a proven runtime bug yet.
No meaningful follow-up yet.
Strong enough.
Acceptable.
Unclear.
Keep it in the right cluster and do not let it drift into unrelated themes.
ask-for-scope-clarification
Ask for a reduced repro or a clearer ownership boundary first.
Indirect.
Noothan-amimprovement7This is just line-height/CSS confusion, not editor behavior.
Thread adds useful extra signal beyond the body and helped narrow the actual seam.
Strong enough.
Strong.
Invalid.
This is more about docs, support, or consumer expectations than a clean current core bug.
close-invalid
Point at the current contract or ownership boundary and close it.
None.
dearlordylordbug, ⚑ cross platform3Dead community links matter for docs hygiene, but they should not pollute product architecture work.
Thread adds useful extra signal beyond the body and helped narrow the actual seam.
Strong enough.
Strong.
Stale candidate.
Treat this as stale or upstream-owned history, not active architecture pressure.
close-stale
Point at the likely resolution or upstream fix and close it if nobody can still reproduce.
None.
JohnnyRacerbug0Image drag duplication appears in copied example code, but not on the official example, which makes ownership murky.
No meaningful follow-up yet.
Weak.
Poor.
Unclear.
Keep it in the right cluster and do not let it drift into unrelated themes.
ask-for-repro
Ask for a reduced repro before assigning real engineering weight to it.
Indirect.
Nefcantoimprovement1Good example request, but not a runtime gap.
Thread adds a few confirmations and small hints, but no deeper maintainer decision yet.
Strong enough.
Strong.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it in the active queue and narrow the exact failing seam with a repro or test.
None.
jrs64bug10Selecting text plus a readonly element and pressing Delete crashes the editor instead of deleting sanely.
Thread adds useful extra signal beyond the body and helped narrow the actual seam.
Strong.
Poor.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it in the active queue and narrow the exact failing seam with a repro or test.
Direct.
yiqingfengbug1Editable rerenders caused by decorate logic shove the caret forward during composition.
Thread adds a few confirmations and small hints, but no deeper maintainer decision yet.
Strong enough.
Poor.
Valid.
Known duplicate target: #5398.
keep-open
Keep it in the active queue and narrow the exact failing seam with a repro or test.
Direct.
HeartLFbug3The issue wants a different post-insert caret policy for links, but the thread already shows the current API pattern for getting it.
Thread adds useful extra signal beyond the body and helped narrow the actual seam.
Strong enough.
Strong.
Invalid.
This is more about docs, support, or consumer expectations than a clean current core bug.
close-invalid
Point at the current contract or ownership boundary and close it.
None.
SeongMinJinbug, ⚑ cross platform2Changing into responsive mode and refreshing exposes a hydration/runtime mismatch tied to platform detection.
Thread adds a few confirmations and small hints, but no deeper maintainer decision yet.
Strong enough.
Poor.
Likely valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it in the active queue and narrow the exact failing seam with a repro or test.
Indirect.
djibarianbug1Inserting a fragment into an empty node leaves the caret before the inserted content instead of after it.
Thread adds a few confirmations and small hints, but no deeper maintainer decision yet.
Strong.
Poor.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it in the active queue and narrow the exact failing seam with a repro or test.
Direct.
giorgoserabug2This looks like a testing-environment mismatch around contenteditable event simulation, not a clean product bug yet.
Thread adds a few confirmations and small hints, but no deeper maintainer decision yet.
Strong enough.
Acceptable.
Unclear.
Keep it in the right cluster and do not let it drift into unrelated themes.
ask-for-scope-clarification
Ask for a reduced repro or a clearer ownership boundary first.
None.
endercrestbug6The placeholder reappears too slowly after clearing content because the runtime deliberately delays it.
Thread adds useful extra signal beyond the body and helped narrow the actual seam.
Strong.
Poor.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it in the active queue and narrow the exact failing seam with a repro or test.
Indirect.
ABCDdouyaerbug4Classic uncontrolled-editor pain: replacing the value externally does not update the current editor state the way users expect.
Thread adds useful extra signal beyond the body and helped narrow the actual seam.
Strong enough.
Poor.
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 pretending it is a routine bugfix.
Direct.
gland2015feature0This asks for exporting private weak-map internals. That is a bad surface to stabilize lightly.
No meaningful follow-up yet.
Strong enough.
None.
Likely invalid.
This is more about docs, support, or consumer expectations than a clean current core bug.
close-invalid
Point at the current contract or ownership boundary and close it.
Indirect.
iNahooNyabug1insertText without a selection is a current-contract misunderstanding, not an engine failure.
Thread adds a few confirmations and small hints, but no deeper maintainer decision yet.
Strong enough.
Strong.
Invalid.
This is more about docs, support, or consumer expectations than a clean current core bug.
close-invalid
Point at the current contract or ownership boundary and close it.
None.
dylansbug0Recent changes broke Transforms.insertFragment(..., { at }) by routing through an editor method that ignores the explicit location.
No meaningful follow-up yet.
Strong.
Poor.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it in the active queue and narrow the exact failing seam with a repro or test.
Direct.
azvoncov-smartlingbug0A prior void-selection fix overcorrected and now misidentifies focus/anchor when the selection ends on a void node.
No meaningful follow-up yet.
Strong enough.
Poor.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it in the active queue and narrow the exact failing seam with a repro or test.
Direct.
aj0ximprovement0Browser extensions that mutate contenteditable state can break Slate. That is real pressure, but it is an engine-hardening direction, not a quick bugfix.
No meaningful follow-up yet.
Strong enough.
Poor.
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 pretending it is a routine bugfix.
Direct.
JarrodMFleschimprovement0Docs and code disagree on the return type of useSlateStatic, which makes the API feel less trustworthy than it should.
No meaningful follow-up yet.
Strong.
Poor.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it in the active queue and narrow the exact failing seam with a repro or test.
Indirect.
smith-rachael94none0Legit example request for a read-only truncate/expand pattern.
No meaningful follow-up yet.
Strong enough.
None.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
keep-open
Keep it in the active queue and narrow the exact failing seam with a repro or test.
None.
Not a direct test candidate.