Bug 78433 - DOCX import, the wrong border is used in first column due unhandled insideV
Summary: DOCX import, the wrong border is used in first column due unhandled insideV
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.2.4.1 rc
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: compatibilityModeDefault
Keywords: filter:docx
Depends on:
Blocks: DOCX-Tables
  Show dependency treegraph
 
Reported: 2014-05-08 12:55 UTC by Sven-Jacobi
Modified: 2024-04-01 03:12 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
bugdoc (8.00 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2014-05-08 12:55 UTC, Sven-Jacobi
Details
Screenshot of the example document in Word and Writer (73.19 KB, image/png)
2020-03-30 18:16 UTC, NISZ LibreOffice Team
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sven-Jacobi 2014-05-08 12:55:04 UTC
Created attachment 98679 [details]
bugdoc

If the attached docx is loaded with LibreOffice then there are some borders in the first column that are not displayed as if loaded with Word.

The table is using conditional styles, it seems that the insideV border attribute of the first column is not applied properly.
Comment 1 Jorendc 2014-05-16 20:06:06 UTC
Reproducible, tested using Windows 8.1 with LibreOffice Version: 4.3.0.0.alpha1+
Build ID: 48eccfb812284f43ba24c3be3903537ce954944d TinderBox: Win-x86@39, Branch:master, Time: 2014-05-16_00:35:19
Comment 2 QA Administrators 2015-06-08 14:42:31 UTC Comment hidden (obsolete)
Comment 3 Buovjaga 2015-08-02 10:10:51 UTC
Confirmed.

Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+
Build ID: 902255645328efde34ddf62227c8278e8dd61ff0
TinderBox: Win-x86@39, Branch:master, Time: 2015-07-30_03:52:07
Locale: en-US (fi_FI)
Comment 4 QA Administrators 2016-09-20 10:21:28 UTC Comment hidden (obsolete)
Comment 5 Xisco Faulí 2017-10-03 15:29:49 UTC
Still reproducible in

Version: 6.0.0.0.alpha0+
Build ID: 34e8fd7e99489e9f50a512b07c6f3923b358b4d3
CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group
Comment 6 QA Administrators 2018-10-04 02:55:41 UTC Comment hidden (obsolete)
Comment 7 NISZ LibreOffice Team 2020-03-30 18:16:22 UTC
Created attachment 159167 [details]
Screenshot of the example document in Word and Writer

Still happens in:

Version: 7.0.0.0.alpha0+ (x64)
Build ID: bc898e2c2784e36ad4d4cdf6d962e39069d2c82d
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; 
Locale: hu-HU (hu_HU); UI-Language: en-US
Calc: CL
Comment 8 NISZ LibreOffice Team 2020-03-30 18:17:42 UTC Comment hidden (obsolete)
Comment 9 Justin L 2020-06-03 08:36:48 UTC
There were a lot of problems with the partial InsideV/H implementation, so a lot of that was cleaned out in LO 6.2.  See bug 82177.
Comment 10 Justin L 2022-04-01 09:33:23 UTC
repro 7.4+
Comment 11 QA Administrators 2024-04-01 03:12:08 UTC
Dear Sven-Jacobi,

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