Oh look, a bunch of updates to catch up to Chrome's tools again .
I know what I'd choose.
31–40 of 118 posts
Oh look, a bunch of updates to catch up to Chrome's tools again .
I know what I'd choose.
Earlier quoted context omitted.
Sounds like your windows copy of firefox might be the main release channel. The numeric status codes have been in since 30 (currently Beta). You can hop on Aurora (or Beta, or Nightly, but Aurora is generally best for web devs), or just wait about 6 weeks for the next uplift. https://bugzilla.mozilla.org/show_bug.cgi?id=972054
Is there an Ubuntu repo for Aurora that I'm missing or do I need to use the tarball.
Earlier quoted context omitted.
my peeves (in order of annoyance, desc): - inspecting ajax responses in console without flipping to net panel, then hunting for the correct request. - keeping an inspected/selected html element highlighted on page, not just on mouseover so you can see element bounds. this is useful for tweaking sizing, padding, margins and position. - as-i-type updating of html rather than on blur - live highlighting html as it chang…
You can enable logging XMLHttpRequests in dev tools settings (gears icon on bottom-right edge) -> console
Wow, I'm really impressed with the strides Mozilla has been making on this front. Chrome has long had the best dev tools and is one of the reasons I hardly ever use Firefox anymore. Once these updates land it may be on par or even better. Excited to see true competition on the dev side of things now.
Fucking unacceptable.
Earlier quoted context omitted.
Long time ago I used Firebug. What do you see is better in Firebug than Chrome Devtools?
I think the chrome devs did a good job of incorporating the best firebug features. The things that I find better in Firebug are mostly add-ons. For example I work with xpath a lot so firepath work awesome and ties into firebug seamlessly. I haven't found a tool that works as well on chrome. I also wonder why Mozilla didn't attempt to acquire firebug instead of building their own tools from scratch?
Looks cool. Still waiting for the localStorage inspector. I don't know how one can live without it..
Earlier quoted context omitted.
Long time ago I used Firebug. What do you see is better in Firebug than Chrome Devtools?
my peeves (in order of annoyance, desc): - inspecting ajax responses in console without flipping to net panel, then hunting for the correct request. - keeping an inspected/selected html element highlighted on page, not just on mouseover so you can see element bounds. this is useful for tweaking sizing, padding, margins and position. - as-i-type updating of html rather than on blur - live highlighting html as it chang…
Shift-enter in the Chrome console creates a newline rather than executing.
> live highlighting html as it changes
In the Rendering tab (bottom panel) there's a toggle for "Show paint rectangles" which sounds like its close (but not quite the same) as what you're looking for.
Wow, I'm really impressed with the strides Mozilla has been making on this front. Chrome has long had the best dev tools and is one of the reasons I hardly ever use Firefox anymore. Once these updates land it may be on par or even better. Excited to see true competition on the dev side of things now.
Same here. I still feel Firefox devtools are not innovating fast enough. Chrome workspaces and a lot of other useful features are just not present in Firefox. I feel that's one of the major reason I could never migrated to Firefox professionally. I am also quite impressed with IE 10 & 11 devtools. It is really useful and has clean UI and UX. In short I could say that: Chrome Devtools > Firebug > IE devtools > Firefox…
Maybe it's just me but I find this annoying, feels a little unprofessional.