Created attachment 132315 [details] SelectBug.odt (see "Steps to Reproduce") In a Writer table: It is (seemingly) impossible to select all cells in a set of contiguous rows if they contain more than one vertically-merged pair of cells. I don't know exactly what conditions make some cells un-selectable (in combination with others), but the attached demo document shows an example. STEPS TO REPRODUCE: 1. Load the attached SelectBug.odt 2. Try to select the bottom two rows of the table, including the vertically-spanned cells (everything except the header row). 3. (In real life, the next step would be to copy the selected rows and paste them many times to create new tables. But you can't get this far.) RESULTS: Impossible to select all cells in the bottom two rows of the table. If you select a vertically-spanned cell on either end and try to sweep horizontally with the mouse to pick up others, then some previously-selected cells un-select themselves. The widespread convention of Control-click to add/subtract from a selection set does not work either (I don't think LO intended to follow this convention, but probably it should for consistency with Microsoft Windows [though I hate to say it]) EXPECTED RESULTS: There should be a way to select any contiguous set of cells, or at least all cells in a contiguous set of rows. If feasible, the "Control-Click to add/subtract from selection" paradigm would help users who are familiar with selection methods in other software.
In the example go to the cell in column A, row 2. Press Ctrl+Shift+End. If the cell has content, then the content will be selected. In that case press Ctrl+Shift+End again. No all but the first row should be selected. The shortcut key Ctrl+End moves the cursor to the bottom right cell and combined with the shift key, will select the cells. But it does not solve the general problem, that it is not possible to select a range, in which the bottom right cell is a hidden cell. This problem exists only in Writer tables not in Calc.
** 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 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 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: 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
Created attachment 147802 [details] Example ODT with repro and no-repro tables Repro 6.3+ for attached ODT. Note read-only cells in status bar. I attach another example ODT with repro and no-repro tables.
wrong bug
Dear Jim Avera, 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
> it is not possible to select a range, in which the bottom right cell is a > hidden cell. This problem exists only in Writer tables not in Calc. Still a problem in 7.2alpha (latest master). I can select most combinations in Timur's example, but in the "SelectBug.odt" example it is not possible to copy the bottom two rows into another table (because the bottom two rows can not be entirely selected). Version: 7.2.0.0.alpha0+ Build ID: ed54542e7237c9e519b75464af55094e578aefdc CPU threads: 12; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-12-24_00:53:01 Calc: threaded
Dear Jim Avera, 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
Bug still there. This time I built lo myself from master. Timur's "Example ODT with repro and no-repro tables" is excellent. Just load it and try to select all cells in each table. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 39ffd246450cbf5feb68d7f5ab058b92a951066a CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Looks like a duplicate of bug 43848. *** This bug has been marked as a duplicate of bug 43848 ***