Bug 65777

Summary:	EDITING: Want buttons for moving to previous/next (tracked) change
Product:	LibreOffice	Reporter:	Eyal Rozenberg <eyalroz1>
Component:	Writer	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED DUPLICATE
Severity:	enhancement	CC:	cno
Priority:	medium
Version:	unspecified
Hardware:	All
OS:	All
See Also:	https://bugs.freedesktop.org/show_bug.cgi?id=65765
Whiteboard:
Crash report or crash signature:		Regression By:

Description Eyal Rozenberg 2013-06-15 06:27:21 UTC

(Filed following a suggestion here: http://is.gd/BC8Vb9 )

When working on a document with tracked changes, I would like to be able to move the cursor (and the viewed part of the document) to the closest change before or after the current cursor position. 

This can be done in MS-Word, but the reviewing toolbar doesn't seem to have these buttons.

Note also that in MS-Word, pressing Next or Previous (tracked change) selects the entire change, making it easier to accept or reject it right after you get there.

Comment 1 Cor Nouws 2013-06-15 08:33:27 UTC

Hi Eyal,
thanks for the report.
Pls have a look at bug 64992.

There is some explanantion first. And an enhancement request that is related to your ideas. Maybe that is a reason for a bit different/more specific formulating of your suggestion?
Regards - Cor

Comment 2 Eyal Rozenberg 2013-06-15 09:22:45 UTC

I think both enhancement requests are valid independently of each other. Bug 64992 is about an automatic move to the next change when you accept or reject something. This bug is about the ability to trigger this move manually, without

I will add this, however: The functionality does exist as a menu item, at

Edit > Changes > Next Change

I just want it to be available as a toolbar button (which seems not to be the case).

Comment 3 Jorendc 2013-07-04 21:56:13 UTC

(In reply to comment #2)
This bug is about the ability to trigger this move
> manually, without
>
> Edit > Changes > Next Change
> 
> I just want it to be available as a toolbar button (which seems not to be
> the case).

Then this looks more a duplicate of Bug 47677 to me :). (also a bit related is bug 32699).

Kind regards,
Joren

*** This bug has been marked as a duplicate of bug 47677 ***