Yes, that helps, thanks. [It would be interesting if the console counted displayed messages by category and suggested turning off a category if the display rate for that category got too high. It might be nice to display the category next to the message... I can't think of a technique to help the user better notice the pull down menu that can be used to turn off categories...]
On Tuesday, September 25, 2012 11:42:09 PM UTC-7, Jan Honza Odvarko wrote: > > It sounds like a CSS error. Try to open Console panel option menu > (click the little black triangle next to the tab title) and uncheck > "Show CSS Errors" > Does it help? > > Honza > > On Sep 26, 7:32 am, Illilillili <[email protected]> > wrote: > > https://getfirebug.com/errorsstates: > > """ > > When things go wrong, Firebug lets you know immediately and gives you > > detailed and useful information about the errors in JavaScript, CSS, and > > XML. > > """ > > > > I'm getting errors of the form " > > > > Error in parsing value for 'background-image'. Declaration dropped. > > " on this here google groups web page. Presumably this isn't an error > in Javascript, CSS, or XML. It certainly isn't detailed, and I'd argue it > isn't useful. I > > don't understand why firebug cannot point one to the offending source > code or DOM object that is casing the error. The > > interpreter can't provide a traceback showing where the error occured? > > > > Since these kinds of errors are useless to me, is there an easy way to > disable the display of of these types of errors so they don't swamp my more > useful logging? > -- 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 https://groups.google.com/forum/#!forum/firebug
