Is there a way to get the same type of JavaScript decompressor as present in Google Chrome? I know there is a plugin for this but it doesn't do the most important: when you decompress the JavaScript, the console file:line details match the decompressed code. So you can click to jump to legible JavaScript when debugging.
Firefox Developer Tools – Editable box model, Sublime Text keys
91–100 of 118 posts
Re: Firefox Developer Tools – Editable box model, Sublime Text keys
#92Earlier 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'm a long time Firefox fan, but very recently I played for the first time with IE 11 memory profiler and I must say, this is the best profiler out there.
How well does the Linux port perform?
Re: Firefox Developer Tools – Editable box model, Sublime Text keys
#93Earlier quoted context omitted.
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?
"In design terminology, ‘chrome’ refers to the non-webpage parts of the browser’s interface – the toolbars, tabs and buttons – because our design philosophy was “Content, not chrome” – putting our focus on minimizing the amount of browser UI present, we felt it cheekily appropriate to name the browser Chrome"
Re: Firefox Developer Tools – Editable box model, Sublime Text keys
#94Would be nice if there was a sane way to take a screenshot.
https://bbs.archlinux.org/viewtopic.php?pid=1412466
Re: Firefox Developer Tools – Editable box model, Sublime Text keys
#95The only thing left in my wish list is the abililty to edit JS code on a website live and compile it. Chrome has that but Firefox still doesn't have it yet.
Re: Firefox Developer Tools – Editable box model, Sublime Text keys
#96Earlier 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…
In Chrome, you could Snippets[1] or Live Editing[2] to monkey-patch Javascript sources inline. No need to copy & modify the content - just edit it within the browser and re-run. Complete with syntax highlighting, auto-completion, and the same no-reload goodness you are used to.
[1] https://developers.google.com/chrome-developer-tools/docs/au...
[2] https://developers.google.com/chrome-developer-tools/docs/au...
Re: Firefox Developer Tools – Editable box model, Sublime Text keys
#97Re: Firefox Developer Tools – Editable box model, Sublime Text keys
#98Earlier quoted context omitted.
I'll use chrome devtools the day they add multiline console support. Really? In 2014, and you want me to shift-enter 200 lines of code?
Why are you putting 200 lines of code into the console?
Because some of us experienced live coding back in the day, and Chrome Dev Tools kind of feels the same way?
Re: Firefox Developer Tools – Editable box model, Sublime Text keys
#99Earlier quoted context omitted.
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…
In Chrome, you could Snippets[1] or Live Editing[2] to monkey-patch Javascript sources inline. No need to copy & modify the content - just edit it within the browser and re-run. Complete with syntax highlighting, auto-completion, and the same no-reload goodness you are used to. [1] https://developers.google.com/chrome-developer-tools/docs/au... [2] https://developers.google.com/chrome-developer-tools/docs/au...
I never would have found snippits without it being pointed out to me. Thank you, that seems to be basically what I was looking for. Thought why it is there, and not just a multi-line console confounds me. Then again, so do most of Google's UI decisions for the last ~2 years or so.
Re: Firefox Developer Tools – Editable box model, Sublime Text keys
#100Earlier 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 still think Firebug + WebDevelopmentToolbar + FF Web Dev Tools is the greatest combo for any browser.
Do I need to do any web dev work? Just do it in firebug.
Do I need to drastically change my browser's behaviour? There's probably a setting for that in the web dev toolbar.
Do I want to do anything that involves monitoring or changing the browser itself? check the FF web dev tools.
Between the three, I don't understand how people can claim chrome has a superior toolset.