Bug 134947 - Dragging an image up down anchored to character/paragraph changes flow of footnotes
Summary: Dragging an image up down anchored to character/paragraph changes flow of foo...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: All All
: low minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Anchor-and-Text-Wrap
  Show dependency treegraph
 
Reported: 2020-07-19 10:28 UTC by Telesto
Modified: 2023-01-12 03:20 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Screencast (257.70 KB, video/mp4)
2020-07-19 10:29 UTC, Telesto
Details
Example file (238.56 KB, application/vnd.oasis.opendocument.text)
2020-07-19 10:29 UTC, Telesto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-07-19 10:28:52 UTC
Description:
Dragging an image up down anchored to character/paragraph changes flow of footnotes

Steps to Reproduce:
1. Open the attached file
2. Select the blue arrow
3. Press arrow up 5x/ arrow down 5x

Actual Results:
Bulleted list changes/footnote distribution changes

Expected Results:
More stability?


Reproducible: Always


User Profile Reset: No



Additional Info:
Found in
Version: 7.1.0.0.alpha0+ (x64)
Build ID: 52820b52b3bca45e2db527d1cc5f4488b2e0b9d0
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL

and in
4.4.7.2
Comment 1 Telesto 2020-07-19 10:29:20 UTC
Created attachment 163260 [details]
Screencast
Comment 2 Telesto 2020-07-19 10:29:39 UTC
Created attachment 163261 [details]
Example file
Comment 3 Buovjaga 2021-01-11 07:56:03 UTC
Reproduced. In 3.3.0 the shape is not visible.

Arch Linux 64-bit
Version: 7.2.0.0.alpha0+
Build ID: 8ac5b55ada3f408b8a6084a2e1811bbf4ee7ad51
CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: kf5
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 10 January 2021
Comment 4 QA Administrators 2023-01-12 03:20:56 UTC
Dear Telesto,

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