5 ms·
Is it yet worth trying to make the shift from all-Firebug to all-FF-Dev-Tools? I hate having two sets of tools to do one job..
by oneandoneis2 13y ago
Is it yet worth trying to make the shift from all-Firebug to all-FF-Dev-Tools? I hate having two sets of tools to do one job..
- amarsahinovic 13y agoThere are two things that annoy me in FF Dev tools for now: - It uses RGB to show colors instead of hex (I think they are working on this) - There is no visual indication of margin/padding for the selected element on the page (it is shown in a box inside dev tools)
- heycam 13y agoYeah, I just started today on adding the ability (internally) for style declarations to expose colours in the syntax they were originally specified in (bug 731271), which the dev tools people will then be able to use.
- jlmendezbonini 13y agoFor the RGB issue see https://bugzilla.mozilla.org/show_bug.cgi?id=775135 https://bugzilla.mozilla.org/show_bug.cgi?id=775135 tl;dr: The bug is on hold until a Mozilla employee comes back from vacations.
- bzbarsky 13y agoThough to be fair nothing is stopping someone else from stepping up and doing the work. It's just on hold from the point of view of full-time employees on the devtools team until then...
- ionelm 13y agoYou can't customize shortcuts, the default ones are pretty bad - forcing you to use two hands to operate the inspector (on qwerty layout at least). I've given up completely on Firefox as a developer's browser ... Chrome's dev tools are better, faster - they don't crash your browser or make it unusable like Firebug.