ship this and I'll bury Chrome! (Well, Chromium)
Was this a reference to RA2's taunt "We will bury them!" ?
Which itself must be a reference to Nikita Khrushchev's famous outburst[1].
Future of Firefox DevTools
71–80 of 170 posts
Re: Future of Firefox DevTools
#72How about opening up a browser-based API for existing in-browser IDE-like environments to leverage the debugging tools that are already present? What I am talking about is instead of recreating jsFiddle in the dev tools, how about letting jsFiddle (with appropriate user confirmation) control the dev tools? As the creator of Plunker ( http://beta.plnkr.co/edit/e5iLyQ?p=preview ), I would love to be able to leverage th…
Isn't the first paragraph exactly about that?
Re: Future of Firefox DevTools
#73I've recently changed back over to Mozilla, this just proves that it was the correct decision.
I'm not quite sure if a mockup proves anything, unless you mean the part about them asking the community.
I think it is proof of quite a few things.
It proves that they are developing functionality that I've been looking for and some I didn't even know I wanted.
It is evidence that they want to be a great tool for developers and that they recognize their tool needs work.
It proves that I made the right decision (completely subjective which is the nature of a comment like the one I made) in moving away from Google for a more user centered and open-source browser.
And yes it proves that they listen to their users.
All of that is assuming they weren't lying or creating fake mockups (which I feel is a safe bet). Sure that's not a lot of proof for a scientific theory, but for a decision on which browser I want to use and which company I want to support I think it's proof enough :-)
Re: Future of Firefox DevTools
#74At 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. :)
Re: Future of Firefox DevTools
#75The #1 thing the Firefox DevTools group should be doing is integrating Firebug into Firefox. Right now they have the same team maintaining two codebases. That seems like a significant waste of time.
Re: Future of Firefox DevTools
#76How about opening up a browser-based API for existing in-browser IDE-like environments to leverage the debugging tools that are already present? What I am talking about is instead of recreating jsFiddle in the dev tools, how about letting jsFiddle (with appropriate user confirmation) control the dev tools? As the creator of Plunker ( http://beta.plnkr.co/edit/e5iLyQ?p=preview ), I would love to be able to leverage th…
Isn't the first paragraph exactly about that?
Hi Paul,
What I understood from your article is that you're mostly exploring 1) the possibility of opening up the dev tools to locally-installed applications like SublimeText2; and 2) the integration of jsFiddle-like apps within DevTools.
Please correct me if I misunderstood.
What I'm asking about is creating an in-browser API for a website to interact with the dev tools. Obviously, this would require a very thorough review of the risks of having such an API from a security perspective (and how users can opt-in in a transparent and well-controlled manner). That being said, I am still hoping!
If this is already in the books, then Hooray! I can't wait to start experimenting.
I hope I didn't come across poorly, because I really appreciate all the work you've been doing!
Re: Future of Firefox DevTools
#77The #1 thing the Firefox DevTools group should be doing is integrating Firebug into Firefox. Right now they have the same team maintaining two codebases. That seems like a significant waste of time.
I kind of disagree, I would rather see Firefox DevTools not be Firebug. Firebug is not that great (compared to Chrome's debug tools) due to its UI. It looks like Firefox DevTools is at least going for a much better UI, so being constrained by Firebug would be a loss.
Re: Future of Firefox DevTools
#78Earlier quoted context omitted.
Isn't the first paragraph exactly about that?
Hi Paul, What I understood from your article is that you're mostly exploring 1) the possibility of opening up the dev tools to locally-installed applications like SublimeText2; and 2) the integration of jsFiddle-like apps within DevTools. Please correct me if I misunderstood. What I'm asking about is creating an in-browser API for a website to interact with the dev tools. Obviously, this would require a very thorough…
So - Firefox exposes a tcp-based protocol (not enabled by default. The user will need to go to a special tool to start the server). It will expose feature like adding break points, exploring the DOM and the CSS rules, and editing content (CSS/HTML/JS).
So external tools can connect to Firefox. But this protocol is not accessible from a page. But we could imagine using a websocket instead of a normal tcp socket, and let the web page connect to ws://localhost.
Re: Future of Firefox DevTools
#79"Control browser from Editor" > "Edit in the Browser". Think about it - everyone prefers a different editor.
That is why the decision has not been made yet, they are discussing. Every user has different preferences, and maybe you will get to have both the options :)
Re: Future of Firefox DevTools
#80While the number 1 suggestion sounds great on paper, isn't anyone else concerned about the security implications? The ability for the browser to modify files directly on my workstation outside of caching folders sounds like a recipe for disaster.
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.