SCAYT should stop at form fields

[Garry Yao]

The 'scayt_word' marker should split words separated by form field elements, while it's not:

Reproducing Procedures

1. Open the replace by class example page with SCAYT plugin enabled.
2. Insert the text 'wrongword' into editor, waiting for SCAYT marking this word;
3. Move the selection into 'wrong|word', click on 'Insert TextField' button to open dialog and insert a default textfield.
4. Disable and re-enable the SCAYT plugin or enter some char to reload all markers.
   • Expected Result : wrong<input />word should not be considered to have spell error;
   • Actual Result : wrong<input />word is marked as spell error in a whole and if click on the first word to open context menu and click any of the suggestions, the in-middle textfield get lost along with these two words.

[Artur Formella]

DUP of 3562

[Garry Yao]

It's not a DUP of #3562 but issue from inside SCAYT, the default word boundary elements definition from SCAYT is not enough for CKEditor, so we need to expand the range of these elements to include commonly appeared ones like <input> and <hr>.

[WebSpellChecker.net]

The problem is inside SCAYT. We're going to update engine to process <input> the same way as <img> processed, so this problem should be degraded to DUP of #3562.

We are reviewing the ability to make split elements configuration accessible via public API, but this is subject not to current version.

[Garry Yao]

Replying to SpellChecker.net:

The problem is inside SCAYT. We're going to update engine to process <input> the same way as <img> processed, so this problem should be degraded to DUP of #3562.

OK that's great, so please update this ticket when it get fixed in SCAYT engine.

[WebSpellChecker.net]

We have updated the SCAYT core and the problem is resolved as specified above - degraded to DUP of #3562