Bug 324665 - shift+click multi-select doesn't work properly across columns in open dialog
Summary: shift+click multi-select doesn't work properly across columns in open dialog
Status: RESOLVED DUPLICATE of bug 182239
Alias: None
Product: kfile
Classification: Applications
Component: general (show other bugs)
Version: 4.11.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-08 15:29 UTC by Mark K Cowan
Modified: 2013-09-08 17:52 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Video demonstrating what happens when I attempt to range-select (3.84 MB, video/mp4)
2013-09-08 15:29 UTC, Mark K Cowan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mark K Cowan 2013-09-08 15:29:04 UTC
I click on a file at the bottom of a column in an open dialog.  I then shift+click on a file in the next column.  I would expect this to select all files inclusively between* the two that I clicked on.
*"between" in the sort order (in this case, by name), not by position on the screen as a click+drag select would do

Instead, a seemingly random selection of files are selected.  The selection is deterministic in that if I repeat the process, attempting to select the same range of files as before, then the same buggy selection is produced.

Reproducible: Always

Steps to Reproduce:
1. Launch an open dialog which permits multi-select (e.g. Kate->open)
2. click on a file in one column
3. shift+click on a file in another column
4. files outside the desired range are selected
Actual Results:  
Files outside the desired range are selected

Expected Results:  
Files inside the desired range, and only those files should be selected

Potential security issue if someone doesn't realise that they're attaching the wrong files to an email.
Comment 1 Mark K Cowan 2013-09-08 15:29:50 UTC
Created attachment 82220 [details]
Video demonstrating what happens when I attempt to range-select
Comment 2 Christoph Feck 2013-09-08 17:52:32 UTC

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