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

101–110 of 118 posts

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

#101

Post by kyriakos »

DatBear wrote: post #42
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…

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?

I am still using firebug. Even though performance is not great i find its console and dom inspection to be better than chrome's and mozilla's

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

#102

Post by hibbelig »

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?

It's great to see humor from MS.

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

#103

Post by tbassetto »

mrspeaker wrote: post #51
enscr wrote: post #14

The editable box model & color picker are very useful. I wonder if the editor would one day catch up so that you do your development in the browser itself.

I made my first contribution to Firefox the other day... I downloaded the source on a whim, realised I could build and run it - so went to the bug tracker. There was a bug with the box model editor that if the labels were long (such as "auto") then they would overlap the borders. I made it so long labels will rotate 90 degrees (try it out, change the outside margin to "auto"). I'm pretty stoked that some code I wrote…

Any chance of getting the bug ID? I am genuinely curious about the the changes made and the review process for such a bug :)

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

#104

Post by warcode »

pekk wrote: post #82
kijin wrote: post #80

Earlier quoted context omitted.

I'm tired of hearing that argument. Chromium !== Chrome. Call me back when Chromium, not Chrome, wins a 20% share of the browser market.

It's an essentially identical browser. The main difference is the branding it ships with. The experience is very much the same.

Sadly, Chromium on windows has been nothing but an unstable mess for me.

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

#105

Post by aleem »

I tried Firefox debugger yesterday when one of the ads on one of the sites I managed somehow created a rogue redirect. The ad cached the redirect response in the browser, so on subsequent requests the browser continued to redirect without making a trip to the server. We happened to catch the error on FireFox on one of the machines and attempted to debug it there.

The first problem was that the requests never showed up in the network tab. I typed in the URL with the network tab set to persistent and hoped that I would see the redirect response header in the network tab. But it never showed up. It loaded directly from cache I presume but it should still have showed up in the network tab or somewhere to allow debugging.

I looked into the cache next and saw that the cached copy of the page contained a single script loading code (I presume this was what got cached for the page). Copying the HMTL from the cache page was fairly annoying. You can't copy the entire text because it's setup as HEX+HTML side-by-side. The HTML version replaces spaces with dots which means you pretty much can't copy it.

Lastly, it would also be nice to prevent the developer tools from closing when a window self closes.

Also, it would be nice to be able to manage cookies in the developer tools.

Another thing I find annoying is that FF/Chrome both don't have a cookie debugger. There are plenty of add-ons but I am not sure why it's not part of the core developer tools. Would be nice to have.

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

#106

Post by quarterto »

mnemonik wrote: post #56
quarterto wrote: post #53

Earlier quoted context omitted.

Don't have a minimal test case yet, I'm seeing it happen on a page with >150 files bundled into a single file with a base64 data URI source map. If the debugger is open on page load, it hangs for 30 seconds to a minute, but loads practically instantly if I open the debugger after page load. Is there an existing bug I can chime in on or should I report a new one?

New one, please: https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&c... I understand if your app is proprietary and you can't share the source, but even non-minimal test cases are much better than no test case :) Thanks!

https://bugzilla.mozilla.org/show_bug.cgi?id=1007565

Outside of my 10kloc app, I could only reproduce it with ~100 copies of jQuery, which is kind of a pathological case I guess.

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

#107

Post by sergiosgc »

dubcanada wrote: post #58
givan wrote: post #8

Earlier quoted context omitted.

Firebug is still unbeatable, chrome dev has a lot to catch up.

I can't stand firebug, the UI is a complete turn off for me. The Chrome dev tools (any any webkit for that matter) just look and function better for what I spend 99% of my time in dev tools doing, tweaking CSS.

It must be a matter of preference, because I can't stand chrome dev tools' ui. Small buttons, cluttered, null use of breathing space in the design.

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

#108

Post by tyilo »

dubcanada wrote: post #58
givan wrote: post #8

Earlier quoted context omitted.

Firebug is still unbeatable, chrome dev has a lot to catch up.

I can't stand firebug, the UI is a complete turn off for me. The Chrome dev tools (any any webkit for that matter) just look and function better for what I spend 99% of my time in dev tools doing, tweaking CSS.

I 100% agree with you. I don't care how good the functionality of firebug is.

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

#109

Post by blueveek »

tbassetto wrote: post #103
mrspeaker wrote: post #51

Earlier quoted context omitted.

I made my first contribution to Firefox the other day... I downloaded the source on a whim, realised I could build and run it - so went to the bug tracker. There was a bug with the box model editor that if the labels were long (such as "auto") then they would overlap the borders. I made it so long labels will rotate 90 degrees (try it out, change the outside margin to "auto"). I'm pretty stoked that some code I wrote…

Any chance of getting the bug ID? I am genuinely curious about the the changes made and the review process for such a bug :)

https://bugzilla.mozilla.org/show_bug.cgi?id=986471

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

#110

Post by conradfr »

fournm wrote: post #37
johnward wrote: post #19

Earlier quoted context omitted.

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?

I believe Mozilla does manage Firebug, but the reason it isn't integrated as the main set of tools has to do with Firebug being much slower on complex pages?

Ironically I don't get console log in Firebug anymore since FF 29 (conflicts with other plugins it seems ?), so that forces me to use the dev tools.
Post reply on HN