johnjbarton wrote: > Hi Don. > > Based on your description I'd say Break On Next worked perfectly. Only > the next JS was so fast you never saw the throbber start.
OK, thanks; not a big deal at this point. I just wanted to get a feel for it. > Assuming that this is true, then the problem is that you really did > not mean "break on next", In complex app, esp built on a library we > don't understand, we want Break On Next to mean "break on the next > thing that interests me". > > Any idea (short of mind reading) on how to allow users to indicate > what kinds of things they want to break on are welcome. I can see this will be a problem with an app built on something as large and complex as ExtJs. There's a lot of stuff going on "under the hood" that I wouldn't want to have to deal with. The only thought that occurs to me at the moment is this: Typically, for a web app, the "infrastructure" (e.g. ExtJs) will get loaded once via one or more script tags. Some of my own code will be loaded the same way, other parts will be dynamically loaded via evals of code blocks sent in XHR responses. If I really wanted the "break on next" capability, I'd be willing to somehow "flag" my own code blocks (maybe extra attributes on script tags and parameters on XHR requests?). Then Firebug would know to only break on entry to a flagged block. FWIW, -- Don Dwiggins Advanced Publishing Technology --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
