Created attachment 148176 [details]
The attached .docx document is really badly rendered especially the 1st part that is made of different frame/boxes
Created attachment 148177 [details]
How it should look like
Thank you for reporting the bug. I can confirm this in
Build ID: 3c964980da07892a02d5ac721d80558c459532d0
CPU threads: 2; OS: Windows 6.1; UI render: default; VCL: win;
TinderBox: Win-x86@42, Branch:master, Time: 2018-12-12_02:07:45
Locale: en-US (en_US); UI-Language: en-US
Thank you, but "Wrong rendering of docx document" title is a classic example of wrong bug report and confirmation.
Bugzilla is not "document based", like "this document doesn't display nice".
Bugzilla is "issue based", so a single issue must be pointed at, after a search for not being a duplicate.
Durgapriyanka, please define the issue and test previous versions. If not, rather just confirm in comment, without changing to New. Because it's not triaged and therefore there's no use of being confirmed.
I'll change to "DOCX Table shown as text".
Fine looking table "Informations utiles" was there with LO 4.2 and not with LO 4.3.
Looks like a regression to me.
..which all makes it a probable duplicate of Bug 116194.
I guess bibisectRequest would show the same commit.
*** This bug has been marked as a duplicate of bug 116194 ***
(In reply to Timur from comment #3)
> Durgapriyanka, please define the issue and test previous versions. If not,
> rather just confirm in comment, without changing to New. Because it's not
> triaged and therefore there's no use of being confirmed.
Timur: I get your intention, but this is not how we work. We have discussed this topic ("needsTriage") for hours on various occasions and I believe you were present in the Brno meeting in 2016 where it was first brought up. In the last QA meeting we *again* decided to not change anything:
I said: "if we decide not to add anything, we can add some clear guidelines in the wiki on what to search for, if concerned about these matters"
Xisco agreed and added the wiki task to his todo.
I confirm the same commit is responsible for this as bug 116194 (looked with 43max on Linux).