adityapooniya / base2

Automatically exported from code.google.com/p/base2
0 stars 0 forks source link

Binding to XMLResponse Object Fails in IE and Safari #81

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Attached is a test case for binding to the XMLResponse object.  I can't
actually recall if this worked in the last public beta.  In any case, the
file httpResponse.html includes my AJAX library hHTTP.js.  In hHTTP.js,
you'll see that the library attempts to automatically bind the XMLResponse
object.

I included a call to the file states.xml...  In Firefox 3, beta 5 and Opera
9.5, each correctly report the number of "hLocationState" elements as "66".
 Safari 3.1 reports no elements, but does not throw any errors.  IE6 and
IE7 throw an error that highlights something in the base2 code, object not
supported or some such.

That said, I'm not sure this is something you intend to work, but thought I
would alert you to it all the same.

Original issue reported on code.google.com by richy...@gmail.com on 6 Apr 2008 at 7:25

Attachments:

GoogleCodeExporter commented 9 years ago
This seems to be working in Safari 3.1 on Windows. Does it not work on Mac?

For MSIE the problem seems to be that expandos are not allowed on XML nodes. If 
there
is no work-around then it may be impossible to bind XML documents on MSIE. That 
would
be a real shame.

Original comment by dean.edw...@gmail.com on 6 Apr 2008 at 7:50

GoogleCodeExporter commented 9 years ago
Just tested Safari Windows, at first the response was "0", then after 
refreshing it
was "66".

I thought it might be a caching issue, so I disabled the cache on Safari Mac, 
but
it's still reporting "0".

Then I thought it might be something caused by my VPN connection, since that 
goes
through a proxy, I disabled that too, still have "0".

I have build 525.13 installed on both.

I'm not surprised there might not be a work-around for IE...  seemed too good 
to be
true. ;-)

Original comment by richy...@gmail.com on 6 Apr 2008 at 8:08

GoogleCodeExporter commented 9 years ago
I'm changing this to "WontFix". But you should read it as "CannotFix". :-)

Original comment by dean.edw...@gmail.com on 17 Aug 2008 at 3:57