Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    ListGrid expansionComponent jumps unexpectedly

    Tested on version v8.3p_2013-05-14

    Browsers: IE8/Chrome26 on XPsp3; Chrome26 on OSX

    To re-create start with the example:

    http://www.smartclient.com/#expansionDetails

    Modify the code thus:

    Code:
    isc.ListGrid.create({
        ID: "itemList",
        width:500, height:300, 
        alternateRecordStyles:true,
        dataSource: supplyItem,
        autoFetchData: true,
        showFilterEditor:true,
        fields: [
            { name: "itemName",width:400 },
            { name: "SKU",width:400 }
        ],
        canExpandRecords: true,
        expansionMode: "details"
    });
    This will show the filterEditor and make the fields have a width of 400.

    1. Expand the top row of the grid
    2. Note the position of the expansionComponent
    3. Scroll the grid horizontally to the far right
    4. Click in the 'SKU' filter box
    5. Type 45300 and press enter to perform a filter
    6. Note how the expansionComponent has jumped to a new position

    [ATTACH]5647[/ATTACH]

    7. Scroll the grid horizontally back to the far left
    8. The expansionComponent scrolls, too, thereby no longer being in its original position

    [ATTACH]5648[/ATTACH]

    I would expect the expansionComponent, once drawn, to permanently stay in the same position relative to the record, rather than jump around like this, regardless of whether I filter the grid. If I apply a filter that does not include the expanded row, I would expect the expansionComponent to disappear.

    Do you agree?

    #2
    v9.0p_2013-07-20/EVAL Development Only update

    I have just repeated the above test but it appears the behaviour of the expansion row has changed, a new bug has been introduced and it is still possible to re-create the original bug, but the steps have changed slightly.

    THE NEW BUG

    1. Use the same modified code listed in the previous post
    2. Filter the SKU field with '45300'
    3. You should see two matches (SKUs 45300 & 4530000)
    4. Now expand 45300 row (Adding Machine)
    5. Filter the SKU field with '453000'
    6. As expected, only the 4530000 matches
    7. Filter the SKU field with '45300', again
    8. BUG: The 45300 rows appears with its expanded icon expanded, but no expansion component

    [ATTACH]5989[/ATTACH]

    If you click the expansion icon for the first row, you also get a JS error:

    Cannot read property '$ba' of null

    and the OLD BUG

    1. Filter the SKU field with '45300'
    2. Expand the second row of the grid (4530000)
    3. Note the position of the expansionComponent
    4. Scroll the grid horizontally to the far right
    5. Filter the SKU field with '453000'
    6. Note how the expansionComponent has jumped to a new position

    If you then scroll horizontally back the left, you can once again see how the expansion component jumped when the filtering in step 5 was performed.

    [ATTACH]5990[/ATTACH]

    Comment


      #3
      The first bug is fixed for builds dated July 26 and later.

      The other issue in 9.0 is under investigation - we'll update this thread when we have more information

      Comment


        #4
        Both bugs should now be addressed - please retest with a build dated August 9 or later

        Comment


          #5
          More thanks, both bugs gone!

          Comment

          Working...
          X