docs/slate-issues/open-issues-dossiers/4067-3949.md
jaceyinone6Selecting everything in the editor and then starting IME composition still explodes, which is the same empty-editor composition family in a slightly nastier wrapper.
The comments broaden it beyond one keyboard and show the problem is reproducible across multiple composition paths, not one user setup.
Strong enough
Poor
Valid.
Keep it open as part of the empty-editor IME family.
keep-open
Acknowledge the issue and keep it tied to the right subsystem.
Direct.
pietropnone8Very large text paste/copy regressed hard enough that the editor effectively stops being usable on big payloads.
The comments keep the signal alive over time and also hint that rerender breadth compounds the ingest cost instead of this being a one-off clipboard anecdote.
Strong enough
Poor
Valid.
Keep it tied to the large-document performance family.
share-status
Reply with scope/status instead of overpromising.
Direct.
stan900814⚑ needs info5The images example traps users after image insertion because getting back to plain text entry is too brittle.
The comments drift into workaround discussion, which is a good sign this is more about void-element contract roughness than one typo in the demo.
Strong enough
Acceptable.
Likely valid.
Keep it scoped to example and consumer void behavior, not as a core architecture signal.
share-status
Reply with scope/status instead of overpromising.
Indirect.
OlegDydynone2Undo and redo should not silently disappear just because the active keyboard layout is Cyrillic.
The thread is short, but it is a clean keyboard-layout shortcut report and not just a consumer integration mistake.
Strong enough
Poor
Valid.
Keep it open as keyboard-layout compatibility debt.
keep-open
Acknowledge the issue and keep it tied to the right subsystem.
Indirect.
spudlynone0A build-tooling change stopped transpiling generators far enough for IE11, which is old browser-compat debt, not current v2 signal.
No real thread. This is frozen historical compatibility baggage.
Strong enough
None.
Stale candidate.
Old browser-compat debt should not steer v2.
close-stale
Reply with scope/status instead of overpromising.
None.
szk3600none3Empty-editor Japanese composition still crashes on confirm once the placeholder path is involved.
The comments are useful because they point at placeholder handling and hacky whitespace workarounds instead of random user error.
Strong enough
Poor
Valid.
Keep it open as part of the empty-editor IME family.
keep-open
Acknowledge the issue and keep it tied to the right subsystem.
Direct.
chshouyunone2Using IME inside list items on Safari still sends the caret back to the start of the list item.
The first comment links prior Safari cursor fixes, which makes this a good linked-artifact issue instead of an isolated complaint.
Strong enough
Poor
Valid.
Keep it open as real input-method debt.
keep-open
Acknowledge the issue and keep it tied to the right subsystem.
Direct.
hdsupermannone0This is just a community-group post, not a Slate issue.
No technical thread. It should never count as architecture signal.
Not enough.
Strong.
Invalid.
Do not let support-style threads distort the architecture map.
close-invalid
Reply with scope/status instead of overpromising.
None.
macrozonenone3There is real demand for a presentation-only runtime that does not pull the whole editing stack just to display content.
The comments keep it grounded in bundle-size and readonly rendering concerns instead of turning it into vague framework cosplay.
Strong enough
Acceptable.
Valid.
Keep it as runtime packaging pressure.
v2-roadmap
Reply with scope/status instead of overpromising.
Direct.
gaetan-wapnone5Chrome page translation mutates the DOM in ways that still break Slate editing.
The comments are useful because they point at concrete mitigations like translate="no", which makes this runtime-boundary debt rather than a mystery crash.
Strong enough
Acceptable.
Likely valid.
Keep it open as runtime-boundary debt.
share-status
Acknowledge the issue and keep it tied to the right subsystem.
Direct.
marcusellisonnone1The placeholder path still breaks non-English keyboard composition, here with the German backtick flow.
The lone comment ties it directly to another placeholder/composition issue instead of introducing a new root cause.
Strong enough
Poor
Valid.
Keep it open as part of the empty-editor IME family.
keep-open
Acknowledge the issue and keep it tied to the right subsystem.
Direct.
thesunnynone1If Slate is going to publish @next builds, users need a clear doc story for what that means.
The thread is short but correctly points at release-process clarity, not editor architecture.
Strong enough
Poor.
Valid.
Keep it in docs/process debt, not architecture pressure.
share-status
Reply with scope/status instead of overpromising.
Indirect.
bryanphnone7Backspace around void nodes still has the wrong deletion semantics and forces people into plugin workarounds.
The thread is valuable because it includes an actual workaround plugin, which proves the behavior gap is real and well understood.
Strong enough
Poor.
Valid.
Keep it open as core operation debt.
keep-open
Acknowledge the issue and keep it tied to the right subsystem.
Direct.
nikhilagnone1This was just a broken example link caused by the TS rewrite.
The only reply already explains the fix path. No deeper signal here.
Strong enough
Strong.
Stale candidate.
Do not let old docs churn distort architecture work.
close-stale
Reply with scope/status instead of overpromising.
None.
xurxenone0Using U+FEFF for zero-width rendering is the kind of tiny runtime detail that can turn into weird platform friction later.
No thread, but the report is precise and tied to a concrete implementation seam.
Strong enough
Acceptable.
Valid.
Keep it in API/docs confusion, not engine architecture.
share-status
Reply with scope/status instead of overpromising.
Indirect.
shobhitwalia123none1This is old IE plus third-party suggestions-plugin behavior, not something that should drive current Slate architecture.
The thread never graduates beyond “same here”, which is exactly why it should stay de-weighted.
Strong enough
None.
Stale candidate.
Old browser-compat debt should not steer v2.
close-stale
Reply with scope/status instead of overpromising.
None.
jakednone0The report itself shows plain HTML reproduces the same cursor skip, so this is mostly browser behavior leaking through Slate.
No real thread, and the issue body already does the important work of separating browser behavior from Slate-specific bugs.
Strong enough
Poor.
Likely invalid for the current Slate contract.
This is useful as browser-boundary signal, not as current core bug pressure.
close-invalid
Reply with scope/status instead of overpromising.
Indirect.
wdfinchnone0Word-unit cursor movement breaks at the start of multi-leaf text, which is a clean core operation bug.
No thread needed. The report is already specific enough to test directly.
Strong enough
Poor.
Valid.
Keep it open as core operation debt.
keep-open
Acknowledge the issue and keep it tied to the right subsystem.
Direct.
Mangattnone3Deleting around marked empty text on adjacent lines still overdeletes and eats both sides.
The comments matter because they connect it to normalization behavior and another nearby core issue instead of leaving it as an isolated repro.
Strong enough
Poor.
Valid.
Keep it open as core operation debt.
keep-open
Acknowledge the issue and keep it tied to the right subsystem.
Direct.
Mangattnone2Pressing Enter at the end of a marked range creates the new line but leaves the caret behind.
The comments help because they connect the bug to the same empty-text normalization family as #3965.
Strong enough
Poor.
Valid.
Keep it open as core operation debt.
keep-open
Acknowledge the issue and keep it tied to the right subsystem.
Direct.
kamilmielniknone1This is basically a misunderstanding of Slate selection semantics around non-void empty elements.
The only comment already states the current contract clearly: if you want standalone selection, make it a void node.
Not enough.
Strong.
Invalid.
Do not let support-style threads distort the architecture map.
close-invalid
Reply with scope/status instead of overpromising.
None.
interstates21⚑ needs info, ignored-template0People want more control over history hotkeys and undo behavior than the current surface gives them.
The issue is too bare to be bug work, but it is still fair API pressure on history customization.
Strong enough
Acceptable.
Valid.
Keep it as API-surface pressure, not a bug bucket.
v2-roadmap
Reply with scope/status instead of overpromising.
Direct.
NCPlayznone0The built-in unit set is too rigid for some tokenization rules, and a function-based unit hook is a sane API request.
No thread, but the request is concrete enough to stand as API-surface pressure.
Strong enough
Acceptable.
Valid.
Keep it as API-surface pressure, not a bug bucket.
v2-roadmap
Reply with scope/status instead of overpromising.
Direct.
Mangatt⚑ needs info5Normalization that transforms a node but does not revisit it is exactly the kind of composability trap plugin authors hit.
The comments are useful because they force the reporter to explain the structural parent-enforcement case instead of handwaving “normalization is wrong”.
Strong enough
Poor.
Valid.
Keep it open as normalization/composability debt.
keep-open
Acknowledge the issue and keep it tied to the right subsystem.
Direct.
Mangattnone0Transform calls returning nothing makes follow-up operations brittle once paths move.
No thread, but it is clean API ergonomics pressure around path churn.
Strong enough
Acceptable.
Valid.
Keep it as API-surface pressure, not a bug bucket.
v2-roadmap
Reply with scope/status instead of overpromising.
Direct.