Opened 12 years ago

Closed 12 years ago

Last modified 9 years ago

#6196 closed defect (fixed)

FilteringSelect user-supplied query is ignored on change

Reported by: John Locke Owned by: Douglas Hays
Priority: high Milestone: 1.1
Component: Dijit - Form Version: 1.1b1
Keywords: Cc: haysmark
Blocked By: Blocking:

Description (last modified by John Locke)

This is different than an earlier reported bug about FilteringSelect? queries.

When you supply a data query to a FilteringSelect? to limit a different attribute than the named item, the query is used for all lookup requests except when the value of the field is actually selected.

Example: <input type="text" dojoType="dijit.form.FilteringSelect?" id="srchaccounts" class="comboBoxL"

searchAttr="name" keyfield="id" value="" store="AccountStore?" name="account" query="{source:'customer'}" promptMessage="Choose an account" size="14"/>

... In this example, AccountStore? is a dojox.data.QueryReadStore? that sends all requests to the server, which returns a name, id, and source attribute for each item.

Firebug reports these URLs: on open

on keypress

... etc. But then when I select an option and tab out of the field, it requests this: on select

Note that the "source" get parameter is no longer requested. Haven't yet tracked this down to the FilteringSelect? or the QueryReadStore?, but I suspect the former.

Tested on FF2/Linux, on Dojo 1.1.0b3.

Change History (6)

comment:1 Changed 12 years ago by John Locke

Description: modified (diff)

comment:2 Changed 12 years ago by John Locke

This appears to be related to QueryReadStore? clearing the other parts of the query (start, count).

comment:3 Changed 12 years ago by wolfram

I dont see where the source parameter can cause the problem, and iirc QueryReadStore? doesnt know about it anyway. So the problem might be in some other place. Did you look at http://archive.dojotoolkit.org/nightly/dojotoolkit/dojox/data/tests/QueryReadStore.html may be the examples in there help.

If that doesnt help please provide a bit more source code to understand the problem a bit better. I currently didnt really get the problem. (but that might also be my fault :-) )

comment:4 Changed 12 years ago by Douglas Hays

Cc: haysmark added
Milestone: 1.1
Owner: set to Douglas Hays
severity: normalmajor

Method setDisplayedValue() in FilteringSelect? was not using the user supplied query.

comment:5 Changed 12 years ago by Douglas Hays

Resolution: fixed
Status: newclosed

(In [13067]) Fixes #6196. Mixin the user-supplied query.

comment:6 Changed 9 years ago by bill

Component: DijitDijit - Form
Note: See TracTickets for help on using tickets.