docs/slate-issues/open-issues-dossiers/5402-5250.md
These dossiers cover issues #5402 through #5250 from the pilot set. Use the top-level index for the range map and the ledger for the canonical structured cache.
mohammad-saadatiimprovement1Repo cleanup nit, not product or architecture signal.
Thread adds a few confirmations and small hints, but no deeper maintainer decision yet.
Strong enough.
None.
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.
paulschreiberbug0The serialization docs show an import that shadows the browser Node global. This is docs friction, not runtime behavior.
No meaningful follow-up 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.
lovebzhoubug5External rerenders during composition push the caret backward and corrupt IME editing.
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.
keep-open
Keep it in the active queue and narrow the exact failing seam with a repro or test.
Direct.
josephmrbug, ⚑ cross platform1The reporter later reproduced this in plain HTML, which strongly suggests an iOS browser bug rather than a Slate-owned selection model bug.
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.
share-status
Share the current status, docs, or workaround instead of promising core work.
None.
data-slate-editor-id did not match (React, Slate, Next.js)DimitarIvanov7bug, ⚑ cross platform1Server and client generate different editor ids under SSR, which leaks as a Next.js hydration warning.
Thread adds a few confirmations and small hints, but no deeper maintainer decision yet.
Strong enough.
Acceptable.
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.
GilHelfgottGongbug2This turns out to be missing white-space: pre-wrap when opting out of the default styles.
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.
zeyad-ahmad-aqlimprovement4Historical roadmap request. Slate already moved forward here; this should not stay hot.
Thread adds useful extra signal beyond the body and helped narrow the actual seam.
Strong enough.
None.
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.
oustrbug3Dragging a multi-line selection can create extra lines in some browsers, but the reproduction is fussy and not everyone could repeat it.
Thread adds useful extra signal beyond the body and helped narrow the actual seam.
Strong enough.
Poor.
Likely valid.
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.
oustrbug0IME input at the end of an inline element crashes or becomes impossible depending on the browser.
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.
edhagerbug, ⚑ cross platform0Selecting a suggested word inserts it, but leaves the cursor inside the word instead of after it.
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.
AbhishekSKini1317bug0This smells like a custom mark/color implementation problem, not a proven slate-history core failure.
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-scope-clarification
Ask for a reduced repro or a clearer ownership boundary first.
Indirect.
jayaikeimprovement12This is a real architecture pressure point: the default normalization model is too rigid for nested-block use cases.
Thread adds useful extra signal beyond the body and helped narrow the actual seam.
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 pretending it is a routine bugfix.
Direct.
instadrewnone0Table navigation with colgroup/col children is probably custom-table territory, not a clean Slate core contract yet.
No meaningful follow-up yet.
Strong enough.
Poor.
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.
ProofOfKeagsbug4This is the empty-editor contract problem again: [] looks reasonable, but the current runtime expects a focusable descendant shape and the docs do not state that sharply enough.
Thread adds useful extra signal beyond the body and helped narrow the actual seam.
Strong enough.
Acceptable.
Likely invalid.
This is more about docs, support, or consumer expectations than a clean current core bug.
share-status
Share the current status, docs, or workaround instead of promising core work.
Direct.
ivxvmimprovement2Mostly GitBook platform limitations, not Slate docs content itself.
Thread adds a few confirmations and small hints, but no deeper maintainer decision yet.
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.
947776795bug0The report claims renderElement keeps firing after deleting all content, but it never really narrows expected versus surprising render behavior.
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.
##)sambowenhughesbug0This is a mismatch between what the markdown example supports and what the user assumed it should parse.
No meaningful follow-up yet.
Strong enough.
Acceptable.
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.
/data-slate-fragment="(.+?)"/ in text12joanbug, ⚑ cross platform0Clipboard HTML parsing is too permissive and mistakes arbitrary text for a Slate fragment token.
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.
robinsonlin0603bug, ⚑ cross platform4On Android, long blocks combined with viewport scrolling can snap the cursor back to the first line.
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.
keep-open
Keep it in the active queue and narrow the exact failing seam with a repro or test.
Direct.
kristian-pucciobug, ⚑ needs info9Editor.isBlock returns surprising truthy results for values that are not elements, which is hostile both at runtime and in wrapper libraries.
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.
macrozonefeature8This is the direct “make Slate controlled again” version of the same runtime/API pain that keeps resurfacing.
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.
vamsimudadlabug1The extra blank lines come from the consumer DOM wrapper shape, not a core Slate copy pipeline bug.
Thread adds a few confirmations and small hints, but no deeper maintainer decision yet.
Strong enough.
Strong.
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.
MaxPower15bug0Clicks that change selection can be immediately reverted if Slate is mid-render, which is exactly the kind of runtime fight React users hate.
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.
simon-guiderfeature0Reasonable adapter request, but this belongs more to ecosystem conversion tooling than Slate core.
No meaningful follow-up yet.
Strong enough.
None.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
share-status
Share the current status, docs, or workaround instead of promising core work.
Indirect.
JokerLHFbug1The thread says this breaks because the initial data is not normalized; history is just exposing that fact.
Thread adds a few confirmations and small hints, but no deeper maintainer decision yet.
Strong enough.
Acceptable.
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.
Not a direct test candidate.