I remember two more approaches that some users have adopted for cases where a feature that worked for them in the past fails on a new version.
First.you can try versions of Firebug between the one that fails and the one that works until you narrow down the change that affects you. All of the past releases are available via http://getfirebug.com/releases/firebug, including all the alpha and beta versions. So for example 1.2.1 is followed by 1.3.0a1. Second you can try Firebug in Firefox 3.0.2. Around Firefox 3.0.3 a new API was introduced that affects the way Firebug gets source files. If your problem is different in 3.0.2 then we have some hints. These are both tedious and may not help, but they are straight forward to try. jjb --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
