docs/slate-issues/open-issues-dossiers/3433-3317.md
horsen689none0Toolbar-driven Editor.addMark after blur should not collapse into null marks.
The comments mostly collapse this into an existing issue family instead of creating a new one.
No linked artifacts surfaced in the current thread.
Strong enough.
Acceptable.
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.
Indirect.
Not a direct test candidate.
plbabinnone0Placeholder visibility should recalculate when child count changes even if Editor.string stays empty.
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.
keep-open
Acknowledge the pain and keep the issue attached to the right cluster.
Direct.
Ready for a red test.
DanweDEnone1Typing or deleting in a paragraph with many inline nodes should not rerender the whole paragraph or freeze.
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.
Not a direct test candidate.
skokenesnone1Caret before a padded inline should stay outside the inline instead of rendering inside it.
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.
Likely valid.
Keep it in the corpus; the signal is stronger than the uncertainty.
keep-open
Acknowledge the pain and keep the issue attached to the right cluster.
Direct.
Ready with minor setup.
inline-block elementplbabinbug, ♥ help1inline-block elements should not swallow caret rendering or mod-arrow navigation.
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 with minor setup.
cboppertnone37Blur to a toolbar or dialog should not destroy the logical selection needed for follow-up commands.
The comments add recurring workarounds and edge cases, which makes the pressure clearer than the title alone.
The thread points to PR #3388, 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.
keep-open
Acknowledge the pain and keep the issue attached to the right cluster.
Direct.
Ready for a red test.
zbeyensnone3DeleteBackward into an empty list or table block should not replace the previous node with the current one.
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.
Acceptable.
Unclear.
Keep it low-weight until a maintainer or reproducer sharpens it.
keep-open
Acknowledge the pain and keep the issue attached to the right cluster.
Direct.
Ready for a red test.
takhtamyshbug, ♥ help8Triple-click paragraph selection followed by typing should replace the paragraph in place.
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.
Likely valid.
Keep it in the corpus; the signal is stronger than the uncertainty.
keep-open
Acknowledge the pain and keep the issue attached to the right cluster.
Direct.
Ready with minor setup.
arpit016bug, ♥ help, examples0The checklist example should not copy checked state or strikethrough to the next item on Enter.
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.
None.
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.
BetaAIimprovement, discussion12Overlapping marks or decorations with the same semantic key should preserve both payloads.
The discussion matters because it exposes design pressure rather than a small isolated patch target.
The thread points to PR #4207, 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.
BetaAIbug5Decoration ranges that do not intersect the current text node should not apply there.
The comments add recurring workarounds and edge cases, which makes the pressure clearer than the title alone.
The thread points to Issue #3352, 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.
keep-open
Acknowledge the pain and keep the issue attached to the right cluster.
Direct.
Ready for a red test.
cvlmtgbug, ♥ help7Deleting an inline block selection should remove the inline instead of leaving an undeletable zero-width shell.
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.
horsen689bug, ♥ help1Placeholder rendering should not break Chinese IME input.
The comments mostly collapse this into an existing issue family instead of creating a new one.
The thread points to Issue #3824, 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.
thesunnyimprovement, discussion1Void blocks should optionally support internal caret positions without forcing the current all-or-nothing selection 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.
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.
sfroestlbug, ♥ help1Backspace at the start of a list item should clear list formatting instead of preserving the list-item wrapper.
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.
Likely valid.
Keep it in the corpus; the signal is stronger than the uncertainty.
keep-open
Acknowledge the pain and keep the issue attached to the right cluster.
Indirect.
Ready for a red test.
BetaAIbug, ♥ help0Returning a stable array from Editable.decorate should not trigger an infinite rerender loop.
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.
keep-open
Acknowledge the pain and keep the issue attached to the right cluster.
Direct.
Ready for a red test.
AWildFoxAppeareddiscussion2Decorations produced for one sibling should be able to span adjacent siblings or fail loudly instead of silently misapplying.
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.
lazharichirbug, ♥ help14Paste-html deserialization should preserve links wrapped in formatting tags.
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.
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.
Indirect.
Not a direct test candidate.
thesunnybug, ♥ help1Backspacing over the first character of a second text node should not merge with the previous block.
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.
height option to Editor.liftNodesianstormtaylorfeature, ♥ help0Editor.liftNodes should optionally lift multiple levels in one call.
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.
*.parent helpers to *.aboveianstormtaylorimprovement, debt, ✶ breaking4Ancestor helper naming should be internally consistent and less ambiguous.
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.
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.
timothyarmesbug, ♥ help3Arrow navigation and backspace should treat multi-byte emoji as one visible character.
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.
henrykuzmick⚑ needs context0Setting a new value during a bound event should not break the editor state.
The thread is thin, so the issue body carries most of the signal.
No linked artifacts surfaced in the current thread.
Strong enough.
Poor.
Likely valid.
Keep it in the corpus; the signal is stronger than the uncertainty.
keep-open
Acknowledge the pain and keep the issue attached to the right cluster.
Direct.
Ready for a red test.
ianstormtaylor♥ help, docs2API helper docs should be generated and discoverable without source spelunking.
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.
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.
None.
Not a direct test candidate.
window in React plugin helpersianstormtaylorbug, ♥ help0React helper APIs should not touch window when running in SSR or non-browser environments.
The thread is thin, so the issue body carries most of the signal.
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.
Indirect.
Ready for a red test.