In bug 48722, blur had been implemented for shadows (v.7.1), and Draw/Impress have an UI to set it up. But the UI is absent in Writer. This is not only a consistency issue: while one can create such an effect in Draw, copying such an object and pasting in to Writer does not offer the same end effect (see bug 154300: particularly, the pasted object with the blurred shadow would arrive as a Drawing object, and would not allow assigning frame styles).
Using Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded I drew a circle in Draw, added a shadow, gave it a 6pt shadow with a 5pt blur, copied & pasted the circle into Writer, and did not see a way to modify the blur / shadow from writer's property sidebar. While properties for the object are exposed for shadow & blur under Format --> Text Box and Shape --> Shadow, those properties don't match the values that I set in Draw. Instead, they show use shadow checked, color gray 0% (correct), a blur value of 3 points instead of the draw's 5 points, and a distance expressed as inches in a scrollbar rather than as 6 points as I selected in Draw. I can confirm there is no exposure in the UI at all via the sidebar for an object pasted from draw for Shadow / Blur, and that the values found under Format/Text Box and Shape/Shadow for the object I pasted don't match the original values I selected in Draw. So something's definitely amiss.
In Writer, if you insert a shape, right click - Area - Shadow - we have here Blur.
(In reply to BogdanB from comment #2) > In Writer, if you insert a shape, right click - Area - Shadow - we have here > Blur. That's correct, drawing objects have it. But not available for e.g. Paragraphs or Images. Mike, is the same code used for paragraphs and image shadows? In that case, I think this can be marked as a duplicate of bug 148177.
*** Bug 157962 has been marked as a duplicate of this bug. ***
Dear Mike Kaganski, 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