4 ms·

TL;DR; JSONP is the only hack that is IE proof IE6, as usual, doesn’t support postMessage. IE6 and IE7 both lack CORS support, while IE8 and IE9 have broken i

TL;DR; JSONP is the only hack that is IE proof IE6, as usual, doesn’t support postMessage. IE6 and IE7 both lack CORS support, while IE8 and IE9 have broken implementations Oh what mankind could have achieved by now if we weren't so occupied making our websites work in IEx.

justatdotin 14y ago
... if we weren't so occupied making our websites work for users ... ? deal with it: or not.
voltagex_ 14y ago
xdr.js will mostly work for IE7/8 as far as I can tell.
RKearney 14y ago
Well people need to stop writing code specifically for IE and just stick to web standards. If Google/Facebook/PayPal/All Banks stopped coding hacks to get their sites to work in IE, the users that use IE would have no other choice but to switch to a standards compliant web browser.
- deleted 14y ago
  [deleted]
- prodigal_erik 14y ago
  IE users should get the standard-compliant pure-HTML version which is sure to work on every browser. Only developers who neglected to start there have a problem.
  - esrauch 14y ago
    I dont buy it. Some features just aren't reasonable to do without js and the number of people without js is tending towards vanishingly small, and you can have a nondegraded experience for a very significant percentage of traffic by not just dismissing all versions of IE. Not that you should support all versions, but if you are sending a separate no-js version to IE10 then you are doing it wrong. In my experience it is totally absurd to think that you can just write "standards compliant HTML" and expect it to be rendered correctly on IE6 or 7 in any meaningful way anyway, you will always need to change your HTML and CSS to specifically support those browsers and realistically any browser that you want to support, the standards just are not uniformly implemented.
philbo 14y ago
Alternatively, we could stand on the shoulders of giants. I've used the easyXDM library to abstract away cross domain hassle in a couple of large projects and am surprised it doesn't seem to be more widely known of. https://github.com/oyvindkinsey/easyXDM https://github.com/oyvindkinsey/easyXDM

justatdotin 14y ago

... if we weren't so occupied making our websites work for users ... ? deal with it: or not.

voltagex_ 14y ago

xdr.js will mostly work for IE7/8 as far as I can tell.

RKearney 14y ago

Well people need to stop writing code specifically for IE and just stick to web standards. If Google/Facebook/PayPal/All Banks stopped coding hacks to get their sites to work in IE, the users that use IE would have no other choice but to switch to a standards compliant web browser.

deleted 14y ago
[deleted]
prodigal_erik 14y ago
IE users should get the standard-compliant pure-HTML version which is sure to work on every browser. Only developers who neglected to start there have a problem.
- esrauch 14y ago
  I dont buy it. Some features just aren't reasonable to do without js and the number of people without js is tending towards vanishingly small, and you can have a nondegraded experience for a very significant percentage of traffic by not just dismissing all versions of IE. Not that you should support all versions, but if you are sending a separate no-js version to IE10 then you are doing it wrong. In my experience it is totally absurd to think that you can just write "standards compliant HTML" and expect it to be rendered correctly on IE6 or 7 in any meaningful way anyway, you will always need to change your HTML and CSS to specifically support those browsers and realistically any browser that you want to support, the standards just are not uniformly implemented.

philbo 14y ago

Alternatively, we could stand on the shoulders of giants. I've used the easyXDM library to abstract away cross domain hassle in a couple of large projects and am surprised it doesn't seem to be more widely known of. https://github.com/oyvindkinsey/easyXDM https://github.com/oyvindkinsey/easyXDM