Safari supports DOMParser since 2.0.1, thus both WebKit and Chrome
(which uses WebKit) support that as well.
-Matej
On Thu, Sep 4, 2008 at 5:26 PM, lesterburlap <[EMAIL PROTECTED]> wrote:
>
> This is the related section of wicket-ajax.js (~line 985 in 1.3.4) right
> before that error message is logged. I can't find much of anything on the
> Internet about Chrome or WebKit supporting DOMParser, so that may be it...?
>
> // parse the response if the callback needs a DOM tree
> if (this.parseResponse == true) {
> var xmldoc;
> if (typeof(window.XMLHttpRequest) != "undefined" && typeof(DOMParser) !=
> "undefined") {
> var parser = new DOMParser();
> xmldoc = parser.parseFromString(responseAsText, "text/xml");
> } else if (window.ActiveXObject) {
> xmldoc = t.responseXML;
> }
> // invoke the loaded callback with an xml document
> this.loadedCallback(xmldoc);
> } else {
> // invoke the loaded callback with raw string
> this.loadedCallback(responseAsText);
> }
> --
> View this message in context:
> http://www.nabble.com/Google-Chrome---Wicket-tp19277005p19312785.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
