docs/slate-issues/open-issues-dossiers/3948-3881.md
helios1138⚑ needs info, ignored-template4Errors bubbling out of Slate in ways React error boundaries cannot catch is real runtime pain, but this thread never gets to a strong minimal repro.
The comments add workaround ideas, which is useful, but they never produce the kind of crisp failing case needed for trustworthy classification.
Weak.
Poor.
Unclear.
Needs a tighter repro before it should influence architecture.
ask-for-repro
Ask for a tighter reproduction before treating it as real roadmap pressure.
Indirect.
hanfordnone2Slate still overrides or blocks browser text-assistance attributes in Firefox in ways users cannot control.
The comments confirm it and even point at a workaround, which makes this a clean runtime-surface issue, not a mystery browser complaint.
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.
wdfinchnone3History is important enough that the lack of clear docs and examples becomes real maintainer debt.
The thread is small but useful because it shows maintainers already agreed this belongs on the roadmap.
Strong enough
Poor.
Valid.
Keep it in docs/process debt, not architecture pressure.
share-status
Reply with scope/status instead of overpromising.
Indirect.
zengemnone5Finishing Chinese input on Safari still throws the caret back to the start of the node.
The comments mostly orbit workarounds, which is exactly why this should stay in the IME debt pile.
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.
ItsSmiffynone3The placeholder path still interferes with normal mobile text features here by disabling auto-capitalization.
The comments are mostly confirmations, which is enough because the issue itself is already very specific.
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.
kenzobanaagnone0This is an example expectation mismatch around Unsplash URLs, not strong engine pressure.
No thread. It belongs with example/documentation cleanup, not v2 architecture.
Not enough.
Strong.
Invalid.
Do not let support-style threads distort the architecture map.
close-invalid
Reply with scope/status instead of overpromising.
None.
IsaacMSchultznone1This is explicit maintainer-quality pressure: slate-react lacked enough direct tests for the amount of bug surface it carried.
The linked PRs make this one especially useful because it is not just complaining about missing tests; it points at concrete attempts.
Strong enough
Poor.
Valid.
Keep it as maintainer-infrastructure debt.
share-status
Reply with scope/status instead of overpromising.
Indirect.
vijaiendransvbug0Creating a list block on Safari still puts the visual caret in the wrong place even though typing goes into the new list item.
No comment thread needed. The repro is direct and the symptom is crisp.
Strong enough
Poor.
Valid.
Keep it open as runtime-boundary debt.
keep-open
Acknowledge the issue and keep it tied to the right subsystem.
Direct.
evasteingrimsnone3Safari still drops pasted void elements in public examples where Chrome works.
The thread is useful because it narrows the scope and links a probable fix, but also notes remaining inline-element fallout.
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.
lukesmurraynone1Readonly should not mean “dead”. Slate’s current readonly behavior is too close to disabled semantics.
The thread is short but sharp and highlights why readonly matters for interactive viewers, not just frozen text.
Strong enough
Poor.
Valid.
Keep it as runtime semantics pressure, not docs noise.
v2-roadmap
Reply with scope/status instead of overpromising.
Direct.
kWh61none7This looks like old history refocus debt that was probably fixed by a later patch.
The thread matters because it names the likely fixing PR, which is enough to de-weight it without pretending it never happened.
Strong enough
Strong.
Stale candidate.
Do not let old docs churn distort architecture work.
close-stale
Reply with scope/status instead of overpromising.
None.
Cannot resolve a DOM point from Slate point on letter insertebasicnone0Refreshing into an editor that then ignores delete or throws DOM-point errors smells like runtime ownership drift, but the repro is too app-shaped.
No real thread. This needs a smaller reproduction before it deserves more weight.
Weak.
Poor.
Unclear.
Needs a tighter repro before it should influence architecture.
ask-for-repro
Ask for a tighter reproduction before treating it as real roadmap pressure.
Indirect.
greenxiiinone6Using Slate inside an iframe broke because DOM target checks assumed one global Node constructor.
The comments keep it grounded in a real cross-window DOM ownership bug instead of generic iframe handwringing.
Strong enough
Poor.
Valid.
Keep it open as runtime-boundary debt.
keep-open
Acknowledge the issue and keep it tied to the right subsystem.
Direct.
guettlinone1Another stale docs-link issue caused by the examples moving to TypeScript.
The first comment already explains the cause and points to multiple open fixes.
Strong enough
Strong.
Stale candidate.
Do not let old docs churn distort architecture work.
close-stale
Reply with scope/status instead of overpromising.
None.
msenejoanone6Firefox trimming trailing whitespace still breaks cursor behavior in newline-ending text.
The comments are mostly workaround discussion, which is enough to prove the behavior is real but browser-sensitive.
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.
twavvnone2Nested contenteditables still fail because Slate treats them as if it owns the whole subtree.
The comments are useful because they include a concrete hack and make the ownership problem explicit.
Strong enough
Poor.
Valid.
Keep it open as runtime-boundary debt.
keep-open
Acknowledge the issue and keep it tied to the right subsystem.
Direct.
twavvnone3People still needed a stable changelog to understand releases after time away from the project.
The thread is straight process pressure, not product architecture.
Strong enough
Poor.
Valid.
Keep it in docs/process debt, not architecture pressure.
share-status
Reply with scope/status instead of overpromising.
Indirect.
ValentinDuboscqnone0The HTML example still produced a bogus trailing paragraph when copying a fully selected block.
No thread, but the report is precise enough and clearly tied to the example clipboard path.
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.
03xb7none5Slate focus state stays stale when the blur comes from clicking a normal HTML button.
The comments matter because they show this is not just one button placement bug; it is a blur/focus timing problem across normal controls.
Strong enough
Poor.
Valid.
Keep it open as runtime-boundary debt.
keep-open
Acknowledge the issue and keep it tied to the right subsystem.
Direct.
gintautassulskusnone0This is early explicit pressure for a custom surface/layout engine because contenteditable blocks pagination, headers, and richer layout.
No thread, but the body is already architecture material, not a bug report.
Strong enough
None.
Valid.
Keep it as architecture pressure, not near-term bug work.
v2-roadmap
Reply with scope/status instead of overpromising.
Direct.
mbisurgisoshacenone0Removing many nodes or sections at once still feels too awkward through the current transforms surface.
No thread, but it is fair API-shape pressure from a structural editing use case.
Strong enough
Acceptable.
Valid.
Keep it as API-surface pressure, not a bug bucket.
v2-roadmap
Reply with scope/status instead of overpromising.
Direct.
Yidaotusnone2Editor.nodes being selection-relative is easy to miss and causes needless confusion.
The comments are useful because they show the confusion is not isolated to one reader.
Strong enough
Acceptable.
Valid.
Keep it in API/docs confusion, not engine architecture.
share-status
Reply with scope/status instead of overpromising.
Indirect.
mihainstonone0Arrow navigation across video embeds still blows up instead of treating the embed as a skip-over boundary.
No thread needed. This is a straightforward embed-navigation failure.
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.
littlehome-eugenenone2Once the starter text is gone, IME typing in the rich-text example still crashes.
The comments confirm it across Korean and Chinese, which makes it a good anchor issue for the empty-editor IME family.
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.
mitchobriannone1This is the same stale examples-link churn as the nearby README issue.
The only comment already explains the TypeScript rewrite and open fixes, so this should collapse into the same docs bucket.
Strong enough
Strong.
Stale candidate.
Do not let old docs churn distort architecture work.
close-stale
Reply with scope/status instead of overpromising.
None.