betamos/Better-Autocomplete

Test and eliminate bugs in IE 7-9 [Need help]

Closed this issue · 14 comments

I want BAC to work in IE 7-9, if this is fairly straightforward I want it done before the initial release. I don't have easy access to a Windows machine right now, but I will try my best to fix it myself.

If you feel that you can help out, it would be awesome. Just send me a pull request or a patch.

IE 9 and 8 are highest priority. IE7 support is not essential.

I have tested the implementation with Linkit and BAC in IE7-9 and as far as I can see it works pretty well.

(If this is fixed #11)

Thanks, did you find a solution for the cross origin JSON communication?

$.support.cors = true; didn't work for me :/

jQuery.support.cors = true; // force cross-site scripting (as of jQuery 1.5)

Works perfect with IE7-9..

Insert before the ajax call in "fetchRemoteData"

I'm glad it worked but it cannot require to change the source code. Can you
move that line outside better-autocomplete.js and any callbacks? The optimal
solution would be to run that line in your local script file before
instantiating better autocomplete, since even jQuery won't deal with IE:s
XDomainRequest object. Is that possible? Use example.html to test.

On Thu, Jul 7, 2011 at 2:08 AM, bratanon <
reply@reply.github.com>wrote:

jQuery.support.cors = true; // force cross-site scripting (as of jQuery
1.5)

Works perfect with IE7-9..

Insert before the ajax call in "fetchRemoteData"

Reply to this email directly or view it on GitHub:

#10 (comment)

If I put the support.cors insude the $(document).ready function in example.html, its the same result. Works prefect.

Hmm, its works when I run this in my apache-windows, but not in apache-ubuntu.

Ah, Think I found it.

Try using "dataType: 'jsonp'" in the ajax request.

Then the support.cors is unnecessary.

Really strange with the Windows/Ubuntu Apache differences. Could there be something else that differs between the installations? Local domain name bugs?

JSONP is not as awesome as JSON so JSON will still be default. The integrating developer can simply override the fetchRemoteData callback.

Yes your right about that. Maybe just a little comment on this in the code so users will have easy access to this infomation?

Sure, but the $.support.cors is still a mystery to me, I would like some clarification so we can help IE users in the best possible way...

This thread fell off topic, so I created another issue for the cross origin stuff: #15

I consider this issue done since it is not specific and it's already tested in IE7+