Search supposed to support numeric input?

[bitwombat]

Hi,

Using v1.8.2, I have options that have numbers in them (eg. WHS301) and I find I can search for 'W' (or 'WH' or 'WHS'), but not '301'.

Is this meant to be? I had a thumb through the source but couldn't find what I was looking for.

I will create a testcase if this is not the intended behavior.

[tjschuck]

You need to set the search_contains option to true (it's false by default). Documentation here.

[bitwombat]

Thanks, that works, sorry it was a RTFM.

But wait... without that option, my searches do start from the middle of the word. It's specifically the numbers that are different:

Now I type a 3:

Something undocumented?

[tjschuck]

@bitwombat No worries — glad to help!

As for the behavior you're seeing, that is strange! What browser, browser version, OS, and OS version are you using? And what version of Chosen? If not the latest version, does it still happen on the latest version?

Can you link to a publicly accessible page (or a Fiddle) that shows the issue?

[bitwombat]

Will put together a testcase and fill out the questions on your contributing guidelines...

[tjschuck]

@bitwombat Thanks, that would be great!

[bitwombat]

Good news - jsFiddle knows about v1.8.5. Bad news, the link they use to cloudflare is 404.

This is 404
https://cdnjs.cloudflare.com/ajax/libs/chosen/1.8.5/chosen.jquery.min.js

and this
https://cdnjs.cloudflare.com/ajax/libs/chosen/1.8.4/chosen.jquery.min.js

but not this
https://cdnjs.cloudflare.com/ajax/libs/chosen/1.8.3/chosen.jquery.min.js

Want me to make a new issue for that?

[tjschuck]

@adunkman ^ Know anything about how those files end up there? Both of the versions you pushed today seem to not be currently working.

[adunkman]

Negatory… I assume a cron or something? But they seem to be working now!

[bitwombat]

Alright, here we go:

Steps to reproduce

Go to
current v1.8.5

Type "WHS" then "3" (no quotes)

Compare with:

v 1.6.1

I include both because they act differently. v1.6.1 highlights the first occurrence of "WHS", which makes the lack of matching of "WHS3" odd.

However 1.8.5 highlights the occurrence of WHS in the description part of the option, which if that means it's not seeing the first part, would make sense that "WHS3" doesn't match anything.

Expected behavior

Chosen should not be matching the middle of the string without the search_contains option.

With the current behavior which seems to be matching within the string anyway, Chosen should match BSBWHS302

Actual behavior

No results are found.

Environment

• Chosen Version:
  Shown in links above.

• jQuery or Prototype Version:
  See source.

• Browser and Version:
  Firefox 59.0.2 (linux)
  Chrome 65.0.3325.181 (linux)

• OS and Version:
  Linux

[tjschuck]

@bitwombat It looks like you're still missing the search_contains option. You need to set the search_contains option to true (it's false by default).

If you add search_contains: true in your example JS here http://bitwombat.com.au/chosen/js/init.js everything works as you'd expect:

Options documentation.

Please let me know if I'm misunderstanding your issue, though!

[bitwombat]

Correct. The issue is really that when the option is false, Chosen sort of, sometimes, matches things in the middle.

[tjschuck]

@bitwombat That's actually the correct, fixed behavior. When you have the option set to false, it's matching on the middle one because that's the first instance that actually matches with that rule — it doesn't match the first WHS because it's inside of a word, and it does match the second WHS (correctly) because that's the occurrence that starts on a word boundary.

PR #2692 is what fixed this behavior, and that fix was included in version 1.7.0.

[MB-Tom]

What if you must enter numbers only?

I am using a list of ALL numeric characters such as:

0400000010469004
0400000010468342
0400000010468949
0400000010469059
0400000010469106
0400000010468214
0400000010468932
0400000010469058
0400000010468438
0400000010467091
0400000010468973
0400000010469063
0400000010468341
0400000010468672
0400000010469081
0400000010468723
0400000010468081
...

Which gives:

I would like the users to only have to enter a partial of the number (eg. 68814) and get a result set, instead I get:

Chosen v1.8.7 / JQuery 3.3.1 / IE11 (Windows 10 Enterprise)

[tjschuck]

@MB-VictoryRider See my answer above here:
#2968 (comment)

You need to set the search_contains option.

[MB-Tom]

I did set it:
<script type="text/javascript"> $(".chosen-select").chosen({ search_contains: true }); </script>

if you try searching for 468 it doesn't find anything.
Sorry, pasting the entire code in as code didn't work. so I've attached an abbreviated file.

test_aspx.txt

[NarjisHasan]

Did anyone find the solution to the problem: all numerical options not searching from middle even with search_contains set to true ?