Opened 13 years ago

Closed 10 years ago

#8049 closed defect (invalid)

Weird timing issue with firebug stubs in bootstrap.js when loading XHTML document causes exception during load

Reported by: otakuj462 Owned by: otakuj462
Priority: low Milestone: future
Component: Core Version: 1.2.0
Keywords: needsreview Cc:
Blocked By: Blocking:


There is a strange timing issue that is causing dojo to fail to load properly in my development environment. My setup is as follows: Firefox 3.0.3 on Ubuntu 8.10, using Firebug 1.2. The issue seems to be that when loading an HTML document with dojo and the firebug console enabled, window.console is available immediately, and so is available when bootstrap.js checks for its existence. Unfortunately, when loading an xhtml document, window.console is not available when bootstrap.js checks for it. It then proceeds to instantiate a new object for window.console. However, very mysteriously, after it constructs the new console object, it nevertheless throws an error on the following line, because console is undefined:


I attempted to debug this a bit, and so set a breakpoint on the following line:


In this case, window.console is available. So it really does seem to be an issue of timing.

This issue affects dojo releases 1.1.1, 1.2.0, and 1.2.1.

The following should fail to load under a similar setup:

And the following should successfully load:

Change History (5)

comment:1 Changed 13 years ago by Tom Trenka

Component: GeneralCore
Owner: changed from anonymous to James Burke
Priority: highestnormal

comment:2 Changed 13 years ago by dante

Milestone: tbdfuture

comment:3 Changed 10 years ago by ben hockey

Keywords: needsreview added
Priority: highlow

bootstrap.js is gone - does anyone know if this is still an issue?

comment:4 Changed 10 years ago by bill

Owner: changed from James Burke to otakuj462
Status: newpending

That link doesn't work anymore (at least not, so we'd need a test case (attached as an HTML file) if this is still an issue. Although even then, it's hard to debug if it just happens on ubuntu. We could easily test it if it fails on firefox/mac.

comment:5 Changed 10 years ago by trac-o-bot

Resolution: invalid
Status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!

Note: See TracTickets for help on using tickets.