Description: Font shadow not rendered in presentation mode if highlighted Steps to Reproduce: 1. Open the attached file 2. Press F5 Actual Results: No shadow Expected Results: Shadow Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: c48e4d795e37f23b71d647247590807ab9e52223 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL
Highlighting in presentation mode is introduced with bug 93789
Please attach an example document. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the document.
Dear Telesto, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Created attachment 176088 [details] Test case
Confirmed with test file Arch Linux 64-bit Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 6678b8123c9952c80a637d3a7f4e27511122009e CPU threads: 8; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 27 October 2021
Most people will benefit from this fix (shadows are an integral part of a presentation) Fixing this bug is probably rather easy because a simmilar bug has been recorded using highlighting intstead of shadows (https://bugs.documentfoundation.org/show_bug.cgi?id=93789) Bug would be a major timesaver, the whole functionality is broken without the bug getting fixed There does not seem to be any workaround for this particular feature The issue does reflect poorly on LibreOffice because such a basic feature should be expected to "just work". Thus I'm bumping priority to Major
Not allowed... Could someone with permissions please bump?
(In reply to vg9lphrc from comment #6) > Thus I'm bumping priority to Major You were not trying to bump the priority, but the severity, which means how hard the bug hits the user. See https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg No need to touch priority and severity in this case.
(In reply to Buovjaga from comment #8) > (In reply to vg9lphrc from comment #6) > > Thus I'm bumping priority to Major > > You were not trying to bump the priority, but the severity, which means how > hard the bug hits the user. See > https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart. > jpg > > No need to touch priority and severity in this case. I see. Didn't know about the difference between priority and severity. Thanks for letting me know. Anyways, I've already read the document you've linked and I would still argue that there is sufficient reason to bump the severity, because in my opinion this qualifies as a serious glich. The simmilar issue I've linked (https://bugs.documentfoundation.org/show_bug.cgi?id=93789) has the same priority. Discussion about this always welcome :-)
Dear Telesto, 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