Problem description: Fill down (Ctrl-D) does not work if selected visible and hidden cells. Steps to reproduce: 1. cells A1=Header, A2=1, A3=empty, A4=1, A5=1 2. enable filter by Header=not empty 3. change value A2 to "2" 4. select A2:A5 5. click Ctrl-D and nothing happen Current behavior: Fill down (Ctrl-D) does not work if selected visible and hidden cells. Expected behavior: Fill down (Ctrl-D) must fill down all visible selected cells and skip all hidden (even selected) cells. Platform (if different from the browser): Ubuntu 11.10 Browser: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0
Menu also is greyed out, so shortcut can't work, expected behavior for now. But reporter's expected behavior is correct, and I am pretty sure that this already has been reported somewhere among all those "hidden cells handling" Bugs. @Vlad: Can you please help to check whether this problem has already been reported?
Still [Reproducible] with parallel Dev-installation of "Version 4.1.0.0.alpha0+ (Build ID: 049ce78144650d92eb6bd73292868f73d37c901) TinderBox: Win-x86@6, Branch:master, Pull Time: 2013-03-29_23:59:42" ENGLISH UI / German Locale on German WIN7 Home Premium (64bit) with LODev/4 Masters User Profile Already [Reproducible] with Server Installation of "LibreOffice 3.3.3 English UI/ German Locale [OOO330m19 (Build:301) tag libreoffice-3.3.3.1] on German WIN7 Home Premium (64bit) I can't find a DUP, so NEW. Additional info: Same with AOOo 3.4.0, so probably inherited from OOo Same with Symphony and still with AOOo 4 Master Softmaker FreeOffice: Fill is active, but overwrites hidden cells, even worse! (Old) Gnumeric: Copa/past overwrites hidden cells, I did not find a "Fill" function @Spreadsheet Team Please change Status to ASSIGNED and add yourself to "Assigned To" if you accept this Bug or forward the Bug if it's not your turf (and remove others in team from CC).
Probably a fall-out of http://wiki.openoffice.org/wiki/Calc/Drafts/Issue_33851 behavior when filtered rows are selected, maybe the change for bug 35345 (2c2ea10d446b32d24f6268116093969b454f47b8) is also related, see also https://issues.apache.org/ooo/show_bug.cgi?id=89232 Note that filtered is different from hidden, on purpose, and material in the wiki and bug comments confuse these a lot. Please stick to the term filtered in this case, thanks. Taking.
Oops, noticing that this is still assigned to me but I never got around to work on it. Releasing for those who want to tackle it.
** 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.6 or 5.2.3 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-20170103
Still present in 5.2.6.2 and 5.3.2.2 on Fedora 25. Copying to selected visible cells works as expected, but it warns about overwriting cells which are not empty, even if there are only empty selected visible cells.
** 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
There are definitely still some bugs here. 1. Following the reproduction steps, an autofilter with Header=not empty does not do anything. 2. if I put A3 = 0 (instead of empty as in step 1) and then filter so that it only shows 1, the filter works and following steps 3, 4, 5 reproduces the same behavior as in the original bug report Version: 6.2.0.3 Build ID: 6.2.0-3 CPU threads: 8; OS: Linux 4.20; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
Dear Vlad, 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
Still present. Version: 7.1.2.2 / LibreOffice Community Build ID: 8a45595d069ef5570103caea1b71cc9d82b2aae4 CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: cs-CZ Flatpak Calc: threaded
Dear Vlad, 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 157077 has been marked as a duplicate of this bug. ***
*** Bug 152665 has been marked as a duplicate of this bug. ***
Created attachment 205245 [details] screenshot of calc app showing selection and menu with greyed out fill down option Hey team, Unfortunately this bug is still present. I was using a slightly older version of libre office, and found the bug, then found this post about it. I then updated Libre office to the latest version, reopened the file in that, and tried to do the fill down again. No luck. Version: 25.8.4.2 (X86_64) / LibreOffice Community Build ID: 290daaa01b999472f0c7a3890eb6a550fd74c6df CPU threads: 16; OS: Linux 6.14; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-GB Flatpak Calc: threaded
Andreas Heinisch committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/1a9ed757489725d106c28c902c24fc827806c902 tdf#48274 - Enable fill operations including filtered rows It will be available in 26.8.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
There seem to be two different cases involved here: 1) When rows are hidden by filter: - Pasting into a filtered range may fail with "Cannot insert into multiple selection". - However, if only visible cells are explicitly selected before pasting, the operation works correctly and only affects visible rows. 2) When rows are hidden manually: - Pasting still affects hidden rows, which is inconsistent with the filtered case. This suggests that Calc already supports correct behavior (visible-only paste), but only when the target range is explicitly defined as visible cells. It would be useful to clarify whether the patch addresses: - only the "multiple selection" error, or - also the inconsistency between filtered and manually hidden rows.
Andreas Heinisch committed a patch related to this issue. It has been pushed to "libreoffice-26-2": https://git.libreoffice.org/core/commit/9280e2a62b1ab469e22848629301b7fdf4d744bd tdf#48274 - Enable fill operations including filtered rows It will be available in 26.2.4. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.