Re: [editing-explainer] How can sites access browser spellchecking? (#36)

@johanneswilm 
> When you say "this" you mean access to spell checking API or a way to define word boundaries?

Primarily the former. But I wonder whether the latter is also such a high priority or not.

> The minimum common ground for spellchecking at this stage seems to be to only let words be within one text node. Otherwise most semi-complex editors have to turn spellchecking of entirely.

I understand your bad example, but I wonder there'd be other bad cases if we limit to one text node. abspos creates a BFC, so it should probably split, but inline-block with margins...I really don't know, there should be both cases. What about letter-spacing:100px? And at least in your example, doesn't putting LF at the element boundary fix the issue?

I think this issue is not very common, has a workaround, hard to do it right, especially when i18n is involved. Important, but need more time to bake, so my opinion is that we can revisit and add in future levels.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing-explainer/issues/36#issuecomment-106320992