Created attachment 163779 [details] Sample slide (PPTX) Office 365 shows shadows for the three rectangular elements in the sample slide, Impress does not. Version: 7.1.0.0.alpha0+ Build ID: <buildversion> CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-07-27_15:39:15 Calc: threaded
Hmm, I "broke" (or fixed) the testcase while minimizing it I'm afraid. Let me retry...
Did you search before? Existing PPT/x bugs with SmartArt, FontArt.
Created attachment 163786 [details] Sample slide (PPTX) This slide shows an effect similar to soft edges, except that it extend inwards. Office 365 shows it, Impress does not. Version: 7.1.0.0.alpha0+ Build ID: <buildversion> CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-07-27_15:39:15 Calc: threaded
(In reply to Timur from comment #2) > Did you search before? Existing PPT/x bugs with SmartArt, FontArt. Yes, I did. Quite a bit, actually.
Created attachment 163787 [details] Comparing 365 (top) with Impress (bottom)
Hello Gerald, For me, MSO 2010 claims both documents are corrupted. Could you please, reattach it again ?
Created attachment 163907 [details] Sample slide (PPTX), take 2 (In reply to Xisco Faulí from comment #6) > For me, MSO 2010 claims both documents are corrupted. Could you please, > reattach it again ? Hi Xisco, I saved that document "163786: Sample slide (PPTX)" from Office 365. To make sure, I just uploaded that attachment to Office 365, verified it still exhibits the same behavior as the screenshot shows, and exported it again from Office 365. This is what I am thusly attaching. It is not binary identical, but looks the same as "163786: Sample slide (PPTX)". Maybe MSO 2010 is too old to process that? (Is there, by the way, a way you have to hide the original description and first comment or two of this report? That was a false start on my end.)
(In reply to Gerald Pfeifer from comment #7) > Maybe MSO 2010 is too old to process that? Ok, that might be the case > > > (Is there, by the way, a way you have to hide the original description and > first > comment or two of this report? That was a false start on my end.) Yes, use the tag 'obsolete'
The PPTX samples open fine in PP 2013. Confirmed with LO 7.1.0.0.alpha0+ (e69fafe1873e4afbe739f21f7a82a069cf7eb5b2), 3.5.0.3 / Windows.
Dear Gerald Pfeifer, 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
Still as originally reported: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e125e6623fa1c0f39d927bb37547ca6d1e299cb1 CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US
Balazs Varga committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/8b7900dc3dfc6e3284442dc106799c44dc8961de tdf#135320 sd fix soft edges are not shown on text frames It will be available in 25.8.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Good in Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ffbe93aa93c0300dd4ff5f4d55dfb33e4c7a394d CPU threads: 16; OS: Linux 6.8; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Bad in (for comparison reason) Version: 24.8.3.2 (X86_64) / LibreOffice Community Build ID: 48a6bac9e7e268aeb4c3483fcf825c94556d9f92 CPU threads: 16; OS: Linux 6.8; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Thanks, Balazs.
Balazs Varga committed a patch related to this issue. It has been pushed to "libreoffice-25-2": https://git.libreoffice.org/core/commit/50131f31f093c32d7f4a3c85fc77637ba0513f2c tdf#135320 sd fix soft edges are not shown on text frames It will be available in 25.2.0.0.beta2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.