Hmmm. I'm using qooxdoo which can be set to use either the javascript files directly or a heavily compressed build version in a single file. I modified the server to not cache the "source" files which is what is used for debugging. All the Javascript files can be seen in Firebug 1.3.x now, as expected.
However I still have the issue of breakpoints not being hit when restarting my application as mentioned in issue 1054. I'll work on a simpler test case for you. Hugh Hugh Gibson wrote, on 02/12/2008 06:08: > John, > > Thanks. I can modify the server to not cache these debug files. > > The implication of that Mozilla bug report is that Firebug has worked > around all the problems. > > It seems likely that the issues I have seen at > http://code.google.com/p/fbug/issues/detail?id=1054 are related to the > same bug. I'll do some more testing to try and establish that. > > It might be worthwhile making another "official" posting in the Mozilla > bug report about these new Firebug issues that can't be worked around. > > Hugh > > John J Barton wrote, on 01/12/2008 16:51: >> Hugh, your diagnosis seems correct. We know that there is a problem >> when Firefox starts from cache-only resources. The nsITraceableChannel >> does not see any inputs from the cache. >> >> Our choice are 1) wait for Firefox to fix the cache notification bug >> https://bugzilla.mozilla.org/show_bug.cgi?id=449198 >> or 2) put up a notice with a button to force reload >> or 3) something I don't know about. >> Obviously we are choosing #1 now. >> >> John. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
