Jvaneyck

[...] me with a concise description of the problem or an overview of alternatives to perform Cross-Domain requests, so this post will serve as a personal future reference. Same-Origin Policy We are seeing [...]

[...] still applied. Here is a non-exhaustive list of issues I faced: Browsers do not allow cross-domain requests out of the box. You can call this secure, but it’s also painful to work with. This [...]

[...] JavaScript communication API’s was mostly a reminder of one of my previous posts: Cross-Domain requests in Javascript. He also discussed the new HTML5 WebSockets API. You can use this API [...]

[...] just finished your work. You pull in the latest changes from other developers and run all the unit tests. If the bar is red, you fix the integration problem. If the bar is green, you can commit your [...]

[...] framework code is designed to run on a mobile device, so it would be impossible to run any unit tests on my desktop computer if the code-under-test had any dependencies on Cordova. The codebase did [...]

[...] forced me into stubbing out all dependencies on the Crossrider framework for my local unit tests. Javascript, being a dynamic language, made stubbing the API very easy. I did not have to write [...]

[...] have access to the full content. Fun fact: 10% (!) of your users are still using Internet Explorer 8, which means that these users would miss out on your cool images drawn on a < [...]

[...] /JavaScript (except Internet Explorer, which requires you to dig up your C++ skills) and each of them have different API’s [...]

[...] . As always, there are some limitations to this approach. For example, older versions of Internet Explorer only partially support CORS. Also, for all but the simplest requests you have to double the [...]

[...] . All you have to do is: Host a local web server that grants local http access to your source code (I used the lightweight and easy to use mongoose). Install a “local development” [...]

[...] ;responsible” part of solid design and testing very nicely. [UPDATE] I have put the source code on github. For those of you who just want to try out the app, use this link or the QR code [...]

[...] ). Most importantly: treat your build scripts with the same diligence as you treat your source code: put them under source control and apply best practices like removing duplication and choosing [...]

[...] don’t support Javascript Web Workers, I’m looking at you IE 9.0!-, you use the Crossrider API. Crossrider builds your extension for you phonegap build-style: you provide your source files, [...]

[...] -browser requirements I can only recommend it. It provides a nice abstraction for different browser implementations and offers easy distribution of your extension and a near painless installation [...]

[...] edge A downside to living on the bleeding edge is that you have to deal with different browser implementations and different levels of support in each browser. This is ever so true when it [...]

[...] . Fallbacks can be divided into two groups, HTML-based fallbacks and fallbacks for HTML5 Javascript API’s. HTML fallbacks HTML elements themselves provide a fallback mechanism. An example [...]