Bug 96614 - Not possible to re-anchor the picture with footer involved
Summary: Not possible to re-anchor the picture with footer involved
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.0.4.2 release
Hardware: All All
: low minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Anchor-and-Text-Wrap
  Show dependency treegraph
 
Reported: 2015-12-20 11:01 UTC by szotsaki
Modified: 2024-09-30 03:16 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Test document (470.83 KB, application/vnd.oasis.opendocument.text)
2015-12-20 11:01 UTC, szotsaki
Details

Note You need to log in before you can comment on or make changes to this bug.
Description szotsaki 2015-12-20 11:01:33 UTC
Created attachment 121425 [details]
Test document

1.) Have a document with a footer and a picture with captions. The picture should be partially inside the footer (attached).

Try to move the picture (with the caption frame, of course) a bit upper. If you select the frame border in the footer, as soon as you start dragging the anchor icon it looses focus.
Comment 1 Buovjaga 2015-12-26 15:54:37 UTC
I selected the frame border in the footer and dragged from the anchor and everything went ok.
What loses focus? The anchor? How does it appear?

Win 7 Pro 64-bit, Version: 5.0.4.2 (x64)
Build ID: 2b9802c1994aa0b7dc6079e128979269cf95bc78
Locale: fi-FI (fi_FI)

Version: 5.2.0.0.alpha0+
Build ID: a4764cfa80270f973da5861d0ddc28298bf16f4d
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-12-24_22:45:12
Locale: fi-FI (fi_FI)

Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the information.
Comment 2 szotsaki 2016-01-23 10:53:47 UTC
I use openSUSE Leap 42.1 x64 Linux with KDE 5.

1.) Click on the picture above the footer (anchor is invisible)
2.) Select the frame in the footer -> the anchor appears above the picture where a new line begins
3.) Click on the anchor -> the anchor disappears immediately and the blinking cursor takes over
Comment 3 Buovjaga 2016-01-24 16:53:01 UTC
(In reply to szotsaki from comment #2)
> I use openSUSE Leap 42.1 x64 Linux with KDE 5.
> 
> 1.) Click on the picture above the footer (anchor is invisible)
> 2.) Select the frame in the footer -> the anchor appears above the picture
> where a new line begins
> 3.) Click on the anchor -> the anchor disappears immediately and the
> blinking cursor takes over

Ah, you are correct - I can reproduce.

But the problem does not appear, if you select the frame without selecting the picture first :)

Win 7 Pro 64-bit Version: 5.2.0.0.alpha0+
Build ID: 6b65a0e83c4798f117be61af91dbaebdc85e94b7
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
TinderBox: Win-x86@39, Branch:master, Time: 2016-01-21_03:41:08
Locale: fi-FI (fi_FI)
Comment 4 szotsaki 2016-01-25 20:11:27 UTC
Yes, but without that step (i.e. selecting the picture) you cannot directly select its frame in the footer because the footer catches the "focus" for the first time. Is this "focus-stealing" of the footer intended or is it an other, separate bug?
Comment 5 Buovjaga 2016-01-26 06:57:02 UTC
(In reply to szotsaki from comment #4)
> Yes, but without that step (i.e. selecting the picture) you cannot directly
> select its frame in the footer because the footer catches the "focus" for
> the first time. Is this "focus-stealing" of the footer intended or is it an
> other, separate bug?

That is incorrect, I am able to select the frame directly like I said.
Comment 6 szotsaki 2016-01-27 08:30:50 UTC
Ahh, I see, thank you for the feedback. I created Bug 97387 which deals with this separate problem.
Comment 7 QA Administrators 2017-03-06 14:29:36 UTC Comment hidden (obsolete)
Comment 8 szotsaki 2017-03-08 09:53:24 UTC
Yes, this issue is still there with 5.3.

Version: 5.3.0.3
Build ID.: 30m0(Build:3)
CPU threads: 8; OS version: Linux 4.9; Display: 
default; VCL: kde4; Layout engine:new; Locale settings: hu-HU (hu_HU.UTF-8); Calc: single
Comment 9 szotsaki 2018-03-07 18:12:06 UTC
Reproducible with 
Version: 6.0.2.1
Build ID: f7f06a8f319e4b62f9bc5095aa112a65d2f3ac89
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
Locale: hu-HU (hu_HU); Calc: CL
Comment 10 QA Administrators 2019-03-08 03:40:25 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2022-09-30 03:54:19 UTC Comment hidden (obsolete)
Comment 12 QA Administrators 2024-09-30 03:16:21 UTC
Dear szotsaki,

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