Created attachment 71117 [details] step-by-step instructions how to reproduce the problem 1. Create 3-rows, 3-columns table 2. In first column merge second and third row. 3. Mark first column and try to delete a column - deleting not possible menu option Table | Delete | Columns is grayed out. Trying to press DELETE key reports error: "Read-only content cannot be changed. No modifications will be accepted" See attached document with detailed step-by-step instructions.
Confirmed in 4.0. The delete column command is disabled when the column with merged cells is selected entirely. It does work when several cells in that columns are selected.
It works for me if the merged cell is not the last cell in the column. Tested in versions 4.2.7.0.0+, 4.3.3.0.0+ and master built at home under Ubuntu 14.04 x86-64. In the present case with a 3 rows table: click in cell B3 and insert a new row. Now the first column can be deleted. When done delete the fourth row. Best regards. JBF
Retested on LibreOffice v.4.1.3.2 on Windows XP and problem still persists like described in attachment. Like "Jean-Baptiste Faure" described if merged column is in the last row in table and column can't be deleted. But somehow work-around it to add a new dummy row in table at the bottom, then do merge like described in attachment and after delete added dummy row. This is work-around, but I still think this is a bug and should be fixed.
Opps... I tested on Windows 7 now, I don't have Windows XP anymore to test this.
It is possible to delete the column but it depends on where the cursor is placed. 1. New Text Document. 2. Insert → Table with 3 rows and 3 columns. 3. Select cells A2 and A3 and Merge. 4. Place cursor in paragraph outside table. 5. With mouse, move cursor to above first column to get downward point arrow and click to select column. 6. Try to delete column using these methods: a. Right click on column → Column. Result: no option to delete. b. Toolbar → Delete Columns. Result: button is greyed out. c. Menu → Table → Delete → Columns. Result: option greyed out. d. Delete key (this only deletes content not the column). Result: Read-only content... Alternate: 4. Place cursor in A1. 5. With mouse, move cursor to above first column to get downward point arrow and click to select column. 6. Try to delete column using these methods: a. Right click on column → Column → Delete. b. Toolbar → Delete Columns. c. Menu → Table → Delete → Columns. Result: column deleted. Alternate: 4. Place cursor in A2. 5. With mouse, move cursor to above first column to get downward point arrow and click to select column. 6. Try to delete column using these methods: a. Right click on column → Column. Result: no option to delete. b. Toolbar → Delete Columns. Result: button is greyed out. c. Menu → Table → Delete → Columns. Result: option greyed out. d. Delete key (this only deletes content not the column). Result: Read-only content... Alternate: 4. Place cursor in either A1 or A2. 5. Try to delete column using these methods: a. Right click on column → Column → Delete. b. Toolbar → Delete Columns. c. Menu → Table → Delete → Columns. Result: column deleted. Version: 4.4.3.2 Build ID: 88805f81e9fe61362df02b9941de8e38a9b5fd16 The same happens in 4.3.6.2 and 4.2.8.2.
Gordo, thanks for work-arounds. I tested your suggestions in LibreOffice 4.4.2.2 on Windows 7 (currently installed on my system). It works exactly the way you have described. It really looks like it is important where cursor is placed BEFORE selecting the whole column. This is little bit unreasonable to average Joe. Specially because when you mark whole column the cursor appears in A1 cell. What I see now is also that there is not required to mark a column to delete it, but I see somehow logical to do the following: a) make selection b) perform action (delete column, merge column, etc). The same logic is in any text oriented. You know make selection and bold, italic, underline the text. I think many users think like "selection & action" and many users can get into this problem very quickly. In my humble opinion this is a usability bug and it should be fixed. Regards
grofaty, following on from what you said about selection and formatting, I ran some other tests. In the first column, I typed "test" into each cell. I attempted to change the formatting with column arrow selection depending on where the cursor was placed. Only if the cursor was before "test" in the first cell was I able to format the column. Additionally, dragging and selecting of the column allows you to delete or format the column no matter whether you drag from the top or drag from the bottom.
** 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
Not reproducible anymore in LibreOffice 5.2.3.0+ and current master under Ubuntu 16.04 x86-64. Closing as WorksForMe. Please, feel free to reopen if you disagree. Best regards. JBF
Hi, I have retested this problem and in my humble opinion this is still a bug. It looks like it is very important where the cursor is and marking the column is not such an importance. This is not what average Joe would expect. I am reopening this problem. Tested on LibreOffice master on Windows 7. Regards ============== MASTER VERSION ============== Version: 5.3.0.0.alpha1+ Build ID: f965a629fba10ecba7bad938a0c1c9c3db1e510d CPU Threads: 3; OS Version: Windows 6.1; UI Render: default; Layout Engine: new; TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2016-11-23_00:13:10 Locale: sl-SI (sl_SI); Calc: group
The steps in the document and the expected behavior aren't the same. When you select a column and press Delete key (step 6.c), you don't actually delete the column, but the content. I'd say the message is still a bug, but a different one. However, if you mark the column as described in 6.a, and then proceed to the menu where the column could be deleted, it's possible to delete the column (tested in a 6.0 daily build, but also in 3.6.0.4). If that's not what you meant, please clarify your procedure.
@Aron, it is almost 5 years since I have reported this issue, so I hope I remember it correctly. Looking into this problem now it seems to me there are actually even problems, not just only one. I. PROBLEM (originally reported problem in this bug report) First is related to deleting columns there are steps from step 4 to including 6a and 6b steps (so without 6c step): Column with merged cells (in the way merged) can't be deleted. This is main problem of this bug report. II. PROBLEM (delete of content not working for merged table cells) Like I see it now it looks there is one new related problem to merged cells. Do the following: - steps from step 4 to including 6a, - then skip 6b, - do 6c. Expected is that content of cells in column A cells is deleted, but instead error appears: "Write-protected content cannot be changed. No modifications will be accepted." If column B is marked and Delete pressed the content of column is deleted, which is expected. III. PROBLEM (protecting cells in merged table cells) Actually looking into little bit strange error in previous II. problem referring to "write-protected content" it looks to me there is even third problem related to merged cells. - 7a) Move mouse at the top of column B (small down mouse icon appears) and click to mark column B cells. - 7b) Select Table | Protect cells. - 7c) Mark B2 text and press Delete key. The error "Write-protected content..." is displayed, which is expected correct behaving. - 8a) Lets try to do the same thing for column A. Click on top of column A and click on Table menu and you will notice Protect Cells option is grayed out. It looks like it is not possible to protect the content of merged cells selecting whole column. - 9a) But.. it is interesting if cells are marked like clicking at front of A1 (inside cell) and marking down. - 9b) Then Table | Protect Cells is not grayed out and working as expected.
Dear Bug Submitter, 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-20180404
This is New as described: "Column with merged non-first rows can't be deleted if first selected as column". It's minor because column or contents can be if all column cells selected before or no column selected before.
The bug is reproducible in current master build: Version: 6.2.0.0.alpha0+ Build ID: b292a27698e85fd9d60c03613c3b0c67835c4dc1 CPU threads: 4; OS: Mac OS X 10.9.5; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-06-06_23:25:55 Locale: en-US (en.UTF-8); Calc: group threaded
Dear grofaty, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
*** Bug 147498 has been marked as a duplicate of this bug. ***
Dear grofaty, 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
It is now 12-years after I have reported this issue. I have retested my first post and problem is still there. Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: sl-SI (sl_SI); UI: en-US Calc: threaded