Description: During the following actions (as far as I have found out) a shape, which is set to background) appears over the text/table as I am typing: - Merging cells in a table (no frame used) - Selecting text that is within the boundaries of the shape - Moving up and down between lines/ cells Scrolling down/up until the shape is out of sight and returning to the shape brings the text back (or partially when not scrolling far enough) and the shape back to the background. This happens both when I've set the shape (anchored to paragraph) in the footer and the main text. Steps to Reproduce: See description Actual Results: The shape pop-up over the text. Typing is still possible but happens behind the shape so you can't see what I've just typed Expected Results: The shape should stay in the background Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Versie: 6.4.6.2 Build ID: 1:6.4.6-0ubuntu0.20.04.1 CPU-threads: 4; Besturingssysteem: Linux 5.4; UI-render: standaard; VCL: gtk3; Locale: nl-NL (nl_NL.UTF-8); UI-taal: nl-NL Calc: threaded $ glxinfo | grep OpenGL OpenGL vendor string: X.Org OpenGL renderer string: AMD VERDE (DRM 2.50.0, 5.4.0-58-generic, LLVM 10.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 20.0.8 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.5 (Compatibility Profile) Mesa 20.0.8 OpenGL shading language version string: 4.50 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.0.8 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions:
Created attachment 168639 [details] A screenshot showing the problem
Thank you for reporting the bug. I can not reproduce the bug in Version: 7.2.0.0.alpha0+ (x64) Build ID: f2171af6ce3516598d9f8bac8294025a21a5b1a2 CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL Version: 7.0.4.2 (x64) Build ID: dcf040e67528d9187c66b2379df5ea4407429775 CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL
Dear Ayush Jain, Thank you for taking the effort for trying to reproduce the bug. I see that you're using Windows 10 instead of Mint 20.0. After updating my system to 20.1 the bug remains. Regards,
I cannot reproduce the bug in LibreOfficeDev 7.2 on mac OS
Could not reproduce the bug in LibreOfficeDev 7.2 on macOS
Cannot reproduce with Version: 7.1.7.2 / LibreOffice Community Build ID: 10(Build:2) CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: cs-CZ Ubuntu package version: 1:7.1.7-0ubuntu0.21.04.1 Calc: threaded and Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: ba7db98cca3d8516697c94ef0d6af27db9e1655e CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded Please attach test file. Thank you.
Created attachment 176873 [details] A video showing the issue My comment won't help to solve the issue but I'm experimenting it on a Writer document that I can't share unfortunately; A shape is placed in a title before a table and when I click on the table, the shape loses its "background" attribute and comes back in the foreground. So I have to move the shape back to the foreground and then to the background to get back the original layout. Unfortunately this bug is random so I'm unable to reproduce it with confidence. But I made a video anyway (added in attachment). My impression is that the LibreOffice rendering engine, when it updates the table display, clear the background attribute of the closest shape. It remains to be determined what makes this behavior unreliable.
Please note that, so far, I can't reproduce this issue on LibreOffice version 7.3.0.0, but the bug being random, I can't confirm that the lastest version is not affected too.