Changes between Initial Version and Version 4 of Ticket #10636


Ignore:
Timestamp:
Apr 30, 2010, 2:56:20 AM (10 years ago)
Author:
bill
Comment:

Sorry, I don't think so. It takes the browser a long time to render 250 rows of data, not much we can do about that. If you have that much data you should really be using a FilteringSelect, which will page the data. I don't think we want to put paging into Select though.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #10636

    • Property Status changed from new to closed
    • Property Summary changed from dijit.form.Select drops down after long delay - not much usable to Select: long delay when lots of data
    • Property Milestone changed from tbd to future
    • Property Owner set to Nathan Toone
    • Property Resolution changed from to wontfix
  • Ticket #10636 – Description

    initial v4  
    11Browser: FF 3.5.7, Opera 9.6
    2 After I click select to see option list I must wait 4 seconds for the first time, wfurther dropping-up/down performs much better.
    3 In comparsion, dijit.form.FilteringSelect with the same selcet options doesn't have such "freeze".
     2After I click select to see option list I must wait 4 seconds for the first time, w/further dropping-up/down performs much better.
     3In comparsion, dijit.form.!FilteringSelect with the same selcet options doesn't have such "freeze".
    44
    5 I'm attaching a simple HTML and JSON that contains Select and FilteringSelect, so you can see speed difference.
     5I'm attaching a simple HTML and JSON that contains Select and !FilteringSelect, so you can see speed difference.