Bug 115205 - FILESAVE HTMLEXPORT images are overlapped when spreadsheet exported as HTML
Summary: FILESAVE HTMLEXPORT images are overlapped when spreadsheet exported as HTML
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.6.7.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:html
Depends on:
Blocks: (X)HTML-Export
  Show dependency treegraph
 
Reported: 2018-01-24 15:26 UTC by Marian
Modified: 2023-02-17 03:26 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Spreadsheet with images (951.66 KB, application/vnd.oasis.opendocument.spreadsheet)
2018-01-24 15:26 UTC, Marian
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marian 2018-01-24 15:26:06 UTC
Created attachment 139334 [details]
Spreadsheet with images

The attached spreadsheet contains 3 images.
When performing File -> Save As -> HTML (Calc) format (or File -> Preview in browser) the result has practically only 2 images (the 2 rightmost are overlapped).
Comment 1 Marian 2018-01-24 15:58:22 UTC
Why the status is RESOLVED INVALID? In what version is it resolved? (I have tried with 6.0.0.2)
Comment 2 Marian 2018-01-25 09:29:06 UTC
Tests done with LO 5.1 (from Ubuntu 16.04) and 6.0.
Comment 3 Xisco Faulí 2018-01-26 11:25:27 UTC
You can't confirm your own bugs. Moving it back to UNCONFIRMED until someone
else confirms it.
Comment 4 Buovjaga 2018-02-15 20:18:05 UTC
Repro.

Arch Linux 64-bit
Version: 6.1.0.0.alpha0+
Build ID: 09cb65bb92318bf8edb467fcd7720f072306f379
CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on February 15th 2018

Arch Linux 64-bit
Version 3.6.7.2 (Build ID: e183d5b)
Comment 5 QA Administrators 2019-02-16 03:42:55 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2021-02-16 04:09:53 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2023-02-17 03:26:52 UTC
Dear Marian,

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