I've learned a bit more about what's going on.  If I wrap console.log
and console.debug with this code

        /** Wrapper for console.log to be sure it is defined
        */
        GW.consoleLog = function( ){
            // check if console.log is ready
            if( console.log ) console.log( ':: ', arguments[0] );
            // check that GW.log is defined
            if( GW.log ) GW.log( ':: ' + arguments[0], 'info',
'gw');
        };
        /** Wrapper for console.debug to be sure it is defined
        */
        GW.consoleDebug = function( ){
            // check if console.debug is ready
            if( console.debug ) console.debug( ':: ' + arguments[0] );
            // check that GW.log is defined
            if( GW.log ) GW.log( ':: ' + arguments[0], 'dbg', 'gw');
        };

The symptom vanishes.  Clearly console.log/console.debug is being
invoked before the console is defined.  Here is the contents of GW.log
(YUI's log)

INFO 3422ms (+61) 2:41:53 PM: gw: :: GW.pageOnLoad
INFO 3361ms (+14) 2:41:53 PM: LogReader instance0: LogReader
initialized
INFO 3347ms (+1674) 2:41:53 PM: gw: :: GW.onLoad
DBG 1673ms (+107) 2:41:51 PM: gw: :: GW.mapedit
DBG 1566ms (+1566) 2:41:51 PM: gw: :: GW.map
INFO 0ms (+0) 2:41:50 PM: global: Logger initialized

And here is the contents of firebug's console

:: gwcommon.jsTestPage# (line 56)
:: GW.mapTestPage# (line 56)
:: GW.mapeditTestPage# (line 56)
:: GW.onLoad
:: GW.pageOnLoad

Note that gwcommon.js appears in console but NOT the log.  Clearly the
script that initializes GW.log has not loaded.

I'm suspicious that the console issue derives from when during the
page load sequence console.log and console.debug are defined.  Can
anyone provide some insight into this?

Regards,
puff


On Jan 27, 11:30 am, puff <[email protected]> wrote:
> Interestingly, firebug breakpoints have also stopped working.  It's as
> though firebug is simply not there.  Firebug is active for the domain
> and clicking the firebug icon gets the firebug panel up with expected
> content.
>
> On Jan 27, 11:22 am, puff <[email protected]> wrote:
>
> > I'm having an issue with console.  I've a google appserv application
> > (source athttp://code.google.com/p/appspot-geowiki/, hosted 
> > athttp://great-loop.appspot.com).  The application runs ok WRT console
> > on a local server but when uploaded to google appserver problems occur
> > when accessinghttp://great-loop.appspot.com/wikiedit/TestPage(you'll
> > need a gmail account to login).
>
> > A bit of debugging (don't you just love falling back to alert) reveals
> > that loading this page fails when the onload script encounters a
> > console.log.  The onload script terminates so that the page is not
> > properly loaded.  Sometimes I get a "console not defined" error.
> > Other times the page loads but the onload scripts do not run so the
> > page is not complete.
>
> > This page is heavily scripted.  It may be that there are issues around
> > script load order (I've been suspicious of this previously).  That
> > said, I would expect console to work in the page's onload.
>
> > At any event:
>
> >  * Are there known issues with firebug console in this environment?
> >  * Are there any work arounds?
> >  * Am I doing something clearly wrong?
>
> > Thanks for any clues.
>
> > Regards,
> > puff
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Firebug" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to