| Summary: | Some table borders in DOC file render blue and displaced | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Walter Cheuk <wwycheuk> |
| Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | NEW --- | ||
| Severity: | normal | Keywords: | bibisected, bisected, filter:doc |
| Priority: | medium | ||
| Version: | 5.4.0.3 release | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://bugs.documentfoundation.org/show_bug.cgi?id=75260 | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 107701 | ||
| Attachments: |
DOC file contains the table borders
DOCX file contains the table borders screenshot of opening in m$ word screenshot of opening in writer DOC compared in LO 7.1+ and MSo 2016 |
||
|
Description
Walter Cheuk
2017-08-30 05:50:34 UTC
Created attachment 135860 [details]
DOC file contains the table borders
Created attachment 135861 [details]
DOCX file contains the table borders
Created attachment 135862 [details]
screenshot of opening in m$ word
Created attachment 135863 [details]
screenshot of opening in writer
Repro with 6.0+. I'd say it's a duplicate of Bug 75260. But I'm not confident that will be solved anytime soon so let's keep it separate so far. ** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug The border is still not render correctly. Version: 6.2.2.2 (x64) Build ID: 2b840030fec2aae0fd2658d8d4f9548af4e3518d CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; Locale: en-GB (zh_TW); UI-Language: en-US Calc: threaded Created attachment 165022 [details]
DOC compared in LO 7.1+ and MSo 2016
Repro with LO 7.1+ for DOC (as in 6.1, better than in 6.0). No repro for DOCX.
Improvement can be seen in bibisect 6.1, also in Linux. c4f824343a6b0862357bf87d1c18c613dcdd3f31 is the first chnaged commit Author: Jenkins Build User <tdf@pollux.tdf> Date: Thu Jan 11 07:54:43 2018 +0100 source f14b9d30293f180500fc56d81e5390021758e7c1 previous source d11120b95ee27cb4b05db466ed07f7a996dda125 https://gerrit.libreoffice.org/plugins/gitiles/core/+/f14b9d30293f180500fc56d81e5390021758e7c1%5E!/ commit f14b9d30293f180500fc56d81e5390021758e7c1 [log] author Noel Grandin <noel.grandin@collabora.co.uk> Mon Jan 08 17:01:49 2018 +0200 committer Noel Grandin <noel.grandin@collabora.co.uk> Thu Jan 11 07:35:43 2018 +0100 tree a6cd0b853169203cfa0953230e6774e7b1dd81b4 parent d11120b95ee27cb4b05db466ed07f7a996dda125 [diff] convert (a>b?a:b) to std::max(a,b) with something like: git grep -nP '(.*)\s*>\s*(.*)\s*\?\s*\g1\s*:\s*\g2' Change-Id: I60b9a3a2a09162bc0de4c13fdde2c209696e5413 Reviewed-on: https://gerrit.libreoffice.org/47602 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk> Adding Noel to CC. Why am I CC'ed? Is this some kind of regression? Dear Walter Cheuk, 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 (In reply to Noel Grandin from comment #10) > Why am I CC'ed? Is this some kind of regression? No, it was improvement, so informative. Removing you now. Repro 7.5+. (In reply to Timur from comment #12) > No, it was improvement, so informative. Removing you now. Ah! Good to know, no problem, thanks Timur |