SprySuggest fails in IE with dynamic server data

Question

When using SprySuggest with dynamic server xml suggestions,
the suggestions are never displayed in IE, if the XML response does
not have the correct content-type. Code in SpryData.js attempts to
handle this situation, but it did not work in my configuration,
until I made the change shown below in bold.
Spry.Data.XMLDataSet.prototype.xhRequestProcessor =
function(xhRequest)
// XMLDataSet uses the responseXML from the xhRequest
var resp = xhRequest.responseXML;
var manualParseRequired = false;
if (xhRequest.status != 200)
if (xhRequest.status == 0)
// The page that is attempting to load data was probably
loaded with
// a file:// url. Mozilla based browsers will actually
provide the complete DOM
// tree for the data, but IE provides an empty document node
so try to parse
// the xml text manually to create a dom tree we can use.
if (xhRequest.responseText && (!resp ||
!resp.firstChild))
manualParseRequired = true;
else if ( (!resp) || (!resp.getElementById))
// The server said it sent us data, but for some reason we
don't have
// an XML DOM document. Some browsers won't auto-create an
XML DOM
// unless the server used a content-type of "text/xml" or
"application/xml".
// Try to manually parse the XML string, just in case the
server
// gave us an unexpected Content-Type.
manualParseRequired = true;
if (manualParseRequired)
resp = Spry.Utils.stringToXMLDoc(xhRequest.responseText);
if (!resp || !resp.firstChild || resp.firstChild.nodeName ==
"parsererror")
return null;
return resp;
};

Answer 1

Hi John,
it is a known IE browser behavior for the files that don't
have the content-type set on xml, that will not get be interpreted
as text. So if you want to have your page working ok, you must
assure that the server response contained an xml and not other
content-type.
Diana