Bug 131285 - FILEOPEN: DOCX: Incorrect font colour in table
Summary: FILEOPEN: DOCX: Incorrect font colour in table
Status: RESOLVED DUPLICATE of bug 131258
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, filter:docx, regression
Depends on:
Blocks: DOCX-Tables
  Show dependency treegraph
 
Reported: 2020-03-11 14:00 UTC by Xisco Faulí
Modified: 2020-03-12 07:56 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Comparison MSO 2010 and LibreOffice 7.0 master (108.00 KB, image/png)
2020-03-11 14:00 UTC, Xisco Faulí
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Xisco Faulí 2020-03-11 14:00:24 UTC
Created attachment 158609 [details]
Comparison MSO 2010 and LibreOffice 7.0 master

Steps to reproduce:
1. Open attachment 84711 [details] from bug 68607

-> Table's header is black. See screenshot

Reproduced in

Version: 7.0.0.0.alpha0+
Build ID: dde0cf9eafed91c88d9999a294ea32fe0e8aa4bc
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded

[Bug found by office-interoperability-tools]
Comment 1 Xisco Faulí 2020-03-11 14:01:17 UTC
Regression introduced by:

https://cgit.freedesktop.org/libreoffice/core/commit/?id=4d5c0eaf3e0d3d3bcd9e691fffee19b75f3d6631

author	László Németh <nemeth@numbertext.org>	2020-02-17 14:34:11 +0100
committer	László Németh <nemeth@numbertext.org>	2020-02-19 16:46:18 +0100
commit 4d5c0eaf3e0d3d3bcd9e691fffee19b75f3d6631 (patch)
tree 6ed8e4a013884c28db01b9175dfc933141b7c395
parent faa2e7b7227b6b87379e7e136ea9ab63f37c3fc4 (diff)
tdf#118812 DOCX import: fix table style preference – part 2

Bisected with: bibisect-linux64-6.5

Adding Cc: to László Németh
Comment 2 László Németh 2020-03-12 07:56:35 UTC
The same issue, as in the case of empty tables, with the same solution.

*** This bug has been marked as a duplicate of bug 131258 ***