This a follow-up bug of bug 116592 based on https://bugs.documentfoundation.org/show_bug.cgi?id=116592#c9 Steps to reproduce: 1. Open attachment 140836 [details] from bug 116592 2. Check the borders in number 9 to 17 See the comparison between LibreOffice 5.4 and LibreOffice 6.1 master -> https://bug-attachments.documentfoundation.org/attachment.cgi?id=140971 Reproduced in Version: 6.1.0.0.alpha0+ Build ID: abf9ec7bef2c341ad9c914fd909dd03b4a784f18 CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group
Initially, the behaviour changed after this commit author Armin Le Grand <Armin.Le.Grand@cib.de> 2017-07-04 16:28:58 +0200 committer Armin Le Grand <Armin.Le.Grand@cib.de> 2017-07-12 21:01:20 +0200 commit f65cbae8947c0462b35c8d3c3d5124e431b100b6 (patch) tree e8248f034f7a97e1716f9477937b55ae31038a76 parent fc55711f01af172eb3a034454405fa941454c781 (diff) borderline: correct problems with border display Bisected with: bibisect-linux64-6.0 Afterwards, it change to its current behaviour after author Armin Le Grand <Armin.Le.Grand@cib.de> 2017-12-01 16:08:10 +0100 committer Armin Le Grand <Armin.Le.Grand@cib.de> 2017-12-07 16:03:53 +0100 commit 1d86f43a10f097aa4925bd48870477001098f5ff (patch) tree 9a77dc6a9d3c4563f5154dfa7cf96823d45fad74 parent f894af6d67510ade1447197833a36151bd778214 (diff) SwFrameBorder: Replaced BorderGeometry creation partially Bisected with: bibisect-linux64-6.1 Adding Cc: to Armin Le Grand
Adding this to [META] borderline regressions [or i'm I missing something?]
Please use a current master for testing. Border corners have been improved. The wrong handling of 3D causes wrong appearance of corners. That affects all border styles, which have in Word a split "tl br" description and example 23. So first the wrong 3D handling has to be repaired. I have shown the borders to Armin on the Hackfest. He said, that example 24 is a real error in drawing the lines and not an error in the import part. I will write a new issue for example 24.
Still incorrect in Version: 6.1.0.0.alpha0+ Build ID: 0a4c1fb68c3619e61099a7c548f550b0d3fd7a53 CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group
Just for the record, this bug is about the borders in figures 9 to 17. The 3D problem is in bug 116592
Can you please add a picture with description what is wrong on the corners? I do not see a problem, which is not caused by wrong 3D handling.
*** Bug 116971 has been marked as a duplicate of this bug. ***
Created attachment 141629 [details] How it looks at 280%
*** Bug 117227 has been marked as a duplicate of this bug. ***
*** Bug 117399 has been marked as a duplicate of this bug. ***
** 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
still repro in Version: 6.3.0.0.alpha0+ (x64) Build ID: 7ca7d61dc25f409e209b3a432c7f07469b17e316 CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-05-03_23:08:41 Locale: ru-RU (ru_RU); UI-Language: en-US Calc: CL
*** Bug 122145 has been marked as a duplicate of this bug. ***
Un-Ccing developer for the moment, old regression & very high workload.
Dear Xisco Faulí, 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