Bug Hunting Session
Bug 42261 - display of selected cells incorrect after inserting row/column above/left of selection
Summary: display of selected cells incorrect after inserting row/column above/left of ...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.4.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 59377 (view as bug list)
Depends on:
Blocks: Cell-Selection
  Show dependency treegraph
 
Reported: 2011-10-26 00:50 UTC by Winfried Donkers
Modified: 2019-07-17 02:49 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Winfried Donkers 2011-10-26 00:50:09 UTC
-select cell(s) and copy to clipboard
-go to any row above selected cell(s) and insert row
-the highlighted area (blinking dashed border) now is one row too high, i.e. no longer shows the selected cell(s)
(the clipboard still has the correct data)

Same principle when inserting columns left of selected cell(s).

Probleem occurs with Windows and with Linux
Comment 1 Winfried Donkers 2011-10-26 01:26:50 UTC
Also occurs with version 3.5 (sources of 24 October 2011)
Comment 2 Winfried Donkers 2012-01-02 23:01:42 UTC
The bug also occurs when dragging selected rows/columns and using the shortcut
key Alt to move them.
version 3.4.4 on Windows XP, as well as master on openSUSE 12.1 

The behaviour seems related to bug 37987 and bug 44383.
Comment 3 A (Andy) 2013-01-02 19:12:46 UTC
not reproducible with LO 3.6.4.3. (Win7 Home, 64bit)

Maybe this was in the meantime already solved?  If yes, then this bug can be marked as resolved.
Comment 4 Winfried Donkers 2013-01-03 06:46:39 UTC
(In reply to comment #3)
> not reproducible with LO 3.6.4.3. (Win7 Home, 64bit)
> 
> Maybe this was in the meantime already solved?  If yes, then this bug can be
> marked as resolved.

Still Reproducible with version 3.6.4.3 (WinXP).

@A: Could you realyy not reproduce the problem?
1. open a new calc document
2. enter "test" in cell B4
3. goto cell B4 and copy (Ctrl C)
4. goto cell B3; cell B4 is marked with a dashed line to show the copied cell
5. insert new row
6. the cell with "test" is now in B5, as expected; the dashed line is still around B4, which is not as expected; one would expect it to be around cell B5.
Comment 5 A (Andy) 2013-02-23 16:47:56 UTC
Thank you very much for your further clarification and sorry for the delayed reply.  I have tested it once more and the issue with the dashed line is now for me reproducible with LO 4.0.0.3 (Win7 Home, 64bit).  But if I choose INSERT then the word "test" will be inserted correctly.
Comment 6 Winfried Donkers 2013-02-25 06:58:15 UTC
(In reply to comment #5)
> But if I choose INSERT then the word "test" will be inserted correctly.

Thank you for your feed back.
Yes, everything functions as expected, but the view is confusing/incorrect.
If you paste a second time, "test" is pasted (functionally correct), but the user sees the dashed lines around B4 which _do_ _not_ indicate the content of the clipboard.
That (indicating the wrong clipboard content) is the incorrect 'behaviour'.

It is not a critical bug, but one which is at least confusing, and to me annoying.
Comment 7 A (Andy) 2015-02-13 11:45:22 UTC
Reproducible with LO 4.4.0.3, Win 8.1
Comment 8 QA Administrators 2016-02-21 08:37:05 UTC Comment hidden (obsolete)
Comment 9 Winfried Donkers (retired) 2016-02-22 08:56:27 UTC
Reproducible with version 5.0.4 (Windows7) and on 5.2 (master, openSUSE 13.1).
Comment 10 QA Administrators 2017-03-06 15:43:49 UTC Comment hidden (obsolete)
Comment 11 Winfried Donkers (retired) 2017-03-07 11:10:08 UTC
Reproducible with version 5.2.5 (Windows7) and on 5.4 (master, openSUSE Tumbleweed).
Comment 12 Thomas Lendo 2017-03-25 10:57:39 UTC
*** Bug 59377 has been marked as a duplicate of this bug. ***
Comment 13 QA Administrators 2018-07-16 02:42:06 UTC Comment hidden (obsolete)
Comment 14 Winfried Donkers (retired) 2018-07-16 05:47:21 UTC
Reproducible with version 6.0.5.2 (Windows10) (no Linux machine available atm).
Comment 15 QA Administrators 2019-07-17 02:49:00 UTC
Dear Winfried Donkers,

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