Created attachment 149018 [details] Screen short - left PowerPoint 2003 (with setting for the second/right color), right LO Impress 6.1.3.2 Test case: attachment 130940 [details] [of bug 105792] PPTX file (PowerPoint 2007) with gradient-filled rectangle In PowerPoint the rectangle shows up as horizontal gradient BLUE to TRANSPARENT. In Impress as BLUE to REDISHGRAY to TRANSPARENT In the file, the settings are: Left: BLUE, 0% transparency Right: ORANGE, 100% transparency PowerPoint seemingly does: - calculate the first color (BLUE) - calculate the second color (TRANSPARENT/no color) - interpolate between them Impress seemingly does: - interpolate between the colors (BLUE->ORANGE) - apply to it the interpolation of the transparency
Thank you for reporting the bug. I can reproduce the bug Version: 6.3.0.0.alpha0+ Build ID: b6b28931435e44aca92b8c0e1659f701e3ed1a87 CPU threads: 2; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-01-30_06:57:04 Locale: en-US (en_US); UI-Language: en-US Calc: threaded
Tested with multiple versions down to 3.3.0. Always been wrong.
Created attachment 169004 [details] The example file opened in PP 2013 and Impress 7.2 Looks quite similar to how more modern PP renders it (which is quite different from 2003), with the "redishgray" middle part in: Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 2081eac430ac69619149e44b453a2d7dda41fc83 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: CL
Dear Tobias Burnus, 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
Created attachment 186716 [details] The example file in MSO 2010 and 2013 Looks like the rendering of this example has changed with MSO 2013. Before only the transparency was considered, since 2013 the color and the transparency are both considered. LO is compatible with the latter. I think it's a NAB at this point, considering even newer MSO renders it differently.
(In reply to Gabor Kelemen (allotropia) from comment #5) > Created attachment 186716 [details] > The example file in MSO 2010 and 2013 > > Looks like the rendering of this example has changed with MSO 2013. > Before only the transparency was considered, since 2013 the color and the > transparency are both considered. LO is compatible with the latter. > > I think it's a NAB at this point, considering even newer MSO renders it > differently. I confirm office.com renders it like MSO 2013.