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.
