We'll probably remove that message and workaround in 1.12.7, but it's up to 
Honza. "Next major version" refers to that of Firebug, which will probably 
be out in a couple of months. It *will* have minVersion >= 29, but 
seriously, don't worry, Australis is quite okay, and there are addons that 
give you the old appearance back. Keeping with an up-to-date browser is 
important.

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.

Den lördagen den 22:e februari 2014 kl. 04:23:24 UTC+1 skrev Jonas:
>
> I've just upgraded Firefox from version 26 to version 27 on both my Mac 
> (running Snow Leopard, 10.6.8) and my Windows VM (Windows 7). I'm running 
> the latest version of Firebug on both. So far I've only been playing around 
> with the Mac version, which is where I mostly develop.
>
> The good news: everything seems snappier, even when using the Firebug 
> Scripts panel.
>
> The bad news: there's still that warning message showing up, "Warning: 
> Enabling the Script panel causes a Firefox slow-down due to a platform bug. 
> This will be fixed with the next major Firefox and Firebug versions."
>
> I thought that annoying warning would be gone, especially since it does 
> seem faster. Did the developers just neglect to remove the warning message, 
> or do they consider that the bug is still unfixed? If the latter, what 
> constitutes "the next major...versions"? I hope they don't mean Australis 
> (Firefox 29 or whatever it is) since I'm unlikely to _ever_ "upgrade" to 
> that.
>
> Another issue I'm seeing: when I load my pages with "All" errors enabled, 
> I'm seeing no errors anywhere. However, when I select the Firebug "Inspect 
> Element" tool and start clicking on things, errors appear. I don't see them 
> at first because clicking the tool takes me to the HTML panel, but as soon 
> as I come back to the Console, there are one or more errors that I'm pretty 
> sure have nothing to do with my code. For example, one error says:
>
> "! Cannot specify value for internal property. Error in parsing value for 
> "-x-system-font'. Declaration dropped."
>
> Looks like some kind of internal CSS error, but I don't even know what an 
> "x-system-font" is. There are also a whole bunch of "errors" that show up 
> intermittently that falsely claim to come from one of my external 
> JavaScript files that are linked in to that page -- but I'm pretty sure 
> actually have nothing to do with it. I don't think clicking anything with a 
> Firebug tool should itself cause an error.
>
> Any enlightenment concerning the "slowdown warning," and the new Console 
> errors, would be greatly appreciated. Thank you.
>

-- 
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/ab4164a2-b423-4d1d-b006-f23d69d0381a%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to