Opened 6 years ago
Last modified 4 years ago
#18206 new defect
[patch][cla?] FilteringSelect: disable auto-complete if the query starts with a wildcard
Reported by: | jsonn | Owned by: | |
---|---|---|---|
Priority: | undecided | Milestone: | 1.15 |
Component: | Dijit - Form | Version: | 1.10.0 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
Using a FilteringSelect? with a query starting with a wildcard has a bad UI experience right now. If the first match contains the input, but it doesn't start with it, the user input is silently replaced. Requiring turning off autoComplete is not optimal.
Attachments (1)
Change History (4)
Changed 6 years ago by
Attachment: | autocomplete-prefix.diff added |
---|
comment:1 Changed 6 years ago by
Component: | General → Dijit - Form |
---|---|
Summary: | [FilteringSelect] Disable auto-complete if the query starts with a wildcard → FilteringSelect: disable auto-complete if the query starts with a wildcard |
comment:2 Changed 5 years ago by
Milestone: | tbd → 1.12 |
---|---|
Summary: | FilteringSelect: disable auto-complete if the query starts with a wildcard → [patch][cla?] FilteringSelect: disable auto-complete if the query starts with a wildcard |
I think jsonn has a CLA iirc, but need to verify. Bill, are you able to review this patch?
comment:3 Changed 4 years ago by
Milestone: | 1.13 → 1.15 |
---|
Ticket planning... move current 1.13 tickets out to 1.15 to make it easier to move tickets into the 1.13 milestone.
Note: See
TracTickets for help on using
tickets.
Possible fix