Bug 135951 - Image anchored to page vanished after changing it to character & pressing Undo (save & file reload bring it back)
Summary: Image anchored to page vanished after changing it to character & pressing Und...
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: Anchor-and-Text-Wrap
  Show dependency treegraph
 
Reported: 2020-08-20 15:37 UTC by Telesto
Modified: 2024-10-24 03:14 UTC (History)
3 users (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 Telesto 2020-08-20 15:37:25 UTC
Description:
Image anchored to page vanished after changing it to character & pressing Undo (save & file reload bring it back)

Steps to Reproduce:
1. Open attachment 164501 [details]
2. Scroll to bottom
3. Select the image change anchor to paragraph/character
4. Press Undo

Actual Results:
Image disappearing in thin air

Expected Results:
Not so


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.1.0.0.alpha0+ (x64)
Build ID: <buildversion>
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL
Comment 1 Telesto 2020-08-20 15:41:02 UTC
Also in
LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4
Comment 2 Telesto 2020-08-20 16:00:17 UTC
@Stuart
Slightly selective but only to point out that "to page" anchoring another vector for flaws :-). And somewhat an illustration of how people use anchors at random (the untouched source file bug 134746). To page anchoring is ideal to prevent images walking away.. But never included in any selection.. 

If you know what you're doing, it's legit. However people tend to use stuff in cases where it probably shouldn't be used. And I personally think LibreOffice software being directed to the masses; so keep it as simple/ straight forward as possible. No sure how to present to features for the "pro/geek". We end up in the area of the initial configuration dialog on first launch (including tabbed/toolbar etc). But could also include the 'autocomplete/markdown etc). An maybe even language setting (need to reconfigure UI language after every reset; not interest in localized versions)
Comment 3 Dieter 2021-03-19 19:52:29 UTC
Telesto, unfortunately nothing has happened with this bug report for more than half year. So I'd like to ask, if it is still valid. Could you please try to reproduce it with the latest version of LibreOffice?
=> NEEDINFO
Comment 4 QA Administrators 2021-09-17 03:51:50 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2021-10-18 03:49:21 UTC Comment hidden (obsolete)
Comment 6 Telesto 2021-10-18 06:04:41 UTC
Still around
Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 93115d2c54d645bcf2f80fde325e3ede39dee4d5
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL
Comment 7 Buovjaga 2022-10-24 16:22:36 UTC
Repro

Arch Linux 64-bit
Version: 7.5.0.0.alpha0+ / LibreOffice Community
Build ID: fe0795c52f783a0cfb9e90aab4ae6fac4eac68df
CPU threads: 8; OS: Linux 6.0; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 24 October 2022
Comment 8 QA Administrators 2024-10-24 03:14:09 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