Apache OpenOffice (AOO) Bugzilla – Issue 111203
Spell check on/off does not update before clicking in text fields (each separately)
Last modified: 2010-05-03 08:34:34 UTC
Please open the attached odp. It opens with enabled spell checker. - Switch off the spell checker (button in the toolbar) The word is is still underlined red. - Click into the word. Now the red underlining has vanished. - Switch on the spell checker The word is not underlined. - Click into the word. Now the word is underlined. Found on OOo 3.2.0 Linux build. Draw is affected by this bug, too! (Text fields have to be double clicked there.) Notice that the user has to click in each text field separately to update them! This is extreme annoying on big and complex documents.
Created attachment 69149 [details] issue.odp
Reproducible with "Ooo-Dev 3.3 multilingual version German UI WIN XP: [DEV300m77 (Build 9496)]" for "issue.odp" and my own sample documens! Worked fine with "2.4.1 Multilingual version German UI WIN XP: [680m17(Build9310)]". No longer reproducible with "Ooo-Dev 3.3 multilingual version German UI WIN XP: [DEV300m77 (Build 9496)]", it seems that the problem has been fixed! DUP of Issue 26821 @norbert2: Can you please watch whether the problem reappears in 3.3 or later and leave a comment in Issue 26821? *** This issue has been marked as a duplicate of 26821 ***
Closed.
@ rainerbielefeld: I think you made a mistake. First you write it wouldn't work with DEV300m77. Then you write that it is fixed in DEV300m77. I think you mean that it is fixed in DEV300m77, right?
.
Sorry, I have removed status duplicate by mistake. I cannot set duplicate again.
May be it would help not to modify status for each comment you want to leave? ;-) Yes, it seems that I inserted a wrong Version for one of my comments. Problem I still reproducible with "Ooo-Dev 3.2.1 multilingual version English UI WIN XP: [OOO320m16 (Build 9497)]", so it seems that it still exists in the 3.2 code line and has vanished in 3.3. code line. And please: if you have new information concerning the BUG, please comment in Issue 26821! *** This issue has been marked as a duplicate of 26821 ***