Created attachment 61223 [details] Sample spreadsheet Hello Problem description: Problem occurs if the "source", the selected cell, is actually several merged cells. The "merged format" is not ok after Edit> Fill> Down. The attached screenshot & workbook explain what happens (easy to reproduce, more difficult to explain...) Steps to reproduce: 1. open the attached workbook 2. Select A3:B10 3. Edit> Fill> Down (Ctrl + D) Expected result: 4 merged cells in A3:B10 Actual result: The result after filling is "inconsistent" since it is possible to select one line: A6 for example (G6 in the screenshot) then we should be able to click only A5 or A7 and while the selection behaves as for merged cells (black square on 2 col. x 2 lig. cf. G6 in screenshot). 4. Save, Close, Reload We find consistency: the selection displayed is the actual situation ... which is not good. The cells have been merged 2 columns x 1 line and a merged cell is shifted I4 cf. screenshot Platform : 3.6.0alpha0+ (Build ID: c2003c7) Windows 7 64bits This problem does not appear in this version. Also occurs with older versions. Reproduces (fr-discuss) with LibO 3.5.2 Windows Vista SP2 64 bits Regards Pierre-Yves
Created attachment 61224 [details] Screenshot after Edit Fill Down
Created attachment 61225 [details] Screenshot after reload
Confirmed with: LO 3.6.3.1 Build ID: f8fce0b Windows 7 Professional SP1 64 bit NEW as all issues reproduced.
Update for this bug. Under Ubuntu 10.04 x86_64 running v4.1.3.2 Build ID: 70feb7d99726f064edab4605a8ab840c50ec57a using the example spreadsheet from the description the initial rendering problem shown in the attachment to comment #1 is not visible. Same with new sheets. The problem will a fill commencing a merged cell does however remain: - Selecting the merged cell group A3:B4 and using the click-n-drag fill method results in only cells A5:A10 being filled i.e., the A-B cells are not merged as indicated in the G:H "Actual result" example. - Selecting cells A5:B5 and using the Edit > Fill > Down (CTRL+D) method results in A5:B5 being coloured yellow but unfilled and unable to be subsequently selected i.e., the content from merged cell group A3:B4 is not copied and clicking on cells A5:B5 results in the selection of A3:B4. - Selecting multiple rows (e.g., A5:B5 and A6:B6) and using the Edit > Fill > Down (CTRL+D) method results in no change / action. Seems somewhat related to bug 47778, although that bug deals with the issue of filling *through* a merged cell, rather than using a merge cell as the source.
(In reply to comment #4) > Update for this bug. Under Ubuntu 10.04 x86_64 running v4.1.3.2 Build ID: > 70feb7d99726f064edab4605a8ab840c50ec57a using the example spreadsheet from > the description the initial rendering problem shown in the attachment to > comment #1 is not visible. Same with new sheets. Apologies. This part of my prior comment is not true. This rendering issue *is* still visible when the indicated A3:B10 range is selected. My other comments are accurate, but given this condition, now seem ancillary. Sorry for any confusion.
Hello (In reply to comment #5) > Apologies. This part of my prior comment is not true. This rendering issue > *is* still visible. Yes I confirm that and also still reproducible with Version: 4.2.0.0.alpha0+ Build ID: cc2a405915e82c4b332dd25457f76704dc536d7f TinderBox: Win-x86@39, Branch:master, Time: 2013-10-15_15:51:52 Regards Pierre-Yves
** 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 (4.4.1 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: 2015-04-18
Hi Still reproduced on windows 7/664 & Version: 4.4.3.1 Build ID: b2f347f2ac68821efc00b6f1793cda90af748118 Locale: fr_FR Regards Pierre-Yves
** 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
Hi Still reproduced on windows 7/64 & Version: 5.2.1.2 Build ID: 31dd62db80d4e60af04904455ec9c9219178d620 CPU Threads: 2; OS Version: Windows 6.1; UI Render: default; Locale: fr-FR (fr_FR); Calc: group Regards Pierre-Yves
(In reply to pierre-yves samyn from comment #10) > Still reproduced on windows 7/64 & Version: 5.2.1.2 Of course now the menu is Sheet>Fill Cells>Down Pierre-Yves
** 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
Hi Still reproduced on windows 7/64: Version: 6.0.4.2 (x64) Build ID: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf CPU threads: 2; OS: Windows 6.1; UI render: default; Locale: fr-FR (fr_FR); Calc: group Regards Pierre-Yves
can also reproduce with linux x86_64 Version: 6.2.0.0.alpha0+ Build ID: 5708534b942c1d0ce384f6a8473da6bb569410e7 CPU threads: 8; OS: Linux 4.14; UI render: default; VCL: kde4; Locale: nl-BE (en_US.UTF-8); Calc: group threaded
Looks like a duplicate of Bug 47778 to me. If not, please explain and set back New because it's repro in 6.3+. *** This bug has been marked as a duplicate of bug 47778 ***