Thanks for the reply Sebastian. Yes, this is exactly what I am talking about. :)
Looking at the links, http://code.google.com/p/fbug/issues/detail?id=4829 in particular, this seems to be an on-going issue that needs addressing but sounds like adding a custom filter to Firebug is difficult to implement. The best solution, of course, would be better design community awareness. Someone with influence @ Firebug / Firefox could start the ball rolling I guess?? ( I was pleased to see yesterday that the new Bootstrap 3.0 alpha/wip has now dropped the -moz-border bit. Still has -moz-background bits though, which throw up errors. But 'work-in-progress') Turning off CSS errors will definitely help to reduce the console noise and one can always use the Webkit Inspector for general CSS errors. :) Only thing is, it doesn't help if you are actually trying to use Firebug to look for CSS errors in Firefox .... Bruce. On Tuesday, 2 April 2013 12:06:10 UTC+2, Sebastian Zartner wrote: > > I guess you're talking about the "Unknown property '-moz-border-radius'. > Declaration dropped." message and similar ones, right? > > For that case the simplest solution would be to uncheck the option *Show > CSS Errors*. > Besides that there are already some requests how to improve the filtering: > > - Issue 5653 <http://code.google.com/p/fbug/issues/detail?id=5653>: > Invert filtering search for Console panel > - Issue 4368 <http://code.google.com/p/fbug/issues/detail?id=4368>: > Allow to ignore specific log messages > - Issue 4829 <http://code.google.com/p/fbug/issues/detail?id=4829>: > Custom Filters for Net Panel (other panels?) > > Sebastian > > On Saturday, March 30, 2013 12:11:31 PM UTC+1, Bruce Miller wrote: >> >> A year is a long time in computing. The IE6 saga is now finished, IE10 >> has is making in-roads, Firefox is on version 19, Opera is moving to Webkit >> .... >> >> >> Unless there is a Firebug feature that I haven't yet discovered, I am >> left wondering if now is the time to do some tidying up: >> >> The problem I am facing is with Firebug (and the plain Firefox console >> (ctrl-shift-k)) throwing up so many errors and warnings which seem to be >> generated by code that has so rapidly become out-of-date. >> >> Yes, I could increase the log's 500 limit but I am wondering if some >> toggle-able filter settings might be a better route. This would make the >> console more usable and easier to see what is going on. >> >> >> Currently, I am trying to get my head around responsive CSS and JS and >> update my skill set. The mixins.less LessCSS 'module' used in Bootstrap >> for instance really causes Firebug to go into overload: >> >> <code> >> >> // CSS3 PROPERTIES >> // -------------------------------------------------- >> >> // Border Radius >> .border-radius(@radius) { >> -webkit-border-radius: @radius; >> -moz-border-radius: @radius; >> border-radius: @radius; >> } >> >> </code> >> >> Conversely, this is what I am reading at StackOverflow: >> http://stackoverflow.com/questions/14226224/css-border-radius-and-moz-border-radius/14226265#14226265 >> >> >> -- -- 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 --- 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]. For more options, visit https://groups.google.com/groups/opt_out.
