Steps to reproduce: 1) Merge a bunch of cells and select it. 2) Try to drag from the bottom right corner along the row or column. Current result: As marker is pulled along, say, the row, only the topmost cell gets filled appropriately, and the filling continues in single column increments, regardless of the number of columns in the merged cell. Expected result: As the marker is pulled along, say, the row, the same number of cells along the column and row get merged and each newly made merged cell is filled accordingly. At least the cells should be merged accordingly along the perpendicular direction.
Ok I get what you mean. To have the selection behave like you want, click and drag from inside the merged cell a little bit outside of it and then back again. Now the merged cell is selected (blue). Now when you drag from the bottom right handle, it selects logically. I'll set this to NEW and lower severity because a workaround exists. Win 7 64-bit Version: 4.4.0.0.alpha2+ Build ID: b021b5983c62e266b82d9f0c5c6d8d8900553827 TinderBox: Win-x86@39, Branch:master, Time: 2014-11-12_01:10:08
(In reply to Beluga from comment #2) > Ok I get what you mean. > To have the selection behave like you want, click and drag from inside the > merged cell a little bit outside of it and then back again. Now the merged > cell is selected (blue). Now when you drag from the bottom right handle, it > selects logically. The workaround you provided does copy all the cells contained within the merged cell, treating it as an array of cells. However, it does not merge the cells. This result is based on LibreOffice 4.3.3.2 430m0(Build:2) on Ubuntu 14.04.1 LTS.
*** Bug 87529 has been marked as a duplicate of this bug. ***
Herman: please don't change the version field, it tells us the earliest version the bug occurs in.
** 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.0.4 or later) 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
*** Bug 101229 has been marked as a duplicate of this bug. ***
** 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
(In reply to QA Administrators from comment #8) > ** 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 The behavior is still the same in this version: 版本：6.3.2.2 組建 ID：98b30e735bda24bc04ab42594c85f7fd8be07b9c CPU 執行緒：4; OS：Linux 5.2; UI 算繪：預設; VCL: kde5; 語言地區：zh-TW (zh_TW.UTF-8); UI語言：zh-TW Calc: threaded As my attachment shows, if a merged cell was selected fully and dragged to the right column, the copied cell would still become a single cell even if I merged it before dragging.
Created attachment 155100 [details] Screenshot of current behavior It might be an UX issue?
Copying a merged cell into another merged cell should be reasonable expectation. @Heiko, do you think it an UX issue?
I have reproduced the problem with the same version 6.3.3.1 according to instructions both under Linux and under Windows. The behavior was identical and therefore it is not a UX problem. The expected behavior is to copy a merged cell in any direction with the result that at the target also merged cells are created and counted as one cell. This is also the behavior in Excel.
(In reply to karsten.henning from comment #12) > I have reproduced the problem with the same version 6.3.3.1 according to > instructions both under Linux and under Windows. The behavior was identical > and therefore it is not a UX problem. The behavior was identical and therefore it is not an UI problem. What I said UX problem is that, is this behavior intuitive to users? Is this behavior matching what users naturally expect? > The expected behavior is to copy a merged cell in any direction with the > result that at the target also merged cells are created and counted as one > cell. > This is also the behavior in Excel. Right, so I think it is an UX problem. Regardless of what behavior Excel has, it is natural for users to expect this way.
needsUXEval needs ux-advise@
Created attachment 155295 [details] Screencast with Excel 2016 When I expand merged cells in Excel, the target is always merged too. In Franklin's example it would put 2019/11/1 in C+D. Same issue also happens on copy/paste. So perhaps we should change the summary to "Respect merged cells on copy/paste".
Since the issue affects results as shown in the example it's not of low importance.
(In reply to Heiko Tietze from comment #16) > Since the issue affects results as shown in the example it's not of low > importance. Let's set it to Normal then, there is a workaround in comment 1
*** This bug has been marked as a duplicate of bug 43958 ***