docs/slate-issues/open-issues-dossiers/5246-5130.md
These dossiers cover issues #5246 through #5130 from the pilot set. Use the top-level index for the range map and the ledger for the canonical structured cache.
getCharacterDistance in the string utils (and/or create a getCharacterLength method and expose that)thesunnyimprovement0Good API request. Consumers building rich text transforms need the same Unicode-aware character counting that Slate already uses internally.
No meaningful follow-up yet.
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.
rcbevansimprovement0Different Slate schemas can collide on the same clipboard fragment mime type. That is a real cross-editor isolation problem.
No meaningful follow-up yet.
Strong enough.
None.
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.
Nikhil22improvement1This is not one bug; it is a request for the selection layer to fail less catastrophically in production.
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.
v2-roadmap
Capture it as roadmap input instead of pretending it is a routine bugfix.
Direct.
skiddushpandabug, ⚑ cross platform0Safari gets visibly laggy when selecting backwards through long paragraphs.
This is a clean benchmark candidate: isolated browser, isolated workload, obvious user pain.
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.
kalda341bug4Autofocus can focus the editor without establishing a selection, which leaves it unfocusably dead until the user clicks.
Thread adds useful extra signal beyond the body and helped narrow the actual seam.
Strong.
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.
Direct.
joepie91improvement2The example copy overstates what it demonstrates. This is docs cleanup, but useful docs cleanup.
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.
None.
doflo-dfabug1This looked real in older versions, but the thread already says newer Slate versions no longer reproduce it.
Thread adds a few confirmations and small hints, but no deeper maintainer decision yet.
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.
wrongakrambug, ⚑ cross platform5Another version of the same external-update problem: route changes fetch new data, but Slate keeps rendering the old editor state.
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.
djibarianbug0unwrapNodes plus keyboard selection can leave the last list item orphaned instead of turning it into a paragraph.
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.
Sebbiditaicbug3Historical local install failure report. Important once, not architecture signal now.
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.
YaoKaiLunbug, ⚑ cross platform, android1Selecting an inline void on Android fails to summon the keyboard and can even collapse 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.
onChange callback called after editor and onChange are changedSmilinBrianbug1Replacing the editor instance and onChange callback can leave Slate calling the old callback.
Thread adds a few confirmations and small hints, but no deeper maintainer decision yet.
Strong.
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.
Direct.
qiooibug1Possible Android flush bug, but the thread never landed a concrete repro or even a stable version scope.
Thread adds a few confirmations and small hints, but no deeper maintainer decision 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.
Direct.
zeyad-ahmad-aqlbug, ⚑ cross platform4Android handling regressed badly after 0.82.0 and started treating the last inserted element as empty/zero-width.
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.
keep-open
Keep it in the active queue and narrow the exact failing seam with a repro or test.
Direct.
foolishwaybug, ⚑ cross platform0Programmatic focus on iOS is heavily browser-controlled. This reads more like platform limitation than Slate-specific breakage.
No meaningful follow-up 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.
qiooibug1Composition plus click-away generates a nasty browser event sequence that leaves Slate in a weird state.
Thread adds a few confirmations and small hints, but no deeper maintainer decision 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.
edmundsjimprovement1This is a product-positioning request for a batteries-included editor, not a flaw in Slate core. The thread already points at Plate.
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.
share-status
Share the current status, docs, or workaround instead of promising core work.
None.
mateuspireslbug0Updating the editor while Firefox thinks it is blurred can still trigger a bogus DOM selection reset.
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.
zeyad-ahmad-aqlbug1Another AndroidInputManager regression: inserting a paragraph leaves the last child empty.
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.
Direct.
jameshfisherbug12If a custom insertText intentionally does nothing, newer slate-react still lets the browser mutate the DOM, causing a DOM/Slate desync.
Thread adds useful extra signal beyond the body and helped narrow the actual seam.
Strong.
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.
Direct.
petrfejfarbug0Pasting over an empty or fully selected node can unexpectedly replace its type instead of preserving it.
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.
milapshah15bug, ⚑ cross platform3Chrome 105 introduced BOM weirdness in editable content. The thread points at other existing discussion and workarounds.
Thread adds useful extra signal beyond the body and helped narrow the actual seam.
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.
None.
KawhiWeibug2This is another undefined/invalid value integration problem, not an engine bug.
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.
macrozonebug0useSlate rerendering on every selection change is exactly the kind of subscription granularity problem that makes large editors feel heavier than they need to.
No meaningful follow-up yet.
Strong.
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.
Direct.
KatTurinibug12Android Firefox predictive typing duplicates characters, loses focus, and can even reverse the first word.
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.
Ready with minor setup.