Created attachment 116863 [details] screenshot as summarized, compared to the rest of the braces, brackets, lines, the scalable ones are too wide (by about 100%)
I'm not seeing such a dramatic thickness difference myself. I do notice that in the other presets in the dropdown, there are lines with bigger thickness. So I'll set to NEW anyways. Are you using Windows? Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ (x64) Build ID: 3a6ec53eeeec71312f5ea890689f9c2ee79c2aac TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2015-07-01_02:24:40 Locale: fi-FI (fi_FI)
** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Dear Dominik, 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
Hello, This comment is going to be post on the bugs: bug 32362 bug 133081 bug 92373 bug 127483 All those bugs seem to be related. In my humble opinion as begginer programmer they seem to be related with a disfunction with OpenGL in windows. Tested on linux (LO 6.4), no problem. Tested with beta 7 on windows, no problem (does not use OpenGL any more). So the bug happened to correct by itself. So I suggest marking as duplicated bug 32362 bug 133081 bug 127483 and close them all.
(In reply to dante19031999 from comment #4) > In my humble opinion as begginer programmer they seem to be related with a > disfunction with OpenGL in windows. Can you install a master build from https://dev-builds.libreoffice.org/daily/master/current.html Win-x86_64@tb77-TDF and then in Tools - Options - LibreOffice - View - Use Skia for all rendering (restart LibO)? Do you still see the problem with Skia-based rendering? OpenGL will be going away.
Done. Can't really find something wrong on the brackets or it's thickness (only bug 32362). The linux graphics leave something to be desired, but since I've been tweaking screen zoom and resolution can't put the blame on LO. However linux version does not use Skia, I think it's VCL. I upload some screenshots.
Created attachment 162132 [details] Screenshots
Done. Can't really find something wrong on the brackets or it's thickness (only bug 32362).