Download it now!
Bug 38433 - UI:Edit > Changes enable navigation toolbar
Summary: UI:Edit > Changes enable navigation toolbar
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.4.1 RC1
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-18 04:22 UTC by pierre-yves samyn
Modified: 2019-01-16 19:59 UTC (History)
1 user (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 pierre-yves samyn 2011-06-18 04:22:56 UTC
Hello

Build Date & Platform: buildid=340m1(Build:101) Windows XP 

Steps to Reproduce:

- Create a new writer document 
- Type "DT" and then F3 to insert  the "Dummy Text" auto-text
- Select Edit> Changes> Record
- Make changes (additions of text, bold, deleting text ...)
- Uncheck Edit> Changes> Record
- Edit> Changes> Accept or Reject (dialog appears)
- Close the dialog 

Expected result: navigation toolbar inactive (no navigation through the navigator)

Actual result: The navigation bar is active and with a functioning "erratic"
(do not move in the history of movements or changes)

Best regards
Comment 1 Rainer Bielefeld Retired 2011-06-26 23:09:59 UTC
Effect is reproducible with Daily Build nearby "LibreOffice 3.4.1RC1 – WIN7  Home Premium  (64bit) English UI [OOO340m1 (Build:101)]", but might be intended?

I did a test with a bigger text and lots or changes proceeding similar to original report. 

When I select several changes one after the other in reporter's step before the last and then close the 'Accept / Reject' dialog, I can use the navigation bar buttons to jump (back) to the changes in the reverse order I selected them in the dialog. And 1 change always will be selected in the 'Accept / Reject' dialog, so it's not unexpected for me that Navigation Bar opens.

I did not see anything unexpected

@pierre-yves samyn
Can you contribute a more precise example for the "erratic" behavior?
Using numbered items in step by step instructions would make references more easy
Comment 2 pierre-yves samyn 2011-06-27 13:00:41 UTC
With your comments I now share your opinion.

My problem was that I did not find documentation or specifications of the new navigation toolbar, which does not facilitate the tests ...

My tests left me thinking that the navigation via the navigator was the only "reliable" way to activate the buttons on the navigation bar.

(In reply to comment #1)
> 1 change always will be selected in the 'Accept / Reject'
> dialog, so it's not unexpected for me that Navigation Bar opens.

This is the point that I missed

As I closed the dialog (as exactly reported) on my list of steps to reproduce (that is to say without selecting anything), I had not noticed that an item was always selected by default

I continue my tests ... thank you
Comment 3 Rainer Bielefeld Retired 2011-06-27 21:44:52 UTC
(In reply to comment #2)

> My problem was that I did not find documentation or specifications of the new
> navigation toolbar

That's a real problem, I also never saw a Help. So may be the observed behavior is intended, but also may be it's not. I will do further investigations.
Comment 4 Björn Michaelsen 2011-12-23 12:29:37 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 5 pierre-yves samyn 2011-12-24 03:10:44 UTC
Same as described by Rainer in his commentary #1 with LOdev 3.5.0beta2+ 
Build ID: 62b9587-7ef74e0-7bf1c81. 

I think we can close this issue...