Bug 146265 - Wrong refresh of changes to image if sidebar is open
Summary: Wrong refresh of changes to image if sidebar is open
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.4.0.0 alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Writer-Images
  Show dependency treegraph
 
Reported: 2021-12-16 13:43 UTC by Regina Henschel
Modified: 2023-12-17 03:12 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
screencast (338.99 KB, video/mp4)
2021-12-16 13:43 UTC, Regina Henschel
Details
screencast of frame moving without picture (1.02 MB, video/mp4)
2021-12-16 13:52 UTC, Stéphane Guillou (stragu)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Regina Henschel 2021-12-16 13:43:05 UTC
Created attachment 176966 [details]
screencast

Insert an image into a text document and enable border and set border color red.
Unmark image and mark again. Set border blue in the toolbar.
Error: The image is shifted inside the frame.
Scroll the image out of view and into view. Now the position is correct.
See attached video.

I see the problem in Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 2dc2188c40282e85ecf9eb62321320251357f760
CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: default; VCL: win
Locale: de-DE (en_US); UI: en-US
Calc: threaded
Comment 1 Stéphane Guillou (stragu) 2021-12-16 13:52:26 UTC
Created attachment 176967 [details]
screencast of frame moving without picture

I could reproduce a very similar behaviour. I was even able to move the "frame" without the picture moving with it.

Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: 06ac18e6302d666c363740644a7976e8c22d1113
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded
Comment 2 QA Administrators 2023-12-17 03:12:49 UTC
Dear Regina Henschel,

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