Taking advantage of Chrome-specific browser APIs is out of the question for mainline Web-Decker. Providing an enhanced experience in Chrome is equivalent to telling my users to switch to Chrome, and in turn encourages a browser monoculture, which I view as seriously harmful to the web.
Yep, fair enough - I empathize. I linked the spec later in the thread so you can keep an eye on it if it does actually get adopted by the other browsers.
Edit: also, to be clear, the 'push to origin' add-on I'm asking about in this thread for git etc is unrelated to this in terms of implementation, but I thought I'd mention it in case you weren't aware of it