On Sunday, February 23, 2014 3:52:21 AM UTC+1, Jonas wrote: > > > 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. > Instead of reading the statements of others and before judging it, you should try it out by yourself <http://nightly.mozilla.org/> and build your own opinion. Custom toolbars definitely still work. I verified that right now by installing Web Developer. It works totally fine for me. As Simon wrote only the Add-on bar was removed (see bug 749804<https://bugzilla.mozilla.org/show_bug.cgi?id=749804>), which I don't like neither (and already complained about at Mozilla like many other people), but at least there are add-ons like The Puzzle Piece<https://addons.mozilla.org/firefox/addon/the-puzzle-piece/>that bring it back. But again, that's off-topic and the Firebug Working Group has no influence on the redesign.
> 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. > Do you have *Show Chrome Errors*, *Show Chrome Messages* and *Strict Warnings (performance penalty)* unchecked? If not, please do so and try it again. > 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. > The option menu items control whether the messages are logged to the console at all while the filter buttons filter the messages after logging. Because I also think that the current UI is not perfect, I created issue 6357 <http://code.google.com/p/fbug/issues/detail?id=6357> and 6358<http://code.google.com/p/fbug/issues/detail?id=6358>as suggestions for improving it. > 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. > That's surely because you have the *Strict Warnings* option checked on your Windows machine. Just uncheck it and you should not see these messages anymore. Sebastian -- 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/c7400398-8bd3-483c-983d-bcda74b0c36a%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
