Announcement

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

    User can not select the first option by pressing "Enter" in a ComboBoxItem with a DropDown grid

    We have tried a lot of SmartGWT builds, starting from April and including the latest v12.0p_2018-07-26/LGPL Development Only (built 2018-07-26).
    The bug can be reproduced in IE, Chrome, Firefox and most importantly it can be reproduced on your current Showcase: https://www.smartclient.com/smartgwt...bobox_category

    Steps to reproduce:
    1. Open the showcase for dropdown grid: https://www.smartclient.com/smartgwt...bobox_category
    2. Click on the Item to expand the dropdown grid.
    3A. Press "Enter" -> Nothing happens. (we expect that the first record should be selected)
    3B. Press "Down Arrow" then "Up Arrow" then "Enter" -> Nothing is selected (we expect that the first record should be selected)
    3C. Press "Down Arrow" and then "Enter" -> Record is selected. (so it works for any other record).
    3D. Click with the mouse on the first record -> Record is selected. (so record clicked handler works for the first record).

    Please note that if the option data source behind the dropdown grid is small (not paged), clicking "Enter" on the first record works just fine.
    We don't understand why selecting the first record does not work and we could not trace back the regression, as it used to work with v11.

    The issue is quite urgent for us, as we are heavily relying on dropdowns in our system. Any help would be appreciated!

    #2
    I'd like to underline that if we set the datasource page size to a value, bigger than number of rows in the datasource, the event starts to work and we are able to select the first record as expected.
    ... so it is probably something connected with the paging functionality...
    Unfortunately, our datasources are too big for this work-around and we are still looking for other ideas.

    Comment


      #3
      Thanks for the notification
      We have made a change to address this issue. This will be fixed in nightly builds going forward (11.1, 12.0 and 12.1 branches)

      Regards
      Isomorphic Software

      Comment


        #4
        Thanks! It looks great!

        Comment

        Working...
        X