spell check the entire web page/site
Is it possible to spell check the entire web page using both Hunspell built-in dictionaries and user-defined dictionaries *.dic, already prepared text in Firefox. As it is done in text editors like Libre Office (also uses Hunspell) but for web site, checking the text from top to bottom with errors in a separate window, so spell check is not only in the text input/search field.
Solução escolhida
You can possibly switch the page to design mode (contentEditable) mode via a JavaScript bookmarklet (you may have to click in the page). javascript:void(document.body.contentEditable=document.body.contentEditable=='true'?'false':'true');
You can also get the page content and check that for errors, but that may not work properly with missing line breaks.
javascript:void(prompt(,document.body.textContent))Ler esta resposta 👍 2
Todas as respostas (3)
Solução escolhida
You can possibly switch the page to design mode (contentEditable) mode via a JavaScript bookmarklet (you may have to click in the page). javascript:void(document.body.contentEditable=document.body.contentEditable=='true'?'false':'true');
You can also get the page content and check that for errors, but that may not work properly with missing line breaks.
javascript:void(prompt(,document.body.textContent))
cor-el said
You can possibly switch the page to design mode (contentEditable) mode via a JavaScript bookmarklet (you may have to click in the page). javascript:void(document.body.contentEditable=document.body.contentEditable=='true'?'false':'true'); You can also get the page content and check that for errors, but that may not work properly with missing line breaks. javascript:void(prompt(,document.body.textContent))
Great, thanks for the reply! Perhaps there is a way/script to quickly move the cursor from one error to another in such design mode?
Alterado por nz-b em
contentEditable is what is used by a rich text editor like TinyMC (i.e. you can edit text in this mode), there is no way to jump to an error AFAIK.
You can make it easier to spot errors as you can create ui.SpellCheckerUnderline prefs to specify the appearance of errors (try Style:4 or Style:3 and RelativeSize:300).
ui.SpellCheckerUnderline (#FF0000)(String) ui.SpellCheckerUnderlineStyle (5) [0:none 1:dotted 2:dashed 3:solid 4:double 5:wavy] ui.SpellCheckerUnderlineRelativeSize (100|200)