[dojo-contributors] Bug or feature in bootstrap2.js?

Brad Neuberg bradneuberg at yahoo.com
Wed Jun 28 07:21:17 EDT 2006

Hi folks; I'd like to fix some code in bootstrap2, but I want to make sure it is a bug and not a feature :)

Here's my situation: I have an OPML file that gets loaded on the client, such as test.opml. This OPML file has a direct line to transform it on page load using an XSLT stylesheet:

<?xml-stylesheet type="text/xsl" href="../client/lib/hs/xslt/hyperscope.xsl" ?>

This XSLT stylesheet writes out all of my HTML, script tags, etc for the 'chrome' of my application (it's an application that presents a user-interface for working with arbitrary OPML files). Here's a taste of hyperscope.xsl:

<xsl:stylesheet version="1.0"
    <xsl:template match="/">
            <title>Address Demo</title>
            <script type="text/javascript">
                var djConfig = { isDebug: true, disableFlashStorage: true };
            <script type="text/javascript" src="../client/lib/dojo/release/dojo/dojo.js.uncompressed.js"></script>
            <script type="text/javascript" src="address.js"></script>
There's alot more written out, but the important part is notice that I load all my JavaScript.

Here's the problem: when isDebug is true, things freak out: the page keeps spinning forever, and I get JavaScript errors like 'dojo.lang not found'; I don't get this if isDebug is false, but I'd like isDebug to work or else I'll have to revert to alert() statements, and then I will really go mad :) 

I've tracked the offending problem down here in bootstrap2.js:

    //Don't do this work if dojo.js has already done it.
    if(typeof dj_usingBootstrap != "undefined"){

    var isRhino = false;
    var isSpidermonkey = false;
    var isDashboard = false;
    if((typeof this["load"] == "function")&&(typeof this["Packages"] == "function")){
        isRhino = true;
    }else if(typeof this["load"] == "function"){
        isSpidermonkey  = true;
    }else if(window.widget){
        isDashboard = true;

    var tmps = [];


    //Support compatibility packages. Right now this only allows setting one
    //compatibility package. Might need to revisit later down the line to support
    //more than one.
        tmps.push("compat/" + djConfig["compat"] + ".js");

    var loaderRoot = djConfig["baseScriptUri"];
        loaderRoot = djConfig["baseLoaderUri"];

    for(var x=0; x < tmps.length; x++){
        var spath = loaderRoot+"src/"+tmps[x];
        } else {
            try {
                alert("writing " + spath);
                document.write("<scr"+"ipt type='text/javascript' src='"+spath+"'></scr"+"ipt>");
            } catch (e) {
                var script = document.createElement("script");
                script.src = spath;

Notice how this code builds up optional JS files, like debug.js; these then get written out to the page with a document.write. One problem: what if you are in an environment where the page is already loaded, like in my situation, and document.writes simply create evil for you? 

The document.write freaks out my page; I'd much rather add a script tag to the DOM. However, this code isn't documented, so I'm not sure if document.write is a 'feature' that is fixing something, or if someone just coded it that way for some reason. Is there person who wrote this here?

Here's what I'd like to do: change this to be what happens in the exception:

            try {
                 var script = document.createElement("script");
                  script.src = spath;
             } catch (e) {
                  // What to do with exception?   

Is there a reason I can't do this? Also, what should I do with the exception here?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.dojotoolkit.org/pipermail/dojo-contributors/attachments/20060628/b8777d0d/attachment.htm 

More information about the dojo-contributors mailing list