Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox Developer Tools – Editable box model, Sublime Text keys

hacks.mozilla.org

Post reply on HN
Print view View original

41–50 of 118 posts

Re: Firefox Developer Tools – Editable box model, Sublime Text keys

#41

Post by interurban »

cbaleanu wrote: post #40
mundanevoice wrote: post #9

Earlier quoted context omitted.

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…

The window title for IE 10&11 devtools is for some reason named "F12" on my windows 7 machine. Maybe it's just me but I find this annoying, feels a little unprofessional.

F12 is the default shortcut for opening the IE devtools, maybe that's why?

Re: Firefox Developer Tools – Editable box model, Sublime Text keys

#42

Post by DatBear »

mundanevoice wrote: post #9
james33 wrote: post #4

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…

I think that Firefox has lagged behind because of Firebug. When there is already a way for developers to do things, why invent your own, unless you can make it better?

Re: Firefox Developer Tools – Editable box model, Sublime Text keys

#43

Post by mbrubeck »

interurban wrote: post #41
cbaleanu wrote: post #40

Earlier quoted context omitted.

The window title for IE 10&11 devtools is for some reason named "F12" on my windows 7 machine. Maybe it's just me but I find this annoying, feels a little unprofessional.

F12 is the default shortcut for opening the IE devtools, maybe that's why?

Yup, the IE devtools are named "F12" after the keyboard shortcut:

http://msdn.microsoft.com/library/ie/bg182326%28v=vs.85%29

(F12 is also the keyboard shortcut for opening the developer tools in Chrome, Firefox, and others.)

Re: Firefox Developer Tools – Editable box model, Sublime Text keys

#44

Post by cbaleanu »

interurban wrote: post #41
cbaleanu wrote: post #40

Earlier quoted context omitted.

The window title for IE 10&11 devtools is for some reason named "F12" on my windows 7 machine. Maybe it's just me but I find this annoying, feels a little unprofessional.

F12 is the default shortcut for opening the IE devtools, maybe that's why?

By this reasoning 'paste' should be renamed to CTRL-V.

Re: Firefox Developer Tools – Editable box model, Sublime Text keys

#46

Post by mnemonik »

quarterto wrote: post #27

The main thing that drove me back to Chrome for web dev was the performance. Firefox would hang for ~30 seconds trying to load source maps for our 150+ modules. Since it's single-threaded, this locks up the entire UI every time our app loads with dev tools open. And if it pauses on an exception during this 30 seconds, good luck trying to do anything for the next five minutes.

We had some source map performance issues a while back, but I fixed all the ones that were reported. If you have a test case and steps to reproduce, I'd love to take a look :)

Re: Firefox Developer Tools – Editable box model, Sublime Text keys

#47

Post by clarkm »

leeoniya wrote: post #34
smalu wrote: post #24

Earlier quoted context omitted.

You can enable logging XMLHttpRequests in dev tools settings (gears icon on bottom-right edge) -> console

it's not at all useful. all you get is some stack-tace-like thing without any of what you actually want to see. like req/resp headers and body, params, inline json/html decoding based on response type. chrome lags here by a large margin.

Just click the request from the console, and it takes you to the network tab where you can see the headers, response, etc.

Re: Firefox Developer Tools – Editable box model, Sublime Text keys

#48

Post by sergiotapia »

quarterto wrote: post #27

The main thing that drove me back to Chrome for web dev was the performance. Firefox would hang for ~30 seconds trying to load source maps for our 150+ modules. Since it's single-threaded, this locks up the entire UI every time our app loads with dev tools open. And if it pauses on an exception during this 30 seconds, good luck trying to do anything for the next five minutes.

I had the same performance issues and the latest stable version of Firefox resolved every bit of slowness I was experiencing. The totally surprised me, it felt like a different browser.

Re: Firefox Developer Tools – Editable box model, Sublime Text keys

#49

Post by leeoniya »

thedufer wrote: post #39
leeoniya wrote: post #20

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…

> multiline console 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.

> Shift-enter in the Chrome console creates a newline rather than executing.

this is not only a major pain in the ass, but also much much worse than just having a persistent multiline editor window that keeps your code, cursor position and selection intact between executions.

there is simply no comparison here.

Re: Firefox Developer Tools – Editable box model, Sublime Text keys

#50

Post by skrebbel »

cbaleanu wrote: post #44
interurban wrote: post #41

Earlier quoted context omitted.

F12 is the default shortcut for opening the IE devtools, maybe that's why?

By this reasoning 'paste' should be renamed to CTRL-V.

So when Google calls a virtually chromeless browser "Chrome" it's ok, but when Micrsoft calls a tool after its shortcut key, it's stupid?
Post reply on HN