docs/slate-issues/open-issues-dossiers/3313-2733.md
stevez86bug, ♥ help5Android text input should not corrupt selection or inject unexpected text in the empty editor.
The comments mostly collapse this into an existing issue family instead of creating a new one.
The thread points to Issue #3112, which helps anchor this issue in the broader issue history.
Strong enough.
Poor.
Duplicate candidate.
Keep the signal, but fold it into the stronger parent instead of counting it twice.
close-duplicate
Point to the stronger parent and preserve the useful context.
Direct.
Not a direct test candidate.
select option to all transformsianstormtaylorimprovement, ♥ help0Transforms should let callers opt into selection updates separately from at.
The discussion matters because it exposes design pressure rather than a small isolated patch target.
No linked artifacts surfaced in the current thread.
Strong enough.
Acceptable.
Valid.
Keep it in the corpus as a real current or long-lived issue.
v2-roadmap
Acknowledge the pressure and frame it as roadmap or v2 design input, not a small patch.
Indirect.
Not a direct test candidate.
jege31bug, ⚑ needs tests, ⚑ needs fixing12Decorated text should stay selectable without DOM point resolution crashes.
The comments add recurring workarounds and edge cases, which makes the pressure clearer than the title alone.
No linked artifacts surfaced in the current thread.
Strong enough.
Acceptable.
Valid.
Keep it in the corpus as a real current or long-lived issue.
keep-open
Acknowledge the pain and keep the issue attached to the right cluster.
Direct.
Ready for a red test.
insertFromDrop beforeinput events for filesianstormtaylor⚑ cross platform0File drops should have a stable public handling path when Chrome skips insertFromDrop beforeinput.
The thread is thin, so the issue body carries most of the signal.
No linked artifacts surfaced in the current thread.
Strong enough.
Poor.
Valid.
Keep it in the corpus as a real current or long-lived issue.
share-status
Share the current status and keep the issue attached to the right design seam.
Indirect.
Not a direct test candidate.
insertFromComposition eventsianstormtaylor⚑ cross platform0Composition commit should have a stable public handling path when Chrome skips insertFromComposition.
The thread is thin, so the issue body carries most of the signal.
No linked artifacts surfaced in the current thread.
Strong enough.
Poor.
Valid.
Keep it in the corpus as a real current or long-lived issue.
share-status
Share the current status and keep the issue attached to the right design seam.
Indirect.
Not a direct test candidate.
ianstormtaylor♥ help, debt, examples0The examples site should not depend on an unnecessary dynamic Next.js directory shape.
The thread is thin, so the issue body carries most of the signal.
No linked artifacts surfaced in the current thread.
Not worth strengthening until the current status is fresh.
Strong.
Stale candidate.
Treat it as historical signal unless someone proves the current branch still reproduces it.
close-stale
Ask for a fresh repro before anyone burns more time on it.
None.
Not a direct test candidate.
dmarkowbug, ♥ help5Void embed examples should allow editing the nested URL input without immediately hiding it.
The thread mostly points toward an older fix path, so this reads more like historical signal than an active bug line.
The thread points to PR #3389, PR #3516, which helps anchor this issue in the broader issue history.
Not worth strengthening until the current status is fresh.
Acceptable.
Stale candidate.
Treat it as historical signal unless someone proves the current branch still reproduces it.
close-stale
Ask for a fresh repro before anyone burns more time on it.
Indirect.
Not a direct test candidate.
normalizeNode to receive only a pathianstormtaylordebt, ✶ breaking0NormalizeNode overrides should not receive stale node entries after mutation.
The discussion matters because it exposes design pressure rather than a small isolated patch target.
The thread points to Issue #3273, which helps anchor this issue in the broader issue history.
Strong enough.
Acceptable.
Valid.
Keep it in the corpus as a real current or long-lived issue.
v2-roadmap
Acknowledge the pressure and frame it as roadmap or v2 design input, not a small patch.
Direct.
Not a direct test candidate.
timothyarmes♥ help, examples2The mentions example should not crash when the editor becomes empty.
The thread mostly points toward an older fix path, so this reads more like historical signal than an active bug line.
The thread points to PR #3270, which helps anchor this issue in the broader issue history.
Not worth strengthening until the current status is fresh.
Strong.
Stale candidate.
Treat it as historical signal unless someone proves the current branch still reproduces it.
close-stale
Ask for a fresh repro before anyone burns more time on it.
None.
Not a direct test candidate.
meanGoreng⚑ needs info, ⚑ needs gif0Rehydrated HTML content should let marks toggle off again after load.
The thread is thin, so the issue body carries most of the signal.
No linked artifacts surfaced in the current thread.
Weak.
Poor.
Unclear.
Keep it low-weight until a maintainer or reproducer sharpens it.
ask-for-repro
Request a minimal repro and avoid overcommitting before that exists.
Indirect.
Blocked until someone refreshes the repro.
maksimsemenovdiscussion3Match callbacks should have access to editor context when cross-node checks are needed.
The discussion matters because it exposes design pressure rather than a small isolated patch target.
No linked artifacts surfaced in the current thread.
Strong enough.
Acceptable.
Valid.
Keep it in the corpus as a real current or long-lived issue.
v2-roadmap
Acknowledge the pressure and frame it as roadmap or v2 design input, not a small patch.
Indirect.
Not a direct test candidate.
focuxdiscussion10Feature logic should have a more coherent extension seam than scattered commands plus render props.
The discussion matters because it exposes design pressure rather than a small isolated patch target.
The thread points to Issue #3177, which helps anchor this issue in the broader issue history.
Strong enough.
Acceptable.
Valid.
Keep it in the corpus as a real current or long-lived issue.
v2-roadmap
Acknowledge the pressure and frame it as roadmap or v2 design input, not a small patch.
Direct.
Not a direct test candidate.
0.50+ianstormtaylor✶ announcement!0Release announcements and migration guides should not linger as open issues.
The thread is thin, so the issue body carries most of the signal.
No linked artifacts surfaced in the current thread.
Not worth strengthening until the current status is fresh.
Strong.
Stale candidate.
Treat it as historical signal unless someone proves the current branch still reproduces it.
close-stale
Ask for a fresh repro before anyone burns more time on it.
None.
Not a direct test candidate.
PeterKottas⚑ needs gif1unwrapNodes with split: true should only unwrap the selected inline segment.
The comments sharpen the problem a bit, but the issue body still carries most of the signal.
No linked artifacts surfaced in the current thread.
Strong enough.
Poor.
Valid.
Keep it in the corpus as a real current or long-lived issue.
keep-open
Acknowledge the pain and keep the issue attached to the right cluster.
Direct.
Ready for a red test.
sherwinyuquestion4RenderElement composition should be easier to extend across editor packages or plugin layers.
The discussion matters because it exposes design pressure rather than a small isolated patch target.
The thread points to Issue #3222, which helps anchor this issue in the broader issue history.
Strong enough.
Acceptable.
Valid.
Keep it in the corpus as a real current or long-lived issue.
v2-roadmap
Acknowledge the pressure and frame it as roadmap or v2 design input, not a small patch.
Direct.
Not a direct test candidate.
Jokcybug, ♥ help, ⚑ ime9IME input inside decorated text should not desync the DOM and Slate text.
The comments add recurring workarounds and edge cases, which makes the pressure clearer than the title alone.
No linked artifacts surfaced in the current thread.
Strong enough.
Poor.
Valid.
Keep it in the corpus as a real current or long-lived issue.
keep-open
Acknowledge the pain and keep the issue attached to the right cluster.
Direct.
Ready with minor setup.
ianstormtaylorimprovement, ♥ help0Fragment insertion should stop blindly merging structural blocks at both ends.
The discussion matters because it exposes design pressure rather than a small isolated patch target.
The thread points to PR #1366, PR #2589, which helps anchor this issue in the broader issue history.
Strong enough.
None.
Valid.
Keep it in the corpus as a real current or long-lived issue.
v2-roadmap
Acknowledge the pressure and frame it as roadmap or v2 design input, not a small patch.
Direct.
Not a direct test candidate.
insert_text on edges of inlines/marksianstormtaylorimprovement, ♥ help1insert_text at inline or mark edges should be canonicalized instead of delegating to browser quirks.
The discussion matters because it exposes design pressure rather than a small isolated patch target.
The thread points to Issue #3148, which helps anchor this issue in the broader issue history.
Strong enough.
None.
Valid.
Keep it in the corpus as a real current or long-lived issue.
v2-roadmap
Acknowledge the pressure and frame it as roadmap or v2 design input, not a small patch.
Direct.
Ready for a red test.
ianstormtaylor⚑ cross platform0Known upstream browser and React event gaps should stay tracked as boundary constraints.
The thread is thin, so the issue body carries most of the signal.
The thread points to Issue #3148, Issue #3303, Issue #3304, which helps anchor this issue in the broader issue history.
Strong enough.
Acceptable.
Valid.
Keep it in the corpus as a real current or long-lived issue.
share-status
Share the current status and keep the issue attached to the right design seam.
Indirect.
Not a direct test candidate.
ianstormtaylor⚑ cross platform0Inline boundary selections should be representable even when Chrome or Safari refuse to place them naturally.
The thread is thin, so the issue body carries most of the signal.
No linked artifacts surfaced in the current thread.
Strong enough.
Poor.
Valid.
Keep it in the corpus as a real current or long-lived issue.
share-status
Share the current status and keep the issue attached to the right design seam.
Direct.
Not a direct test candidate.
0.50gracicotdiscussion1Android editing should handle selection changes, autocomplete, and deletion without falling apart.
The discussion matters because it exposes design pressure rather than a small isolated patch target.
No linked artifacts surfaced in the current thread.
Strong enough.
Poor.
Valid.
Keep it in the corpus as a real current or long-lived issue.
v2-roadmap
Acknowledge the pressure and frame it as roadmap or v2 design input, not a small patch.
Direct.
Not a direct test candidate.
split_node operations to include the full targetianstormtaylorimprovement, idea1split_node operations should carry enough target data for correct OT transforms.
The discussion matters because it exposes design pressure rather than a small isolated patch target.
No linked artifacts surfaced in the current thread.
Strong enough.
None.
Valid.
Keep it in the corpus as a real current or long-lived issue.
v2-roadmap
Acknowledge the pressure and frame it as roadmap or v2 design input, not a small patch.
Direct.
Not a direct test candidate.
ianstormtaylordiscussion7Inline adjacency should not force junk surrounding text nodes into the document model.
The discussion matters because it exposes design pressure rather than a small isolated patch target.
No linked artifacts surfaced in the current thread.
Strong enough.
Acceptable.
Valid.
Keep it in the corpus as a real current or long-lived issue.
v2-roadmap
Acknowledge the pressure and frame it as roadmap or v2 design input, not a small patch.
Direct.
Not a direct test candidate.
turt2livediscussion0Screen readers should keep virtual focus inside the editor after pressing Enter.
The discussion matters because it exposes design pressure rather than a small isolated patch target.
No linked artifacts surfaced in the current thread.
Strong enough.
Poor.
Valid.
Keep it in the corpus as a real current or long-lived issue.
v2-roadmap
Acknowledge the pressure and frame it as roadmap or v2 design input, not a small patch.
Direct.
Not a direct test candidate.
Nantris⚑ perf, discussion0ApplyOperation scheduling changes should improve performance without breaking focus responsiveness.
The thread is thin, so the issue body carries most of the signal.
No linked artifacts surfaced in the current thread.
Not worth strengthening until the current status is fresh.
Poor.
Stale candidate.
Treat it as historical signal unless someone proves the current branch still reproduces it.
close-stale
Ask for a fresh repro before anyone burns more time on it.
None.
Not a direct test candidate.