Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simple AJAX call freezes browser #27

Open
performancewanted opened this issue Apr 13, 2012 · 3 comments
Open

Simple AJAX call freezes browser #27

performancewanted opened this issue Apr 13, 2012 · 3 comments

Comments

@performancewanted
Copy link

Using jQuery 1.6.4, this causes an infinite loop somewhere deep inside jQuery and eventually gets terminated by the browser (Firefox). This is very simple data retrieval of only a few items, so I'm surprised this plugin is broken. I'm using the latest zipball Chosen and the latest zipball of this project. Chosen worked fine by itself (but sluggishly) so I was looking for possible AJAX solutions. This seemed like it would fit the bill perfectly but it unfortunately freezes. Firebug confirms that valid JSON data is being returned from the server. I followed the example demo you provided pretty closely.

@meltingice
Copy link
Owner

I'll look into it, but if you're looking for something more robust, I would check out select2.

@performancewanted
Copy link
Author

select2 looks really nice. (The AJAX example has photos - woot!). I'll try that. Thanks.

@perryzheng
Copy link

Can select2 do multiple selects through ajax?

I have a element with already prepopulated options. For the ones that are not on the options list, I want to repopulate the list through the ajax call. However, select2 doesn't allow me bind an ajax option to a element (only <input type="hidden" ..>. In that regard select2 is better.

However, I am running into a lot of weird issues with ajax-chosen on the ipad. Most of it is due to the fact list:updated clears the field so the cursor would jump back and forth when you type. Is there a more efficient way to update the list so we don't have this problem on the ipad?

Either solution works: a fix that would allow it to work well with iPad or a good workaround with select2.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants