Bug 123006 - Incorrect render: no border around image
Summary: Incorrect render: no border around image
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.4.7.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:doc
Depends on:
Blocks: DOC-Images
  Show dependency treegraph
 
Reported: 2019-01-28 06:48 UTC by Vitaly Zdanevich
Modified: 2025-05-25 03:11 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
doc (218.50 KB, application/msword)
2019-01-28 06:49 UTC, Vitaly Zdanevich
Details
Render in LibreOffice (215.03 KB, image/png)
2019-01-28 06:50 UTC, Vitaly Zdanevich
Details
Render in Google Doc (208.99 KB, image/png)
2019-01-28 06:51 UTC, Vitaly Zdanevich
Details
properties for line (199.16 KB, image/jpeg)
2019-01-28 09:28 UTC, BogdanB
Details
Microsoft Office online render (322.73 KB, image/png)
2019-01-28 16:02 UTC, Vitaly Zdanevich
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vitaly Zdanevich 2019-01-28 06:48:40 UTC
Description:
Please see the screenshots.

Steps to Reproduce:
Open file.

Actual Results:
No borders around my images (I remember that Office on Windows XP showed my borders).

Expected Results:
The same render as in Google Doc.


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Vitaly Zdanevich 2019-01-28 06:49:35 UTC
Created attachment 148697 [details]
doc
Comment 2 Vitaly Zdanevich 2019-01-28 06:50:09 UTC
Created attachment 148698 [details]
Render in LibreOffice
Comment 3 Vitaly Zdanevich 2019-01-28 06:51:04 UTC
Created attachment 148699 [details]
Render in Google Doc

The same as in Microsoft Office - correct.
Comment 4 BogdanB 2019-01-28 09:26:30 UTC
I think the reason is that the color of border is automatic, and on Libre Office is white and is not visibile... See the screenshot if I click on image and then on Line properties.



Confirm this
Version: 6.3.0.0.alpha0+
Build ID: 9bc10964f0673b64e282ad567d08bf7ebba4df65
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-01-27_18:08:30
Locale: ro-RO (ro_RO.UTF-8); UI-Language: en-US
Calc: threaded
Comment 5 BogdanB 2019-01-28 09:28:04 UTC
Created attachment 148702 [details]
properties for line

Line style is not selected and line color is automatic (white???).
Comment 6 BogdanB 2019-01-28 09:29:58 UTC
And line width is seen as zero.
Comment 7 Telesto 2019-01-28 10:16:58 UTC
Also in
Versie: 4.4.7.2 
Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
Locale: nl_NL
Comment 8 Vitaly Zdanevich 2019-01-28 16:02:49 UTC
Created attachment 148714 [details]
Microsoft Office online render
Comment 9 Regina Henschel 2019-01-28 19:56:37 UTC
The "borders" do not belong to the image, but to the text field. The images exist separate and are placed as character in the paragraph of the text field.
Comment 10 BogdanB 2019-01-28 20:40:44 UTC
If I change color, width and style of line I could obtain the original border, like Google Drive. But the question is why the border style change on opening with LO?
Comment 11 Regina Henschel 2019-01-28 22:46:30 UTC
The original border is not a single stroke as rendered by Google, but has a thick and a thin line. Such kind is not available as line style but only as border style. And border styles do not exists for shapes but only for frames. With the current abilities of LibreOffice the same design as in the original doc is not possible.
You can get a frame with border and picture in it as in the original text field, but then you have no grouping. Or you use graphic objects with grouping, but have a 'wrong' border style.

But using no border at all, is surely a bug.

With the new feature "text box in shape" it would even be possible to get a distance between border and image as in original doc and so keep ratio and size at the same time.
Comment 12 QA Administrators 2021-01-29 04:22:55 UTC Comment hidden (obsolete)
Comment 13 BogdanB 2021-01-29 19:59:26 UTC
I retested in Version: 7.2.0.0.alpha0+ / LibreOffice Community
Build ID: f2389a70da606768a39ee599de6a5b24058734aa
CPU threads: 4; OS: Linux 5.8; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded

The same problem. No change.
Comment 14 QA Administrators 2023-01-30 03:21:52 UTC Comment hidden (obsolete, spam)
Comment 15 Justin L 2023-05-25 16:39:28 UTC
repro 7.6+
Comment 16 QA Administrators 2025-05-25 03:11:27 UTC
Dear Vitaly Zdanevich,

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