Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Ext JS Premium Member
    Join Date
    Mar 2009
    Posts
    198
    Vote Rating
    1
    rspaeth is on a distinguished road

      0  

    Default unexpected selection with multiple shift clicks

    unexpected selection with multiple shift clicks


    REQUIRED INFORMATIONExt version tested:
    • Ext 4.1
    Browser versions tested against:
    • Chrome 18
    • FF 12
    Description:
    • Most application (mac finder, yahoo mail, ...) add rows to the selection on each shift click selection. Extjs deselects the old rows and only selects the last shift click rows as selected. The text within the grid rows tend to get selected too (as a side effect). Note, shift click going up seems to behave properly, it is when you shift click going down the grid where the problem occurs.
    Steps to reproduce the problem:
    • select 3m Co (the first row)
    • shift select AT&T Inc. (6th row)
    • shift select Citygroup, Inc. (9th row)
    The result that was expected:
    • the first through the 9th row selected and no strange selection remnants (on the text)
    The result that occurs instead:
    • rows 1 - 5 have been deselected
    • on all muli-selection, there is a strange selection remnant over the text (the text gets selected)
    Test Case:
    use the Basic Array Grid sample

  2. #2
    Ext JS Premium Member
    Join Date
    Mar 2009
    Posts
    198
    Vote Rating
    1
    rspaeth is on a distinguished road

      0  

    Default


    it looks like we can keep the old selection by ctrl + shift + click. Is this by design? Having to hold the ctrl to keep the old selections is not standard from my experience. Our users are finding the current results unexpected.

    Code:
    selectWithEvent: function(record, e, keepExisting) {
            var me = this;
    
    
            switch (me.selectionMode) {
                case 'MULTI':
                    if (e.ctrlKey && me.isSelected(record)) {
                        me.doDeselect(record, false);
                    } else if (e.shiftKey && me.lastFocused) {
                        me.selectRange(me.lastFocused, record, e.ctrlKey);
                    } else if (e.ctrlKey) {
                        me.doSelect(record, true, false);
                    } else if (me.isSelected(record) && !e.shiftKey && !e.ctrlKey && me.selected.getCount() > 1) {
                        me.doSelect(record, keepExisting, false);
                    } else {
                        me.doSelect(record, false);
                    }
                    break;
                case 'SIMPLE':
                    if (me.isSelected(record)) {
                        me.doDeselect(record);
                    } else {
                        me.doSelect(record, true);
                    }
                    break;
                case 'SINGLE':
                    // if allowDeselect is on and this record isSelected, deselect it
                    if (me.allowDeselect && me.isSelected(record)) {
                        me.doDeselect(record);
                    // select the record and do NOT maintain existing selections
                    } else {
                        me.doSelect(record, false);
                    }
                    break;
            }
        },

  3. #3
    Sencha User
    Join Date
    Oct 2012
    Posts
    2
    Vote Rating
    0
    JelleJelle is on a distinguished road

      0  

    Default


    I agree with rspaeth. In my opinion this is uncommon multi-select behavior.

    Is there any way to change the behavior to common (Windows Explorer like) shift select behavior?


    Edit:
    For those who are looking for a fix, see this issue: http://www.sencha.com/forum/showthre...tiSelect-issue
    Last edited by JelleJelle; 13 Nov 2012 at 12:44 AM. Reason: Added fix

  4. #4
    Sencha Premium Member
    Join Date
    Sep 2010
    Posts
    98
    Vote Rating
    5
    plleeuwm is on a distinguished road

      0  

    Default


    Is this going to get fixed? This is still broken in the 4.2 beta. Currently it behaves differently than the 3.* version which is a legit bug imo.

Thread Participants: 2

film izle

hd film izle

film sitesi

takipci kazanma sitesi

takipci kazanma sitesi

güzel olan herşey

takipci alma sitesi

komik eğlenceli videolar