jam
30 April 2026 20:00
1
Based on microsoft response to the issue, it seems like we need to use Web Workers (or another way) to solve the performance problem.
opened 12:11AM - 06 Jan 19 UTC
closed 06:42PM - 10 Jan 19 UTC
**monaco-editor version:** 0.15.6
**Browser:** chrome
**OS:** ubuntu 17
**S… teps or JS usage snippet reproducing the issue:**
monaco.editor.create(document.getElementById("container"), {
value: "sfaewfwef",
language: "markdown"
});
judging from the image used for the github repo, monaco used to support spellchecking provided by the web browser.
But the latest version doesn't.
I'm trying to build a markdown editor, spellcheck is a useful feature. Anyway this can be enabled? this should be an editor option.
Someone suggested his own spell check lib, but I don’t think that’s the right way to handle it.
opened 09:35AM - 23 May 20 UTC
feature-request
editor-core
If the DIVs and SPANs is explicitly set to `contenteditable="true"` (instead of … inherited) you get a red squiggly under badly spelled words in the monaco editor. The context menu hides the suggestions - but if that is removed/disabled - the word can be replaced; but even without the replace - the spell lint would be very nice.
Such a "feature" would be VERY nice for .TXT, .MD etc... especially with Chromes "new" enhanced (opt. in) spell checker that also "checks the language".
jam
30 April 2026 20:32
2
What if we moved the dictionaries and computations to the backend, and let the frontend render markers based on the incoming data? Is this achievable in our infrastructure?
It is achievable, but I feel doing this on the front-end side makes more sense. Otherwise we’d expose an endpoint that would be a free spellchecker for anyone
So I think workers are the way to go
