Comments on: Supported browsers

By: Aktham Nassar

Aktham Nassar — Wed, 23 Mar 2016 19:55:00 +0000

Hello

easyXDM working just fine in IE8, but in IE11 I am getting a javascript error from provider page:
File: Provider.html, Line: 24, Column: 18927
“Unable to get property ‘parse’ of undefined or null reference”

Can you please help?

By: lukeyb152

lukeyb152 — Wed, 10 Jul 2013 10:20:00 +0000

Hi, I’ve been experimenting with this for some time now. I’m having a fairly trivial problem. Frameborders in IE8 and below will not go away.

If you could help, that would be great! Thanks

By: dhar

dhar — Fri, 29 Mar 2013 15:11:00 +0000

hi i downloaded your examples and it works perfectly fine on firefox and chrome, but it’s not working on IE8 and under, can you help me with this?

By: Michiel

Michiel — Sat, 04 Sep 2010 22:00:00 +0000

Hehe – for sure! I’ll subscribe to the list.

Thanks.

By: Øyvind Sean Kinsey

Øyvind Sean Kinsey — Sat, 04 Sep 2010 21:42:00 +0000

It’s kind of hard to debug without knowing the error message you know 😉
Do you mind continuing this on the mailing list?

By: Michiel

Michiel — Sat, 04 Sep 2010 21:38:00 +0000

That was fast 😉

Your answers are clear – thanks!
One more for you – I keep getting an error (firebug) at the moment, trying to use RPC:

JSON.parse
var data = serializer.parse(message);

Not doing anything advanced – simple remote method call. Can’t seem to find out why it breaks on this line. Any clues?

By: Øyvind Sean Kinsey

Øyvind Sean Kinsey — Sat, 04 Sep 2010 21:08:00 +0000

1)
No, local set on the provider, and local and remoteHelper on the consumer is only needed if you want the fast NameTransport to be used instead of the slower HashTransport when no other transports are available (only very old browsers).

2)
json2.is needed if you want to use the RPC feature in a browser that hasn’t got a native JSON feature. The current examples of cross domain ajax use the RPC feature, but it can be done using a Socket, but with a bit more work involved.

Regarding jQuery, no, there are no such plans, nor is it natural in any way.
easyXDM is a framework agnostic library usable for all, and though it could be wrapped within jQuery, the question of why still stands (I was actually discussing this with Paul Irish the other day).
For those who want this feature, they should use easyXDM directly, and know what it means to use it (as you could potentially expose your server resources without knowing it).
But sure, it is possible to wrap the native post/get methods and instantiate an easyXDM object internally when the call is going to a remote domain, but that would also mean that you would need to tell easyXDM where to find the remote endpoint, something that means that you will need to break the standard post/get paradigm anyways – so why not just use easyXDM directly right?

I hope that answers your questions 🙂

Sean

By: Michiel

Michiel — Sat, 04 Sep 2010 20:56:00 +0000

Great lib! Now trying to get it working in a project I’m doing. Few questions though:

1) is the ‘local: ‘name.html’ file needed?

The reason for this question is that I’d like for the customer page to only include 1 single JS file that does the job for me. I’d like to use rpc or XD Ajax but cannot ask my users to also include the name.html file. Does this have a crossbrowser effect or is it purely performance the name.html file is used for?

2) Do I need json2.js?
As said, I’d like to use this as a cross domain ajax implementation – however – the json2 file adds quite a lot to the footprint. So the question is, do I need to include this file if I want to support cross domain Ajax from IE6 and up (+plus all other browsers of course)?

Would be great if you could provide some answers. Also – any plans to convert this thing into a native jQuery plugin so jQuery can transparently support cross-domain Ajax? I think it would be a killer plugin (worthy of a place in the jQuery Core even).

Thanks,
Michiel