docs/slate-issues/open-issues-dossiers/4541-4392.md
codewitchbug6editor.selection lags behind repeated text insertion, which makes imperative logic read stale cursor state during typing.
The comments identify a likely regression point and confirm the problem persisted far beyond the original report, so this is real runtime debt rather than one confused consumer report.
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 seam instead of letting it dissolve into vague frustration.
Direct.
Ready now.
Nantrisbug0Shift-clicking into an inline link collapses the selection instead of expanding it, so inline boundaries still behave differently from ordinary text.
The report is tight, reproducible on the official links example, and there is no noise in the thread.
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 seam instead of letting it dissolve into vague frustration.
Direct.
Ready now.
churichardbug, ⚑ cross platform0The markdown-shortcuts example does not convert prefix shortcuts on Android, which exposes a real mobile gap but in an example-specific seam first.
There is no deeper thread, so this is useful as signal but should not be overweighted as core architecture on its own.
Strong enough.
Poor.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
share-status
Reply with the current scope and route people to the right layer.
Indirect.
Not a direct test candidate.
churichardbug, ⚑ cross platform1Android autocorrect suggestions flicker and lose context, which points to Slate fighting the platform text input pipeline rather than cooperating with it.
The workaround comment points at unnecessary DOM text updates, which makes this more useful than a vague Android complaint.
Strong enough with minor setup.
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 seam instead of letting it dissolve into vague frustration.
Direct.
Ready with minor setup.
churichardbug2Triple-click selection breaks when a checklist item follows the block, which suggests the rendered checklist structure is tripping browser selection semantics.
The comments connect it to known rendering changes and provide a rendering workaround, so this is more than random example noise.
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 seam instead of letting it dissolve into vague frustration.
Indirect.
Ready now.
Lalitj03bug, ⚑ cross platform2Pressing Enter in heading blocks on Android produces the wrong DOM shape and drops the first typed character, so block tag choice still changes input correctness.
One comment blames Gboard, another reproduces with other keyboards and ships a patch, so this cannot just be dismissed as one vendor bug.
Strong enough with minor setup.
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 seam instead of letting it dissolve into vague frustration.
Direct.
Ready with minor setup.
bryanphbug, ⚑ cross platform7The root cause ended up pointing at a React 17 Firefox event bug, not a clean Slate-owned behavior contract.
The comments are useful because they show the symptom is real, but the final trail points outside Slate.
Strong enough.
Poor.
Invalid.
This sits outside Slate's current contract or points at an external/browser/framework problem.
close-invalid
Close it and point at the actual owning layer or unsupported scope.
None.
Not a direct test candidate.
sarahdayanbug3Imperative focus handoff between multiple Slate editors is unstable, which matters a lot for Notion-style block editors.
The thread already contains a partial workaround using Transforms.select, which makes this a clear runtime contract problem rather than misuse.
Strong enough with minor setup.
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 seam instead of letting it dissolve into vague frustration.
Direct.
Ready with minor setup.
andrewMyronovbug0This is another Cannot resolve a DOM point crash report, but the thread never got past a large app snippet and a generic symptom.
There is no reduced repro and no maintainer follow-up, so the signal is real but still too muddy for strong classification.
Weak. The thread still needs a reduced repro.
Poor.
Unclear.
The symptom is plausible, but the thread never produced a reduced repro strong enough for confident triage.
ask-for-repro
Ask for a reduced repro before letting it shape roadmap work.
Indirect.
Blocked until the thread has a real reduced repro.
jakedimprovement7Dynamic decorations are still too global and too expensive, and the reporter already measured a huge win from a more local render API.
This is one of the stronger performance-shaped API issues because it has a clear workload, a plausible seam, and concrete before/after numbers.
Strong enough.
Poor.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
v2-roadmap
Keep it on the v2/runtime roadmap, not in generic bug triage.
Direct.
Not a direct test candidate.
5andufeature0Selection-anchored comments for collaborative writing are a real capability request, but this is product-layer pressure rather than a precise current bug.
There is no thread, so it should inform roadmap thinking without pretending it is a tightly specified implementation target.
Strong enough.
None.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
v2-roadmap
Keep it on the v2/runtime roadmap, not in generic bug triage.
Direct.
Not a direct test candidate.
yusonghuilifebug0Word-jump navigation in Chinese does not match native contenteditable behavior, so Slate hotkey logic is still too western-text-centric.
The report is small but concrete and points directly at the hotkey detection seam.
Strong enough with minor setup.
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 seam instead of letting it dissolve into vague frustration.
Direct.
Ready with minor setup.
amirHosseinKhademiifeature1This is a low-level API ergonomics request for “no user typing, but still allow programmatic transforms”.
A simple onKeyDown workaround exists in the thread, so this should stay de-weighted.
Strong enough.
Strong.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
share-status
Reply with the current scope and route people to the right layer.
Indirect.
Not a direct test candidate.
bharatnbug2Normalization over mixed block and newline text children can delete the wrong sibling because index accounting drifts after removal.
The report is low on polish but unusually strong on root-cause detail, so it is worth taking seriously.
Strong enough with minor setup.
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 seam instead of letting it dissolve into vague frustration.
Direct.
Ready with minor setup.
rmccueimprovement9Clipboard serialization is still too closed over DOM-derived defaults, which makes advanced export use cases brittle.
The thread is valuable because it moves past one proposed method and surfaces the deeper question of where clipboard policy should live.
Strong enough.
Acceptable.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
v2-roadmap
Keep it on the v2/runtime roadmap, not in generic bug triage.
Direct.
Not a direct test candidate.
echarlesfeature2This is effectively a request for Slate to become a richer code editor platform, not a concrete bug or realistic core feature seam.
The maintainer reply already redirects toward Monaco-level tradeoffs, which is the right call.
Strong enough.
Strong.
Invalid.
This sits outside Slate's current contract or points at an external/browser/framework problem.
close-invalid
Close it and point at the actual owning layer or unsupported scope.
None.
Not a direct test candidate.
mwood23feature4This asks for transitory masked ranges that do not pollute document state, which is exactly the kind of runtime-only overlay problem current decorations handle poorly.
The thread is thoughtful and explicitly tries to keep editor state pure, which makes it useful v2 pressure.
Strong enough.
Poor.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
v2-roadmap
Keep it on the v2/runtime roadmap, not in generic bug triage.
Direct.
Not a direct test candidate.
AndroidEditable interfering with IMELannybug, ⚑ cross platform5AndroidEditable is still a major architecture smell: removing it fixes composition in the report, and the thread explicitly calls out the cost of maintaining a forked mobile editor path.
This is one of the most valuable Android issues because it surfaces both the symptom and the likely architectural reason.
Strong enough with minor setup.
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 seam instead of letting it dissolve into vague frustration.
Direct.
Ready with minor setup.
schlengerimprovement7The TypeScript docs and walkthroughs were faulty enough to trip beginners repeatedly, which makes this real docs debt, not picky formatting feedback.
The comments confirm the problem persisted for years, which is enough to keep it visible in maintainer triage.
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 scope and route people to the right layer.
None.
Not a direct test candidate.
mylvghbimprovement5Cross-node decoration works in principle, but the current API shape falls apart around voids and practical example coverage.
The comments are actually useful because they show the current mechanism is close, but still awkward enough to keep surfacing.
Strong enough.
Acceptable.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
v2-roadmap
Keep it on the v2/runtime roadmap, not in generic bug triage.
Direct.
Not a direct test candidate.
hans000feature0This is a small selection utility ergonomics request, not a serious engine failure.
There is no thread depth here, so it should stay low priority.
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 scope and route people to the right layer.
None.
Not a direct test candidate.
JonasKruckenbergfeature12The Text shape is a real interoperability barrier with the unist/unified ecosystem, but solving it is a deep model decision, not a local patch.
The long thread is useful because it explores the realistic options and makes the DX tradeoffs obvious.
Strong enough.
Acceptable.
Valid.
Keep it in the right cluster and do not let it drift into unrelated themes.
v2-roadmap
Keep it on the v2/runtime roadmap, not in generic bug triage.
Direct.
Not a direct test candidate.
YaoKaiLunbug2This looks more like a failed repro or user-environment mismatch than a stable core bug.
The only substantive comment says the shortcuts work as expected and the reporter never followed up.
Strong enough.
Strong.
Likely invalid.
This sits outside Slate's current contract or points at an external/browser/framework problem.
close-invalid
Close it and point at the actual owning layer or unsupported scope.
None.
Not a direct test candidate.
Harsh1796bug, ⚑ cross platform10Safari blur handling still nulls selection in ways that break toolbars and cross-browser consistency.
The thread is strong because it ties the regression to a previous Safari workaround and shows why the workaround is still not good enough.
Strong enough with minor setup.
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 seam instead of letting it dissolve into vague frustration.
Direct.
Ready with minor setup.
arminbrobug, ⚑ cross platform1Deleting all marked-up content on iPhone Safari can leave the editor in a dead input state.
There is no deep thread, but the repro is clear and serious enough on its own.
Strong enough with minor setup.
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 seam instead of letting it dissolve into vague frustration.
Direct.
Ready with minor setup.