See the history as a tree, not as a list, so branch points can be preserved and you can navigate back over everywhere you've already been.
A detailed development roadmap.
Privileged browser Apps and Extensions working on mobile. C'mon, it's 2015! ( no PhoneGap required )
An automation API.
The same really committed team who optimized V8.
Source on GitHub ( not necessarily all of it mind, some can be privileged access, tho a place to post issues that is no more code.google or crbugs, just, why? ).
For an automation API, would the RemoteDebug APIs³ work, or perhaps the command-line⁴ API for Firefox? See node-firefox⁵ for an example of using the RemoteDebug API to automate some functions in Firefox.
What makes you perceive the V8 team as more committed than other teams?
You can use your GitHub login to sign in to Mozilla's Bugzilla⁶, is that not enough of an integration for you?
I watched a couple of video presentations V8 did about optimization. It was really coherent. And their skills were really advanced. Also, visceral experience of the speed and stability of Chrome.
Also visceral experience deving Chrome apps and extensions ( man, I love their clear APIs ) versus doing the same in Moz with XUL ( omg, die ).
Browsers are as much about branding as anything, and I'm never going to come to the Mozilla camp. I don't believe a browser works to be a political cause, nor do I believe Mozilla is anything like the narrative they have about it. I mean what the hell is the committee of the Mozilla foundation doing? Wasting time with meetings about the grandiose purpose as a "movement", instead of making a better browser.
They pretend they're so "righteous" and yet all that pedantic dogmatic nitpicking and differentiating themselves is actually costing a lot of efficiency, which doesn't work for people who browse or for people who code.
Aside from that, I like the way Chrome does JS, and I don't like the way Moz does. Custom Elements, c'mon!
The masses have voted anyway. Chrome FTW.
Your answer was clear, it just seems we're on different sides of the browser divide. I wonder why there's so much loyalty? The browser is such an important piece of software.
A dev roadmap is just a general program requirement. Not specific to web browsers but good.
And you're right about mobile and extensions. There's no need to restrict when you don't have to! For a web browser on iOS, sadly you have to use Apple's engine but that's workable with js injection for extensions. And of course on Android there's no problem. I like that iOS is opening a little (I have an iPhone) but I wish it was more open like android, that way jail breaking would not be required for a lot of features. The one good thing now is that they're letting you side load apps from source with Xcode 7 without paying, but it's some michigas to go through. Mobile platforms are weird.
This may be not exactly what you are looking for but there is a session management tool for firefox. It allows you to save/restore the tabs (and their history) of a session.
For automation API you probably want a way to record actions and replay them like Excel macros? If you look for scriptable automation for Chrome then http://phantomjs.org/ might be a step in that direction.
A detailed development roadmap.
Privileged browser Apps and Extensions working on mobile. C'mon, it's 2015! ( no PhoneGap required )
An automation API.
The same really committed team who optimized V8.
Source on GitHub ( not necessarily all of it mind, some can be privileged access, tho a place to post issues that is no more code.google or crbugs, just, why? ).