Bug 127276

Summary: Displayed page in a LO Writer document moves to the very end after anchoring a picture to the paragraph
Product: LibreOffice Reporter: Adalbert Hanßen <adalbert.hanssen>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED WORKSFORME    
Severity: minor CC: dgp-mail
Priority: medium    
Version: 6.4.0.0.alpha1+   
Hardware: All   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: the test case mentioned in the bug report

Description Adalbert Hanßen 2019-09-02 09:06:13 UTC 
Created attachment 153816 [details]
the test case mentioned in the bug report

This bug report pertains to LibreOfficeDev Writer
Version: 6.4.0.0.alpha0+
Build ID: 0fb2927a8fe06e6c3255544b8e4c4c9c0f5a67d3
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-08-27_22:50:23
Locale: de-DE (de_DE.UTF-8); UI-Language: en-US
Calc: threaded

In the associated document I have collected the sections of the operating manual of K9-Mail. It was made by copyint the parts of it which were on a bunch of linked html-pages. I want to collect it all to one single file which can be printed. I visited the pages of all components of the website  https://k9mail.github.io/documentation.html and its linked subparts, marekd each pages conue to HTML code to a blank LO Writer document. 

Unfortunately the pictures were distorted and also their placement was not as on the website from where it was copied: e.g. those pictures which were arranged in pairs side by side were arranged vertically.

Also by default all pictures were anchored as characters. However anchoring them to the paragraph seems to give more sense.

I wanted to beautify this by keeping pictures and text side by side where this makes sense: I wanted to put them in 2*1-tables which – together with preventing splitting of rows by page breaks, yields the proper arrangement. Sometimes anchoring pictures to paragraphs lets pictures descend into the footer area or the like, which I don’t like.

Steps to reproduce

1. Open the associated document.
2. Locate the headline “===HERE=== Last step”.
3. Change the anchoring of the picture “you are almost done” from “As Character” to “To Paragraph” (unfortunately they are anchored as character by default rather than to the paragraph and unwrapped, what I would prefer, but that’s another story)

Result: the document is scrolled to its very end. I expect it to remain close to where it was, e.g. at the beginning of the paragraph of the character to which the picture was anchored.

Note: One can almost regain the display position within the document by pressing e.g. the left arrow key (move cursor left by one step). But scrolling the document to its very end is really awesome and it is unnecessary for the processing of the text.

Nota bene: A symptomatic remedy might be to act internally as if a movement of the cursor by one step to the left plus a correcting one to move it one step to the right would be added after the anchoring change. But it would be better to understand why the display window is moved to the very end and do something against it rather than a symptomatic treatment as mentioned. I just mentioned it because it is a circumvention which alleviates work after this bug has pinched you during your work.
Comment 1 Dieter 2019-09-03 15:56:40 UTC 
> (In reply to Adalbert Hanßen from comment #0) 
> Steps to reproduce
> 
> 1. Open the associated document.
> 2. Locate the headline “===HERE=== Last step”.
> 3. Change the anchoring of the picture “you are almost done” from “As
> Character” to “To Paragraph” (unfortunately they are anchored as character
> by default rather than to the paragraph and unwrapped, what I would prefer,
> but that’s another story)

Image is already anchored "To Paragraph" so I couldn't follow the steps with the provided document.
Comment 2 Adalbert Hanßen 2019-09-05 06:36:32 UTC 
(In reply to Dieter Praas from comment #1)
> > (In reply to Adalbert Hanßen from comment #0) 
> > Steps to reproduce
> > 
> > 1. Open the associated document.
> > 2. Locate the headline “===HERE=== Last step”.
> > 3. Change the anchoring of the picture “you are almost done” from “As
> > Character” to “To Paragraph” (unfortunately they are anchored as character
> > by default rather than to the paragraph and unwrapped, what I would prefer,
> > but that’s another story)
> 
> Image is already anchored "To Paragraph" so I couldn't follow the steps with
> the provided document.

Unfortunately I have further processed the whole file and unfortunately I had done one step too much with the one which I supplied as a sample (i.e. the image is already anchored to the paragraph and the bug does not show up if I revert it to being anchored to the character). I'll try to repeat to compile a sample file like the one I wanted to supply. Unfortunately I don't have the time for that today.
Comment 3 Dieter 2019-12-04 09:23:32 UTC 
(In reply to Adalbert Hanßen from comment #2)
> Unfortunately I have further processed the whole file and unfortunately I
> had done one step too much with the one which I supplied as a sample (i.e.
> the image is already anchored to the paragraph and the bug does not show up
> if I revert it to being anchored to the character). I'll try to repeat to
> compile a sample file like the one I wanted to supply. Unfortunately I don't
> have the time for that today.

=> NEEDINFO
Comment 4 QA Administrators 2020-06-03 03:48:41 UTC Comment hidden (obsolete)
Comment 5 Adalbert Hanßen 2020-06-03 19:17:02 UTC 
(In reply to QA Administrators from comment #4)
> Dear Adalbert Hanßen,
> 
> This bug has been in NEEDINFO status with no change for at least
> 6 months. Please provide the requested information as soon as
> possible and mark the bug as UNCONFIRMED. ...

Sorry,

I can't reproduce this bug any more, as told before in comment #2. You may close this bug as INSUFFICIENTDATA now.

I would have marked it this way myself if I had the power to do so. RESOLVED is definitely not the right thing because the cause is still unclear. But it i not relevant any longer given that 6.4.4.2 is out and Version: 7.1 is in alpha0+ state.

Regards

Adalbert Hanßen
Comment 6 QA Administrators 2020-06-04 03:45:03 UTC Comment hidden (obsolete)
Comment 7 Dieter 2020-06-04 06:46:07 UTC 
(In reply to Adalbert Hanßen from comment #5)
> I can't reproduce this bug any more, as told before in comment #2. You may
> close this bug as INSUFFICIENTDATA now.

If it works for you in a newer version, you can close bug as RESOLVED WORKSFORME.