Page MenuHomePhabricator

VisualEditor: Using browser native interactive spell-check tool breaks in Firefox
Closed, ResolvedPublic

Description

Quote: Using Firefox 19.0.2 on Windows Vista, editing Relativity Media. Find "subsidairies", right-click, select "subsidiaries". The word appears changed, but the "Save" button is not activated.


Version: unspecified
Severity: major
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=63462
https://bugzilla.wikimedia.org/show_bug.cgi?id=63395
https://bugzilla.wikimedia.org/show_bug.cgi?id=59748

Details

Reference
bz50822

Event Timeline

bzimport raised the priority of this task from to High.Nov 22 2014, 1:49 AM
bzimport set Reference to bz50822.

(In reply to comment #0)

Quote: Using Firefox 19.0.2 on Windows Vista, editing Relativity Media. Find
"subsidairies", right-click, select "subsidiaries". The word appears changed,
but the "Save" button is not activated.

Odd. I get the save dialog activated on making a spelling-correction changes in both Chrome and Firefox, including on that particular word in that particular page. Saved example: https://en.wikipedia.org/w/index.php?title=Relativity_Media&diff=563012676&oldid=559815961

Is the user using a non-standard way of doing the spell-correcting, do you know?

(Assigning to me absent confirmation that this problem is reproducible.)

No i don't know, it's a report from the VE/Feedback page.

  • Bug 52372 has been marked as a duplicate of this bug. ***

Tried to duplicate this with FF 28 on a variety of typos on different pages. Ran into Bug 63395 a lot, but was able to save after using FF autocorrect to alter the typo text. (On a side note, hilariously, FF autocorrect suggests that "autocorrect" should be changed to "autocrat":))

I have issues with this locally as well (Iceweasel/Firefox 24.4.0 with VE 3b3a66763ade397b857e35efe8990ac217e5d54c , in debug mode.

In my case, when I try correct the word, it does change in that spot (fixing the misspelling), and the save button enables. However, the change also appears at the beginning of the document. In this case the required spelling fix was adding an 'r' (occurence. to occurrence), so an 'r' ended up at the beginning of the ContentEditable.

However, in Review Changes (and the actual save), it then drops the original correction, and *only* puts the wrong edit at the beginning.

As far as I can tell, these issues have all been fixed now. However, there's bug 72929 which I've opened for a new issue that's developed in the past few weeks.