Any chance you can put the page you have a problem with on a public
URL and give us directions to reproduce the problem?
jjb

On Feb 25, 10:09 am, otie <[email protected]> wrote:
> loaded 1.3.3x recreated the problem - traced according to your
> instructions  - except I can't find a 'save to file' at the top of the
> trace window.  (http://kpftx.org/tmp/tracetop.gif)
> i can copy and paste, but that doesn't save the elegant plusses...
>
> FYI, a number of parse errors for css, but some don't make sense to my
> limited faculties (i.e. css looks ok). also some js errors (assign
> function to undeclared variable; function doesn't always return
> value).
>
> I'm perfectly happy to submit any and all source - it's open source
> anyway. whatever.
>
> I'm willing to do the different versions as well
>
> suggestions?
>
> On Feb 25, 9:56 am, John J Barton <[email protected]> wrote:
>
> >  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 
> > viahttp://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
-~----------~----~----~----~------~----~------~--~---

Reply via email to