Bug 144880

Summary:	Image doesn't jump to next page or stops moving when pressing arrow down, but disappears behind the next page (DOCX only)
Product:	LibreOffice	Reporter:	Telesto <telesto>
Component:	Writer	Assignee:	Not Assigned <libreoffice-bugs>
Status:	NEW ---
Severity:	normal	CC:	dgp-mail, libreoffice
Priority:	medium	Keywords:	bibisected, bisected
Version:	5.0.0.5 release
Hardware:	All
OS:	All
See Also:	https://bugs.documentfoundation.org/show_bug.cgi?id=91260 https://bugs.documentfoundation.org/show_bug.cgi?id=154128
Whiteboard:
Crash report or crash signature:		Regression By:
Bug Depends on:
Bug Blocks:	104468
Attachments:	Example file Bibisect log

Description Telesto 2021-10-02 18:11:25 UTC

Description:
Image doesn't jump to next page or stops moving when pressing arrow down, but disappears behind the next page (DOCX only)

Steps to Reproduce:
1. Open the attached file
2. Select figure 1 frame
3. Press and hold arrow down.. stops at the end of page 1 (OK)
4. File -> Reload
5. File save as DOCX
6. File -> Reload
7. Press and hold arrow down.. image disappears

Actual Results:
Image disappears

Expected Results:
Same model for all file formats? Doesn't happen with ODT or DOC


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: b60b6bfaafa1315e07108dba50f016975b619c59
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: en-US (nl_NL); UI: en-US
Calc: CL

Comment 1 Telesto 2021-10-02 18:11:45 UTC

Created attachment 175466 [details]
Example file

Comment 2 Telesto 2021-10-02 18:18:08 UTC

Also in
Version: 5.2.5.0.0+
Build ID: a4d4fbeb623013f6377b30711ceedb38ea4b49f8
CPU Threads: 4; OS Version: Windows 6.2; UI Render: GL; 
TinderBox: Win-x86@62-merge-TDF, Branch:libreoffice-5-2, Time: 2016-12-24_14:43:55
Locale: nl-NL (nl_NL); Calc: CL

and in
Versie: 5.0.6.3 (x64)
Build ID: 490fc03b25318460cfc54456516ea2519c11d1aa
Locale: nl-NL (nl_NL)

still OK with
Versie: 4.4.7.2 
Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
Locale: nl_NL

Comment 3 Telesto 2021-10-02 18:38:44 UTC

Created attachment 175467 [details]
Bibisect log

Bisected to
commit a4dee94afed9ade6ac50237c8d99a6e49d3bebc1
    Author:     László Németh <laszlo.nemeth@collabora.com>
    AuthorDate: Wed May 13 17:47:36 2015 +0200
    Commit:     László Németh <laszlo.nemeth@collabora.com>
    CommitDate: Wed May 13 18:10:45 2015 +0200
    
        tdf#91260: allow textboxes extending beyond the page bottom
    
        This commit fixes layout problems of DOCX import, but also
        now it's possible to move a textbox beyond the page bottom
        using the arrow keys (this worked only for page-anchored
        shapes in Writer).
    
        Change-Id: Ie83d3202a2248d948348656aa26df20982f9675b

https://cgit.freedesktop.org/libreoffice/core/commit/?id=a4dee94afed9ade6ac50237c8d99a6e49d3bebc1

Comment 4 Telesto 2021-10-02 18:49:09 UTC

@NISZ
A bug or feature topic. The arrow key behavior is apparently an addition to the initial purpose of the commit (or a side-effect presented as desired to prevent additional work).

I personally  against different behavior of same object type only based on the source file format. 

Moving stuff intentionally of page makes no sense to me;  against the wysiwyg principle (in my perception).

Comment 5 Dieter 2021-10-22 07:40:51 UTC

I confirm it with

Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 56883788d0090383dad58552f5a11044ffe64a44
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

Additional information
Couldn't reproduce after saving as docx and reload, but after reopening the document.

Comment 6 QA Administrators 2023-10-23 03:14:20 UTC Comment hidden (obsolete)

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

Comment 7 Dieter 2023-11-02 17:55:41 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