2019 modern browsers update This is the approach I’d now recommend with a few caveats: A relatively modern browser is required If the file is expected to be very large you should likely do something similar to the original approach (iframe and cookie) because some of the below operations could likely consume system memory at least as … Read more
When you call loadTeachers() on DOMReady the context of this will not be the #CourseSelect element. You can fix this by triggering a change() event on the #CourseSelect element on load of the DOM: Alternatively can use $.proxy to change the context the function runs under: Or the vanilla JS equivalent of the above, bind():
When logging a formData object with just console.log(formData) it always returns empty, as you can’t log formData. If you just have to log it before sending it, you can use entries() to get the entries in the formData object
AJAX does the magic:
Possible repeated question from How to overcome the CORS issue in ReactJS CORS works by adding new HTTP headers that allow servers to describe the set of origins that are permitted to read that information using a web browser. This must be configured in the server to allow cross domain. You can temporary solve this … Read more
In your action method, return Json(object) to return JSON to your page. Then just call the action method using Ajax. You could use one of the helper methods from the ViewPage such as SomeMethod would be a javascript method that then evaluates the Json object returned. If you want to return a plain string, you … Read more
As you’re making a synchronous request, that should be Example – http://api.jquery.com/jQuery.ajax/#example-3 PLEASE NOTE: Setting async property to false is deprecated and in the process of being removed (link). Many browsers including Firefox and Chrome have already started to print a warning in the console if you use this: Chrome: Synchronous XMLHttpRequest on the main … Read more
The solution that was eventually implemented was to use a wrapper for the callback function of the Ajax call and in this wrapper check for the existence of a specific element on the returned HTML chunk. If the element was found then the wrapper executed a redirection. If not, the wrapper forwarded the call to … Read more
I think you need to have strings as the data values. It’s likely something internally within jQuery that isn’t encoding/serializing correctly the To & From Objects. Try: Notice also on the lines: You don’t need the jQuery wrapper as To & From are already jQuery objects.
Edit There appears to be a better LZW solution that handles Unicode strings correctly at http://pieroxy.net/blog/pages/lz-string/index.html (Thanks to pieroxy in the comments). I don’t know of any gzip implementations, but the jsolait library (the site seems to have gone away) has functions for LZW compression/decompression. The code is covered under the LGPL.