On Jul 16, 4:53 pm, patrick <[email protected]> wrote:
> Hi,
>
> I just upgraded firebug, and I am experiencing some problems.
>
> Upon loading an app I am working on, I get "Reload to activate window
> console", and reloading seems to do nothing.  It appears if I switch
> back and forth several times between two pages, this goes away.

Sounds like
http://code.google.com/p/fbug/issues/detail?id=2042&sort=-id

>
> The terrible thing is, when this message appears, it seems that JS is
> completely disabled.  I have some links that are using the lowpro
> library that have an Event.addBehavior set to change their click to
> perform a JS function, and nothing happens.  Its only when I click
> back and forth between two pages and the "reload to activate window
> console" message is gone that the JS calls actually go through.

Open Firebug and reload the web page. Ignore the message. If you have
another problem, it's a another problem.  But that one sounds too
bizarre.

>
> ...  Also, when I click the arrow w/ box icon (which replaced
> "inspect"), half of the webpage background turns white (not sure what
> is actually happening, but I have a div with a repeating background
> image and half of it just becomes solid white when I go into inspect
> mode!).

Really on 3.0? Sounds like
http://code.google.com/p/fbug/issues/detail?id=1999
Will be fixed in 3.5.1 I understand.

>
> So, as of now I am regretting upgrading because this is going to slow
> down my development process...  Can anyone recommend a way to
> downgrade back to the previous version?

All versions of Firebug are available from http://getfirebug.com/releases.

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