[EMAIL PROTECTED] wrote: > Hi, > > I have an embedded application that uses the XSLTProcessor within > javascript to generate an html document. The problem is that whenever I > generate an img tag I get a few assertions: > > ASSERTION: Could not get loadgroup; onload my fire to early: > 'loadGroup', file j:/mozilla/content/base/src/nsContentUtils.cpp, line > 1730. > > The file is generated fine (I write it out for caching), but when I > load it with window.location.href = "test.html" or document.write(...) > the images are broken. If I load the same html file without doing the > transformation the images are ok. > > The assertions only appear when img tags are involved. From the > debugger I can see that it all begins with nsIHTMLElement::setAttribute > and the name of the image. > > I've run out of things to try. Anybody have any ideas?
Ok, I found the "problem". It turns out the assertions are really warnings (NS_WARN_IF if I'm correct). The problem is that I had a javascript function that would persist xml to file and return a file name. In the process of fixing these warnings I modified that name of the file the function would return. So instead of returning a relative path, ../cache/test.html, I changed it to the URI, file://c:..../cache/test.html. (used in window.locaction.href) This caused more problems than just the broken images. Javascript functions did not work at all. Nasty problem. _______________________________________________ mozilla-embedding mailing list [email protected] http://mail.mozilla.org/listinfo/mozilla-embedding
