Description: Impress: Delete table row disabled with cursor in row (after applying blue table style) Steps to Reproduce: 1. Open Impress 2. Insert a 2x3 table 3. Apply the blue table style 4. Place cursor in bottom row 5. Click delete row button in toolbar 6. Place cursor again inside table (de-focus is known bug). Notice the table row delete button being disabled Actual Results: Disabled Expected Results: Enabled Reproducible: Always User Profile Reset: No Additional Info: Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: d7f734db2c078ced3ce08ad58cd816a79abe3bcf CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL
Found in 7.1 7.0 6.1 Fine in Version: 6.0.6.0.0+ Build ID: c30963b8b4bbbe42a24b97aafa161eff9d7ccdd4 CPU threads: 4; OS: Windows 6.3; UI render: default; Locale: nl-NL (nl_NL); Calc: CL
Found in Version: 7.1.3.2 / LibreOffice Community Build ID: 10(Build:2) CPU threads: 8; OS: Linux 5.11; UI render: GL; VCL: kf5 Locale: en-US (en_US.UTF-8); UI: en-US Ubuntu package version: 1:7.1.3-0ubuntu0.21.04.1 Calc: threaded If you deselect the table again and select it once again, the delete table row is enabled again.
What I found is that step 3 (applying blue table style, or any) isn't needed. However, after step 5 the delete row/column buttons tend to get disabled, if not, when moving to the table cell, hover over the border, then those two buttons will definitely get disabled, which is a prerequisite for the bug. This is actually a regression in 6.0, from the following commit, bibisected using repo bibisect-linux-64-6.0. https://cgit.freedesktop.org/libreoffice/core/commit/?id=e142027a26634f51b0fc0903076f980d4a37496a author Tamás Zolnai <tamas.zolnai@collabora.com> 2017-10-27 18:48:51 +0200 committer Tamás Zolnai <tamas.zolnai@collabora.com> 2017-10-27 23:23:57 +0200 tdf#110002: Sidebar shows 2 as font height for some specific... ... Impress tables cells
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