Future of Firefox DevTools • Hacker News Board

Re: Future of Firefox DevTools

#161

Post by past » Wed, Mar 20, 2013, 10:01 AM UTC

purephase wrote: post #80

nsmartt wrote: post #64

Earlier quoted context omitted.

He had to click accept connection before it allowed him to edit the CSS.

Which, as we know, is a rock-solid protection mechanism against these types of exploits. Everyone reads modal messages.

In order to get to that modal message, you first have to go and enable remote debugging, which is not something normal people would do. And in general, even though we can (and already have) come up with even more mitigations for the potential threat, the sad truth is that security and usability are fundamentally a tradeoff, so you have to strike a balance at some point.

Re: Future of Firefox DevTools

#162

Post by past » Wed, Mar 20, 2013, 10:07 AM UTC

leeoniya wrote: post #40

Are there any plans to implement an instrumenting profiler in addition to the existing one? Not having call count is a huge minus for me. Devtools has a sampling profiler like Chrome (which also doesnt provide call counts). So the only instrumenting profilers remaining for JS on Windows are Firebug and an outdated, abandoned version of Safari :(

The profiler has a stackwalking mode that provides more accurate info:

https://developer.mozilla.org/en-US/docs/Performance/Profili...

You would need to use a nightly release to get that though, and only on the platforms that are currently supported.

Re: Future of Firefox DevTools

#163

Post by mcepl » Wed, Mar 20, 2013, 10:12 AM UTC

smnrchrds wrote: post #74

quaunaut wrote: post #9

At the moment, I really like Chrome because I just find the behavior of the Omnibar superior to Firefox's Awesomebar. But hot damn, you're making me question loyalties on my dev machine.

I removed search box from Firefox few months ago and never looked back. I use search engine keywords instead[1]. My current keywords include goog, bing, amzn, crate, and wiki. Guess what search engine they refer to. :) [1] http://kb.mozillazine.org/Using_keyword_searches

+1 ... except that gg is a keyword for DuckDuckGo. I just couldn't switch my finger memory from gg, so I rather switched the alias ;)

Re: Future of Firefox DevTools

#164

Post by mcepl » Wed, Mar 20, 2013, 10:14 AM UTC

And one more for the Chrome "Resources" tab. I am now trying to develop FFOS app with IndexedDB and not being able to see the content of the database makes me run to Chrome all the time.

Re: Future of Firefox DevTools

#165

Post by past » Wed, Mar 20, 2013, 10:16 AM UTC

visarga wrote: post #150

The main problem for me is the narrow format of the dev tools. I can't see the web page well and I can't see the debugger well. Docking to the right side is also bad, because it reduces my width and makes the page display badly. I fondly remember the debugger I used to have in Borland Pascal 7 under MSDOS. Concise and efficient.

You can detach the developer tools window and put it anywhere you like.

Re: Future of Firefox DevTools

#166

Post by past » Wed, Mar 20, 2013, 10:23 AM UTC

ricardobeat wrote: post #68

bmuon wrote: post #63

Making Firebug into an extension that works inside the Firefox dev tools (the same way Firebug plugins can add tabs) sounds like the best way to move forward both Firefox and Firebug.

Why? I say leave Firebug alone, or just kill it already? We don't need two inspectors.

Mozilla can't kill Firebug, even if they wanted, since it's a separate open source project and community. And the only people with two inspectors would be those that elected to have them both, by installing Firebug and using both tools.

Re: Future of Firefox DevTools

#167

Post by past » Wed, Mar 20, 2013, 10:31 AM UTC

boundlessdreamz wrote: post #42

The timeline needs to show protocol. Btw this already exists in Firebug. Why duplicate effort? I'm sure this hass been asked before. But why have devtools instead of improving firebug? (Performance?) What will happen to firebug in the long run ? Edit: * In inspect view, can we have a search HTML function like firebug? * Also in inspect view, a way to disable the display of PATH. * Increase the font size of html/css r…

The inspector has a search box in Firefox 21 and above.

Re: Future of Firefox DevTools

#168

Post by past » Wed, Mar 20, 2013, 10:34 AM UTC

existentialmutt wrote: post #69

Very excited to see the network panel, as that is what makes me go back to Chrome or Firebug most often. In the network panel, being able to sorting/filter requests by content-type, request verb, and response code makes it much more usable for me. I didn't see that in the video-- do you plan to include it?

Sorting and filtering are planned, yes.

Re: Future of Firefox DevTools

#169

Post by path411 » Wed, Mar 20, 2013, 10:37 PM UTC

As someone who's loving TypeScript, is it a possibility we will see that supported too?

Re: Future of Firefox DevTools

#170

Post by purephase » Thu, Mar 21, 2013, 9:04 PM UTC

past wrote: post #161

purephase wrote: post #80

Earlier quoted context omitted.

Which, as we know, is a rock-solid protection mechanism against these types of exploits. Everyone reads modal messages.

In order to get to that modal message, you first have to go and enable remote debugging, which is not something normal people would do. And in general, even though we can (and already have) come up with even more mitigations for the potential threat, the sad truth is that security and usability are fundamentally a tradeoff, so you have to strike a balance at some point.

And, I understand that. But, the drawbacks of the security implications of your development/developer browsers being thus weakened is, IMO, a decision heavily weighted in favour _against_ this feature.

Personally, I would love it. It would make my life easier to have a full IDE within a browser. However, I would never be comfortable with the security tradeoff and would never enable it.