Created attachment 103559 [details] screenshot MS PowerPoint Viewer vs. LibO 4.2.5.2 any slide containing formulas in .pptx attachment 97256 [details] is shown with blue background around each formula which is not shown in MS PowerPoint viewer. see comparative screenshot. AOO has same problem so bug is inherited from OOo similar issue in Writer has been reported here: Bug 79179
Created attachment 103560 [details] screenshot in LibO 4.4 master interestingly the blue background is not present in 4.4.0.0.alpha0+ Build ID: b9dca968c6fd0ab5ca140c65b0e54d153cd34986 TinderBox: Win-x86@42, Branch:master, Time: 2014-07-18_22:51:20 anyway the background is still abnormal with a thin frame around the formula and and OLE icon behind it
the position bug of the formula is Bug 77363 which is still present in 4.2.x but fixed in 4.4.x
(In reply to comment #0) > Created attachment 103559 [details] > screenshot MS PowerPoint Viewer vs. LibO 4.2.5.2 Confirmed with LO 4.2.6.2 and 4.3.0.3 under Ubuntu 12.04 x86. But the position is wrong, perhaps its been reported in another bug.
(In reply to comment #3) > ... > But the position is wrong, perhaps its been reported in another bug. yes, as said before, the position bug is Bug 77363 which is fixed in 4.4.x is it still present in 4.3.x? can you give feedback in that report?
** 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.0.0.5 or later) 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-09-03
(In reply to tommy27 from comment #1) > background is still abnormal with a thin frame around the formula > and and OLE icon behind it issue still present in LibO 4.4.5 and recent 5.1.0 alpha builds
** 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
Still there in 6.0 master builds.
It is fixed in master. Version: 6.0.0.0.alpha0+ Build ID: 616f21db9e50a77b0c02dfb123f871a742f46216 CPU threads: 2; OS: Linux 4.4; UI render: default; VCL: gtk2; Locale: en-US (en_US.UTF-8); Calc: group
As mentioned the bug as described in comment 1 and shown in attachment 103560 [details] is still there (so slightly changed from the original, but still not correct). Assuming it's Windows-only. Version: 6.0.0.0.alpha0+ Build ID: a056bc01bdd0d8bbb5af47a58c2ed86003869c80 CPU threads: 16; OS: Windows 6.1; UI render: default; Locale: hu-HU (hu_HU); Calc: CL
The issue of the icon has been opened in bug 113186 as it wasnt the original bug report filed and is a windows only bug.
I don't fancy unnecessary administration, the remaining issue on Windows is pretty much the same, and this was a perfectly fine bug report to continue tracking that.