Created attachment 123316 [details] package with two svg-graphics and a document which links to the graphics Open attached package. It contains a document and two svg graphics, which are linked in the document. Inserting as links guarantees, that always the original graphic is used, when testing in different versions. The graphics contain a group with a gray rectangle and a colored line. This group is scaled by a transform-attribute. In a correct rendering, the line is scaled together with the rectangle. In the wrong rendering, the line is scaled in y-direction, when the rectangle is scaled in x-direction; and when the rectangle is scaled in y-direction the line is not scaled. The rendering is correct in Version: 4.1.6.2 Build-ID: 40ff705089295be5be0aae9b15123f687c05b0a here on Windows 7. The rendering is broken in Version: 4.2.0.0.alpha0+ Build ID: 8624906bc437b242ea0df17801bc77d0f273f32c TinderBox: Win-x86@6, Branch:master, Time: 2013-07-05_04:07:10
TESTING on Ubuntu 14.04 64bit (In reply to Regina Henschel from comment #0) > Open attached package. It contains a document and two svg graphics, > ... > In a correct rendering, the line is scaled together with the rectangle. > > In the wrong rendering, the line is scaled in y-direction, when the > rectangle is scaled in x-direction; and when the rectangle is scaled in > y-direction the line is not scaled. With LO 5.2.0.0.alpha0+ (2016-02-24_23:58:47): I believe that I'm seeing the grey line (incorrectly) scaled in the y-direction when the rectangle is scaled in the x-direction, so Status -> NEW I don't have a 4.1 build here to confirm the regression, but I do see the same problem in LO 4.2.8.2. Regina: Do the SVG docs render correctly in Firefox? (I'm testing with FF 44 here). If so, it's really easy to compare the SVGs in LibreOffice side-by-side with a browser window, and makes the written repro steps much shorter.
The svg-graphics render correctly in browser Seamonkey (version 2.39), which is based on Firefox. I havn't got Firefox to test it there. They render correctly in browser Chrome (version 49.0.2623.75 m) and in the applications Batik (version1.7, http://xmlgraphics.apache.org/batik/) and The Gimp (version 2.8.4). The rendering in Inkscape (version 0.48) is wrong. So there are many ways to see the correct rendering. I have tested it in LO4.1 to make clear, that it is regression.
Created attachment 123349 [details] Diagonal lines which are scaled I'm not sure about the rendering in regard whether the lines have to stay rectangular or should become parallelograms, and in case they need to stay rectangular, what width has to be used. It is handled different in Inkscape and in browsers. I have written to w3.org for that, read https://lists.w3.org/Archives/Public/www-svg/2016Mar/0002.html
The answers from the mailing list www-svg@w3.org are clear: It has to be rendered as parallelograms. And I have come closer to the reason. The rendering is only wrong, if anti-aliasing is enabled.
If such svg-graphic is use in a presentation and anit-aliasing is off, the rendering is nevertheless wrong in presentation mode. And an exported pdf has the wrong shapes.
It is wrong too, if you break the svg-graphic to get draw objects. It seems the problem is deeper. In SVG all kind of lines (line, polyline, polygon) are considered equal to some paths. But if LO breaks them up to Draw objects they are not converted to a filled path but to the Draw "line".
Adding keyword 'preBisect' as this regression was introduced before branch 4.4 and therefore it can't be bibisected as there's no bibisect repository for this branch.
** 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.4.1 or 5.3.6 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-20170929
The problem still exists as described in Version: 6.0.0.0.alpha0+ Build ID: 6c68f38bc28bb55a4f0d53b8f38957516d3935d1 CPU threads: 4; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2017-09-04_22:05:26 Locale: de-DE (de_DE); Calc: group
** 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 error is still in Version: 6.2.0.0.alpha0+ (x64) Build ID: efe119aaa50e9f532b3fac1ef153469c80f24b80 CPU threads: 8; OS: Windows 10.0; UI render: GL; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-09-10_01:36:26 Locale: de-DE (en_US); Calc: CL
Dear Regina Henschel, 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://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 situation is different but still wrong. If Skia is enabled, rendering is wrong, independent from anti-aliasing setting. If Skia is disabled, rendering is correct, independent from anti-aliasing setting. I see the wrong rendering in Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 7c6605bd2c1b27c12c4a492921e537eb4bf5a98e CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: de-DE (en_US); UI: en-US Calc: CL
Dear Regina Henschel, 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
The rendering is still wrong when Skia is enabled and is correct, when Skia is disabled. Tested with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4829a85d0753c93419bd46b1d50bcfa6f0f3f1da CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: de-DE (en_US); UI: en-US Calc: CL threaded
Idem with: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 486ae5db6987411d5e394de94b2b077099d03856 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: en-US Calc: threaded