Bug 136549 - Fileopen DOCX and DOC: Border from frame not proper size and excess shade
Summary: Fileopen DOCX and DOC: Border from frame not proper size and excess shade
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.0.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:doc, filter:docx
Depends on:
Blocks: DOCX-Frames
  Show dependency treegraph
 
Reported: 2020-09-07 14:21 UTC by Timur
Modified: 2022-12-21 03:20 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
MSO saved DOC from sample DOCX (27.50 KB, application/msword)
2020-09-07 14:21 UTC, Timur
Details
DOCX compared MSO LO (123.13 KB, image/png)
2020-09-07 14:22 UTC, Timur
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Timur 2020-09-07 14:21:36 UTC
Created attachment 165235 [details]
MSO saved DOC from sample DOCX

We had filesave bug 131420 (seen in  attachment 165231 [details]), this is fileopen of the same sample MSO-created DOCX attachment 158797 [details].

Per screenshot, there are 2 issues: 
1. borders from frame have wrong width, wider than in MSO
2. shadow border opens wrong.

Similar problem is with DOC, except that shadow border is black from DOC.
Let's keep together so far, easy to open new if a single issue resolved. 
No point in atomizing bug reports where all is said, rather check on change.
Comment 1 Timur 2020-09-07 14:22:34 UTC
Created attachment 165236 [details]
DOCX compared MSO LO
Comment 2 Justin L 2020-12-19 05:08:39 UTC
repro 7.2+
Comment 3 QA Administrators 2022-12-21 03:20:12 UTC
Dear Timur,

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