- From: Johannes Wilm <notifications@github.com>
- Date: Fri, 02 Apr 2021 10:37:10 -0700
- To: w3c/editing <editing@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 2 April 2021 17:37:23 UTC
@siusin I see a spellchecker API came up on the TPAC 2019 meeting: https://lists.w3.org/Archives/Public/public-editing-tf/2019Oct/0004.html . But as far as I can tell, @BoCupp-Microsoft was going to investigate more as there were some security concerns and it was not clear whether we could move beyond those. I don't think I have seen a draft spec since then. Whether or not JS can get access to the browser internal spell checking dictionaries really depends on whether or not it is possible to overcome the security concerns. The creation of the API itself does not seem that complex. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/editing/issues/294#issuecomment-812633379
Received on Friday, 2 April 2021 17:37:23 UTC