Bug 157013

Summary:	Clumsy navigation in document with tracked changes
Product:	LibreOffice	Reporter:	Nadie Nada Nunca <nadie.nada.nunca>
Component:	Writer	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED INSUFFICIENTDATA
Severity:	normal	CC:	miguelangelrv, telesto
Priority:	medium
Version:	7.6.0.2 rc
Hardware:	All
OS:	Windows (All)
Whiteboard:
Crash report or crash signature:		Regression By:
Attachments:	Sample file

Description Nadie Nada Nunca 2023-08-30 13:50:40 UTC

Description:
I'm working on a DOCX file with tracked changes and I've noticed that after accepting comment deletions, navigation of the document stalls or gets quirky. 

Specifically: 

- I have to press the PgDn key several times, not just once, to go down a screen; 

- the "Next" and "Previous" buttons in the Track Changes ribbon do nothing, or appear to do nothing. I'm not sure whether it's a display issue (the document doesn't get refreshed) or they actually do nothing at all.

Steps to Reproduce:
1. Open a DOCX file and enable track changes. 
2. Insert and delete comments. 
3. Press the PgDn key, and use the "Next" and "Previous" buttons in the Review ribbon (tabbed interface).

Actual Results:
It's difficult to move through the document.

Expected Results:
I expected the key and buttons to keep working normally.


Reproducible: Always


User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no

Comment 1 m_a_riosv 2023-08-30 21:38:32 UTC

Please attach a sample file.

Comment 2 Nadie Nada Nunca 2023-09-02 20:33:03 UTC

I just discovered it happens right after deleting a comment and accepting the change, with track changes enabled. It seems to happen in any document (i.e. create a new document, fill it with text, insert a comment, enable tracking changes, delete the comment, accept --> clumsy navigation).

Comment 3 m_a_riosv 2023-09-02 22:50:50 UTC

I can't reproduce.
Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: d88779fc86385dde1215fd28b78a69eacc6b4f97
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo

Comment 4 Nadie Nada Nunca 2023-09-03 12:42:26 UTC

Created attachment 189315 [details]
Sample file

Comment 5 m_a_riosv 2023-09-03 16:18:58 UTC

I can't reproduce also with the sample file.

Comment 6 QA Administrators 2024-03-02 03:15:53 UTC Comment hidden (obsolete)

Dear Nadie Nada Nunca,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
 
Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

Comment 7 QA Administrators 2024-04-02 03:12:22 UTC

Dear Nadie Nada Nunca,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp