Bug 145125 - EDITING Moving a bulleted paragraph upwards/downwards and rejecting all changes leaves paragraph bulleted
Summary: EDITING Moving a bulleted paragraph upwards/downwards and rejecting all chang...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Track-Changes-Lists
  Show dependency treegraph
 
Reported: 2021-10-14 11:14 UTC by Gabor Kelemen (Collabora)
Modified: 2025-11-06 03:12 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot of the original document in Writer after moving a bulleted paragraph down (48.64 KB, image/png)
2021-10-14 11:14 UTC, Gabor Kelemen (Collabora)
Details
Screenshot of the problem in Writer after rejecting all changes (44.50 KB, image/png)
2021-10-14 11:14 UTC, Gabor Kelemen (Collabora)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gabor Kelemen (Collabora) 2021-10-14 11:14:15 UTC
Created attachment 175734 [details]
Screenshot of the original document in Writer after moving a bulleted paragraph down

This is a followup to bug 39721
When a bulleted paragraph is moved upwards/downwards to a non-bulleted paragraph and changes are rejected, the formerly non-bulleted paragraph stays bulleted.

Steps to reproduce:
    1. Open attachment 166793 [details] from bug 39721 (you can reject all existing tracked changes in this, this problem is independent of those)
    2. Move the first  “the quick brown flying fox” paragraph downwards using the Bullets and Numbering toolbar, or the second  “the quick brown flying fox” paragraph upwards.
    3. Reject all changes

Actual results:
The empty paragraph between the four non-empty ones is now bulleted. See attachment 175730 [details] for how it initially looks.

Expected results:
The empty paragraph should not be bulleted after rejecting the changes.

LibreOffice details:
Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: fb3e13cae8ab0915facaf07fe5fca177a4041a9b
CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: default; VCL: win
Locale: en-US (hu_HU); UI: en-US
Calc: threaded
And all the way back to 3.5.0
Comment 1 Gabor Kelemen (Collabora) 2021-10-14 11:14:39 UTC
Created attachment 175735 [details]
Screenshot of the problem in Writer after rejecting all changes
Comment 2 Dieter 2021-11-01 15:07:43 UTC
I confirm it with

Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 273a25c796fca9afa0dfadac57dc3f336831221c
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL
Comment 3 QA Administrators 2023-11-02 03:15:45 UTC Comment hidden (obsolete)
Comment 4 Dieter 2023-11-06 08:15:06 UTC
Still present in

Version: 7.6.2.1 (X86_64) / LibreOffice Community
Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL threaded
Comment 5 QA Administrators 2025-11-06 03:12:49 UTC
Dear Gabor Kelemen (allotropia),

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug