Issue of Combobox when the number of options is 2 or more times of pageSize!

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue of Combobox when the number of options is 2 or more times of pageSize!

gu yu

Hi guys,

I don't know whether this is a bug of combobox :( You can see the example below ...

I use the combobox like this:

<label for="setvaluetest">US State test 1: </label>
<select id="setvaluetest" name="state1" dojoType="dijit.form.ComboBox" class="medium"
     style="width:50%;font-size:15pt;" name="foo.bar1" autoComplete="false"pageSize="3">
     <option>Alabama</option>
     <option>Alaska</option>
     <option>American Samoa</option>
     <option>Arizona</option>
     <option>Arkansas</option>
     <option>Armed Forces Europe</option>
</select>

When i click the arrow button first time i see     

     <option>Alabama</option>
     <option>Alaska</option>
     <option>American Samoa</option>
     <option>More choices</option>

and when i click the "more choices" i see 

     <option>Previous choices</option>
     <option>Arizona</option>
     <option>Arkansas</option>
     <option>Armed Forces Europe</option>
     <option>More choices</option>

As you see, there is only 6 records in the option list , so in the 2nd page there shouldn't be "More choices" option there! When i click the "More choices" there will show nothing but the default value of 2nd page, i think this behavior is not so good... Is this a bug of combobox or can somebody help me to solve this problem? Thank in advance!


_______________________________________________
FAQ: http://dojotoolkit.org/support/faq
Book: http://dojotoolkit.org/docs/book
Forums: http://dojotoolkit.org/forum
[hidden email]
http://dojotoolkit.org/mailman/listinfo/dojo-interest
Reply | Threaded
Open this post in threaded view
|

Re: Issue of Combobox when the number of options is 2 or more times of pageSize!

enez
This post has NOT been accepted by the mailing list yet.
Post is little bit older but issue is reactivated in 1.7.2 and 1.7.3 versions.
I am using filtering select with json rest store.

Can anybody help?