Earlier quoted context omitted.
Why are you putting 200 lines of code into the console?
I have to say, I stared at this question for a while. I have such a large reliance on using the console as a scratchpad, before ever even opening a script file, that I don't think I've even considered the possibility that one could do front end development work without it. The best answer for you question, would be that throughout my career, the number of situations where I could directly edit a source javascript fil…
Firefox Developer Tools – Editable box model, Sublime Text keys
111–118 of 118 posts
Re: Firefox Developer Tools – Editable box model, Sublime Text keys
#112Every example of dev tools have their pluses and minuses, but all of them are great in their own way.
Everybody has their favorite for whatever specific reasons they have which is usually based off their individual workflow.
One developer's useless dev tools is another's life saver.
Too many people latch onto one way of doing things and don't experiment that much to see what's going on in another tool set.
Give Firefox/Chrome/Firebug dev tools a try. If it works out great! If it doesn't, well that's great too because you still have what you were happy with before.
I just try to forget the dark days before Firebug.
Re: Firefox Developer Tools – Editable box model, Sublime Text keys
#113Would be nice if there was a sane way to take a screenshot. https://bbs.archlinux.org/viewtopic.php?pid=1412466
Developer toolbar 'screenshot' command: http://www.ghacks.net/2012/11/02/take-screenshots-straight-f... | https://developer.mozilla.org/en-US/docs/Tools/GCLI#Commands
Re: Firefox Developer Tools – Editable box model, Sublime Text keys
#114Earlier quoted context omitted.
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
#115I 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 u…
Re: Firefox Developer Tools – Editable box model, Sublime Text keys
#116Earlier quoted context omitted.
Why are you putting 200 lines of code into the console?
I have to say, I stared at this question for a while. I have such a large reliance on using the console as a scratchpad, before ever even opening a script file, that I don't think I've even considered the possibility that one could do front end development work without it. The best answer for you question, would be that throughout my career, the number of situations where I could directly edit a source javascript fil…
Re: Firefox Developer Tools – Editable box model, Sublime Text keys
#117I 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 u…
What sort of cookie debugging? Seeing the cookies being sent for each request in the Network panel isn't enough?
Re: Firefox Developer Tools – Editable box model, Sublime Text keys
#118Just installed it from Aurora channel. I have not used firefox for couple years now (moved to Chrome) but I think I will jump back now. The only thing in dev tools missing so far for me compared to Chrome is :before and :after pseudo elements, I love how Chrome dev tools shows it as a separate entity in the inspector tree. I hope FF team implements it as well.
Firebug gives you the option to toggle all pseudo states for an element and edit its CSS. IMO Firebug and Chrome's dev tools still lag behind Firebug's.