Third party Firefox spell check error

[zappaDPJ]

Affected version

2.0 RC1

Firefox 56.0.2 (64 bit) (plugins, extensions and dictionaries disabled)
Windows 10 Home 1709

If a word is incorrectly spelt it is briefly highlighted after a space is added but the highlighting is then removed. Incorrectly spelt words are not recognized via a r/h mouse click menu overlay. Deselecting and re-selecting 'Check Spelling' from the same menu will highlight misspellings and enable suggested corrections.

 

[Chris D]

This seems to be a Froala regression or changes which have been made in Firefox. The issue was raised with them and they made some changes, but I agree there seems to be more work to do here.

I've created an issue for them to look at but there will be no ETA for a fix and it's out of our hands, unfortunately.

https://github.com/froala/wysiwyg-editor/issues/2345

 

[Chris D]

I should correct something.

We're still running 2.7.0 here which is still susceptible to the original issue, I think. The best place to try it is in one of the Froala demos as they are running 2.7.1.

https://www.froala.com/wysiwyg-editor/examples/textarea

I think you'll notice an improvement on 2.7.1 except if you use backspace while typing. They've confirmed that in Firefox 56 and above that triggers the problem.

Hopefully they'll get it sorted in time for 2.7.2. We're waiting to upgrade as we noticed some new issues in 2.7.1 so decided to skip that until they were fixed. We've now reported 4 issues, two of them are fixed already. We'll update this thread if we get any updates on the spell check issue.

 

[zappaDPJ]

Thanks for the detailed explanation Chris, it's very much appreciated

 

[DaveM]

The one thing I have noticed here if you move to the next line the previous line will then show the mispelled words and these can be corrected in the normal way.

 

[dash]

Was this ever fixed. Numerous members on my forum are complaining of spell check issues when using firefox. Either everything gets highlighted as an error or it doesn't catch errors / changes from error to non-error.

EDIT: Seems like it has not been fixed, I can replicate it here at Xenforo.com. Also noticed this was raised on Aug 11th.
Five months and no fix?

 

[Ozzy47]

EDIT: Seems like it has not been fixed, I can replicate it here at Xenforo.com. Also noticed this was raised on Aug 11th.
Five months and no fix?

As it is a Froala issue, XenForo has no control over the time it takes for a issue to be sorted.

 

[Chris D]

Also noticed this was raised on Aug 11th.
Five months and no fix?

It was fixed (by the Froala team) and it was working well. Something in Firefox 56 a couple of months ago caused a regression.

 

[dash]

As it is a Froala issue, XenForo has no control over the time it takes for a issue to be sorted.

Xenforo can decide which editor to use. Never had a complaint about the editor in 1.x. Now getting numerous complaints. 5 months to fix a simple bug seems a bit long. If the solution is to wait for the unresponsive Froala, maybe the previous editor can be included and forum owners can decide to use one that works or the one with bugs that don't get fixed.

 

[Ozzy47]

While I would agree that having a choice between editors would be nice, it is just not feasible due to how much integration is needed, it is not like changing a color of the headers.

Blame can also be laid on FireFox for reintroducing the bug in the 56 update.

 

[Chris D]

Can anyone still reproduce this? (cc @AndyB as I know you've had issues with FF and the spell checker before)

I'm using Firefox 59.0b3 and I cannot currently reproduce the issue, so we suspect that FF has fixed the original regression in the meantime. If you can still reproduce it, please let me know which Firefox version you're using (I'm not sure which version they'd have fixed it).

 

[AndyB]

The problem still exists in 58.0.

Would you like me to install Firefox 59.0b3 to test?

 

[Chris D]

Only if you wish to. I assume it must be a beta version though given the b3 suffix.

 

[zappaDPJ]

I noticed very recently the problem appeared to have been fixed. However I'm still on 57.0.4 (although I can see there's an update waiting for a restart).

The problem still exists in 58.0.

I'll restart and report back.

 

[zappaDPJ]

I'm back with 58.0 and I can't reproduce the issue.

Incidentally I can also type 'I'm' without my spellchecker highlighting the 'm'. I don't think it was related but I thought I'd mention it.

 

[Chris D]

If the issue appears to be reproducible in 59 or above, please try and capture a video producing the issue on the Froala WYSIWYG home page.

 

[dash]

58 is the latest firefox non-beta version. problem still exists.

 

[ENF]

My test...



Win10 Pro, Latest Build... FF 58.0, No Addons/Extras. (fresh install of FF for this test)

 

[dash]

Misspell a bunch of words. Then put 2 spaces after it and see what happens. Also misspell a bunch of words, then do a backspace. See what happens.

 

[Jeremy P]

@dash Per Chris's post above, it appears this may be fixed in Firefox 59+. Firefox 58 presumably still has this issue.