IE9 and domLoader problem

Leo Tohill
  • Leo Tohill

    Leo Tohill - 2010-10-23

    IE9 has added a native domLoader which breaks existing Sarissa apps.  I think that the problem is that Sarissa is using the IE9 native domLoader instead of emulating it (good) but is not adding the enhancement methods such as setProperty that it does  for non-IE browsers (bad).
    The following will demonstrate: hope it's not bad form to post all this:

    <html xmlns="" xml:lang="en" lang="en">
        <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
        <title>ie9 Sarissa test</title>
        <script type="text/javascript" src="sarissa-full-"></script>
        <script type="text/javascript" src="sarissa-full-"></script>
        <script type="text/javascript">
            function xmltest() 
                var xmlDoc = Sarissa.getDomDocument();
                xmlDoc = (new DOMParser()).parseFromString("<xml/>", "text/xml");
                xmlDoc.setProperty("SelectionNamespaces", "xmlns:xsl=''");
                alert("It worked ok.  You must not be in native IE9 mode. ")
                 catch (e)
        Demonstrates Sarissa problem on IE9.<br/>
        Clickme runs JS that uses the DOMParser setProperty method.<br/>
        That reference will fail when running IE9 (in IE9 mode).<br/>
        Problem reproduced on IE9 beta 9.0.7930.16406 with Sarissa<br/>
        <button  onclick="javascript:xmltest()">Clickme</input>
  • Anonymous - 2011-07-02

    Thanks for the info!!! I was wondering why my scripts won't work in IE9.

  • Zsolt Zsuffa

    Zsolt Zsuffa - 2011-07-06

    Well, now I'm not wondering why my scripts don't work in IE9, but looking for a solution.

    Any idea, how to overcome on this issue?


  • Emmanuil Batsis (Manos)

    Wow had not idea about the issue, haven't used IE for a looong time. Anyone got a patch for this?

  • Leo Tohill

    Leo Tohill - 2011-07-06

    I did a bit of digging and I imagine the problem could be fixed pretty easily.  I don't have time now to do it myself.  Too bad the project isn't active anymore. 
    For now, I'm working around it by forcing ie9 into ie8 mode, using this metatag:

    <meta http-equiv="X-UA-Compatible" content="IE=8"/>

  • Zsolt Zsuffa

    Zsolt Zsuffa - 2011-07-08

    I've been fallen back to this solution too, though would be better to have a solution which doesn't requires this post massage of existing html documents. Resolve browser incompatibilities, that's the whole idea behind Sarissa, right?

    I played a while with IE9 DOMParser. The returned document lacks, not only the setProperty method, but also selectNodes,

  • Keith Pepin

    Keith Pepin - 2011-09-06

    One other community member discussed how this might be fixed in the Sarissa code on this thread:

    Has any effort been made by the Sarissa team to integrate these suggestions/solutions?  Having Sarissa not work in IE9 seems to be a fairly glaring problem and I'm surprised there hasn't been a patch/fix released since 9.9.5 was released over a year ago as of this writing.


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks