Bug 100288 - First line after inserted picture is not justified
Summary: First line after inserted picture is not justified
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.3.0.4 release
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Writer-Styles-Paragraph
  Show dependency treegraph
 
Reported: 2016-06-09 11:18 UTC by Heinrich Hartl
Modified: 2023-08-18 04:39 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
demo and instructions for reproducing bug (1.00 MB, application/vnd.oasis.opendocument.text)
2016-06-09 11:18 UTC, Heinrich Hartl
Details
screenshot showing unjustified line after image frame (80.27 KB, image/jpeg)
2016-06-09 11:20 UTC, Heinrich Hartl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Heinrich Hartl 2016-06-09 11:18:45 UTC
Created attachment 125568 [details]
demo and instructions for reproducing bug

Version: 5.0.6.3
Build ID: 490fc03b25318460cfc54456516ea2519c11d1aa
Locale: de-DE (de_DE)
Justified alignment spoiled in first line after frame with picture.
If the frame is deleted the line ending in Dorfrathaus is justified. Undo the deletion and the same line is not justified again.
For demo and instruction to reproduce see attached file WriterBug-justification.odt
Comment 1 Heinrich Hartl 2016-06-09 11:20:38 UTC
Created attachment 125569 [details]
screenshot showing unjustified line after image frame
Comment 2 Buovjaga 2016-06-11 14:09:19 UTC
Confirmed.

Arch Linux 64-bit, KDE Plasma 5
Version: 5.3.0.0.alpha0+
Build ID: e1ca24369142af3e721e789bf757be671e1905b7
CPU Threads: 8; OS Version: Linux 4.6; UI Render: default; 
Locale: fi-FI (fi_FI.UTF-8)
Built on June 10th 2016

Ubuntu 16.04 64-bit
Version: 4.3.0.0.alpha1+
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
Comment 3 QA Administrators 2017-09-01 11:20:54 UTC Comment hidden (obsolete)
Comment 4 Heinrich Hartl 2018-02-15 11:07:37 UTC
Comment on attachment 125568 [details]
demo and instructions for reproducing bug

Bug still exists in 
Version: 5.3.7.2 (x64)
Build-ID: 6b8ed514a9f8b44d37a1b96673cbbdd077e24059
CPU-Threads: 4; BS-Version: Windows 6.1; UI-Render: Standard; Layout-Engine: neu; 
Gebietsschema: de-DE (de_DE); Calc: group

MS WIndows 7 , SP  1
Comment 5 QA Administrators 2019-02-16 03:42:30 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2021-02-16 04:09:38 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2023-02-17 03:26:48 UTC
Dear Heinrich Hartl,

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