> AFAIK toolbars have not been removed, only the addon bar has. I hope you're right. I'd read various complaints (a couple of months ago, I guess) on a few different online forums about Australis killing all toolbars, including custom toolbars needed by extension developers... but perhaps they were mistaken, or maybe Mozilla has added more flexibility. I haven't experimented with Australis myself; I just assumed the complaints were accurate.
For the second error, can you post a link to some page online where that > message can be reproduced, and somewhat more detailed instructions? It > sounds like it's something like Firebug trying to copy styles from the page > and failing because of CSS oddities, which isn't anything to worry about at > all but clearly still ought to be fixed if possible. > > I've just done a lot more experimenting, disabling various extensions and themes, relaunching Mac Firefox repeatedly, etc. I finally discovered that the problem happens even with *all* extensions and themes disabled except Firebug itself. So it isn't an extensions conflict. I also discovered that the problem happens if the "Warnings" button is enabled in the Console, but if I only have "Errors" enabled, the problem goes away. So I guess I just can't use Warnings any more. By the way, can somebody explain the relationship between the choices you can check in the popdown menu -- like "Show JavaScript Errors", "Show JavaScript Warnings", etc. -- and the simple "All"/"Errors"/"Warnings" buttons along the top of the Firebug panel? (I should explain that I run Firebug in a standalone window on a separate monitor.) At present, the popdown-menu options seem to have no effect at all, although the buttons work. I also tried to find online pages that exhibited the problem I was describing, that is clicking with the "Inspect Element" tool generating these weird warnings. But I discovered that on common pages such as https:// /www.google.com or http://www.bbc.co.uk/news/ I can't even get that far -- if the Warnings button is enabled, the Console panel fills up with many, many warnings before I even get a chance to click anything. (Not always at first load, but always on reloading those pages.) I also discovered that the same version of Firefox + Firebug on Win7 generates different messages in general than on the Mac, looking at the same pages. As I said before, the Windows version generates far fewer of the weird Warnings (generally none for my own pages). But it flags some things as Errors that the Mac doesn't -- for example, in a JavaScript "for loop", I had started it (as I usually do) like this: for(i=0; and Mac FF/Firebug had no problem with that, but the Windows version flagged it as an undeclared variable error and stopped the page from even loading further. (I easily fixed this by changing it to for(var i=0;... which seems kind of picky to me, but okay.) I was told here previously that the errors may come from Firefox, and are simply displayed by Firebug, but still I don't understand why Mac vs. PC would differ that way. Anyway, that's fairly trivial. Sorry for running on so long. Finally, here are two more of the weird Warnings I'm getting with my own devel pages when clicked with the Firebug Inspect tool, with the Warnings console button enabled -- sometimes the same few warnings repeated hundreds of times per page, filling up the whole Firebug console, such as: Cannot specify value for internal property. Error in parsing value for 'border-left-color-rtl-source'. Declaration dropped. physical Cannot specify value for internal property. Error in parsing value for 'border-left-color-value'. Declaration dropped. -moz-use-text-color ...and so on. All other addons disabled; doesn't look related to my source code; happens only on Mac, not on PC. Any idea what's causing that? Thanks much for your patience, Jonas -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/CAJ-Ow5D4Dt4uAubh445AMLBaYUuE%2Bw14MiH28Je7-vJZZUPZ2Q%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
