Bug 120043 - Dragging a column results in selection being increased rather than column moving
Summary: Dragging a column results in selection being increased rather than column moving
Status: RESOLVED DUPLICATE of bug 46930
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.1.0.3 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-21 22:40 UTC by AaronPeterson
Modified: 2018-10-23 13:15 UTC (History)
2 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 AaronPeterson 2018-09-21 22:40:01 UTC
Description:
I know people have horribe computers that missinterpret finger movements as drag events... but still I expect a mouse press and hold on a column header then movement to reposition the column... essentially dragging the column... instead the selection increases... and I would expect to do that by holding down control or shift while clicking on column headers.

behavior just doesn't conform to expectations.

Steps to Reproduce:
1.click on column header (c)
2.(release)
3.see it is selected
4..drag column header for c to between a and b...


Actual Results:
selection increases

Expected Results:
column should be moved to be between a and b.


Reproducible: Always


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: yes
Version: 6.1.0.3 (x64)
Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1
CPU threads: 8; OS: Windows 10.0; UI render: default; 
Locale: en-US (en_US); Calc: group threaded
Comment 1 Aron Budea 2018-09-27 00:19:32 UTC
The column can be dragged by clicking into and dragging the column content, not the header.
Comment 2 Buovjaga 2018-10-23 13:15:51 UTC

*** This bug has been marked as a duplicate of bug 46930 ***