Bug 41646 - Contextual spell-checking menu doesn't show accept or reject options for changes
Summary: Contextual spell-checking menu doesn't show accept or reject options for changes
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.3.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-10 04:56 UTC by shtrom
Modified: 2014-07-15 23:43 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description shtrom 2011-10-10 04:56:50 UTC
When using LibO in “Track changes” (Edit/Changes/Record), and one of the
changed word is not recognised as a properly spelled word (i.e. it's
wavey-underlined in red, in addition to showing what the change is with colours
and strike-through, if enabled), right-clicking on the word brings up the
spell-check menu allowing to Add/Ignore/Replace the word, but the change
management functions (Accept/Reject change) are missing, thereby making it
impossible to “manipulate” this particular change from there.

One would expect a consistent interface where *both* spell-checking and
record-management actions are available from the context menu.
Comment 1 Björn Michaelsen 2011-12-23 12:32:55 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 2 Florian Reisinger 2012-08-14 14:01:27 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 3 Florian Reisinger 2012-08-14 14:02:32 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 4 Florian Reisinger 2012-08-14 14:07:08 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 5 Florian Reisinger 2012-08-14 14:09:13 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 6 Olivier Mehani 2012-08-15 04:06:23 UTC
I just checked with 3.5.5.3 (350m1 b:3 from ArchLinux), and the problem seems to be fixed. This bug can indeed be closed.
Comment 7 Olivier Mehani 2012-08-15 04:11:07 UTC
Woops, no, the problem is still there. Sorry.

When a change introduces a spelling error, the contextual menu on the misspelled word of the change only shows spelling options, and the Accept/Reject change option are not present.

The change does appear properly in the Edi/Change/Accept or reject dialog box. The problem is only with the context menu.

Sorry for the false closure.
Comment 8 Florian Reisinger 2012-08-15 11:29:04 UTC
Confirm that
Comment 9 Niklas Johansson 2014-07-15 08:23:50 UTC
From what I can tell this issue does no longer exist in LibreOffice 4.2.5. Both spell-checking and actions related to track changes is available from the context menu, so I'm marking this as resolved - worksforme. Please feel free to reopen this bug if the problem reoccurs.
Comment 10 Olivier Mehani 2014-07-15 23:43:42 UTC
I can confirm that the problem is gone with 4.2.5.2 Arch Linux build-1.