In the comments so far, there seems to be some confusion on what this is. The Chrome Sidebar API is an API for Chrome extensions, adding a sidebar surface to Chrome.
The proposed API allows Chrome extensions to access and control a sidebar panel - a per-tab split-pane HTML container to the right (to the left in RTL environment) of the main page content with the ability to resize horizontally.[1]
In short, it provides extensions an alternative to using popups or injecting HTML directly into web pages in order to display something to the user.
With it, you could for instance (re-)implement something like the old Side Tabs feature, which was removed from Chrome because the complexity of a tree-style interface in terms of usage is beyond what most users need or want, and in terms of implementation is more than passes the cost/benefit test for building into Chrome natively as an option.[2]
We had a sidebar extension on Chrome called Teamgum[1]. But it was removed from store last month because we were using remote iframes. And when we asked for more explanation nothing from their end. And now I see they are developing there own sidebar.
If successful, it will be interesting to see how Chrome evolves for developers to compete.
(I was reminded of this because the Firefox sidebar was always wildly popular - I know lots of people that continue to use it specifically for that purpose)
I use Firefox by default with an add-on 'Vertical Tabs'. This moves all tabs away from the top into a narrow sidebar.
Screens are more wide then tall and for me my vertical space is more valuable. Every line that holds only static info (address bar, open tabs) is not strictly needed at all times, so I want them either to popup (like the menu bar in full screen view) or at least move to the sides ('cheaper' space).
I am somewhat surprised this is not more common opinion.
It's that whole 80/20 thing. Most features of products go unused. So Chrome has finally reached a level of maturity where it can concentrate on rarely used features.
> It's funny to see they're going to release one now that nobody cares about it.
But that's because up until now we couldn't care about it anyway if Chrome didn't support it. Sidebars can easily make a comeback if the functionality proves to be useful, and I can picture many extension developers experimenting with it if it's made available.
Finally! Our customers have been begging us to provide this for years. We build "Employee Engagement" (aka gamification) tools that extend various CRMs. Not all of them support a way to extend the UI but a sidebar would be perfect.
Looks good, now they need a way to hide the existing tabs (and perhaps the addressbar too) and we can move to a nice slick side-tabs extension for Chrome.
Does anyone know how Honey [1] implemented a sidebar like UI in their chrome extension? It seems pretty solid and I wonder how they got around the current limitations against Sidebars in chrome extensions.
I've been working on a graphical command-line for manipulating webpages with natural language queries (https://contextscript.com). So far I've been using a bookmarklet, which has the benefit of working across browsers, but it has a lot of drawbacks too. If I go the browser extension route, this looks like it would be very useful for developing the UI.
I'm currently working on creating a sidebar app similar to Honey's UI [1]. Have you made any progress implementing the sidebar look? It doesn't seem very documented and even Honey seems to do it in a hacky way.
I remember all the fuss that was made about a sidebar in Windows (was it in Vista?) At the end of the day its just a souped up menu in a different position.
If the user installs an extension that delivers ads, then perhaps it is the user's intention to receive ads? Barring some kind of exploit, this won't be something that a website can do to you.
[+] [-] ohaal|10 years ago|reply
The proposed API allows Chrome extensions to access and control a sidebar panel - a per-tab split-pane HTML container to the right (to the left in RTL environment) of the main page content with the ability to resize horizontally.[1]
In short, it provides extensions an alternative to using popups or injecting HTML directly into web pages in order to display something to the user.
With it, you could for instance (re-)implement something like the old Side Tabs feature, which was removed from Chrome because the complexity of a tree-style interface in terms of usage is beyond what most users need or want, and in terms of implementation is more than passes the cost/benefit test for building into Chrome natively as an option.[2]
[1]: https://docs.google.com/document/d/102hfWTM5cMl-95PyfGcn89YH...
[2]: https://code.google.com/p/chromium/issues/detail?id=344870#c...
[+] [-] smurfpandey|10 years ago|reply
[1]: http://www.teamgum.com
[+] [-] bhilburn|10 years ago|reply
It looks like Mozilla is making a new push with Firefox, as well, to attract devs back: http://arstechnica.com/information-technology/2015/07/big-ch...
If successful, it will be interesting to see how Chrome evolves for developers to compete.
(I was reminded of this because the Firefox sidebar was always wildly popular - I know lots of people that continue to use it specifically for that purpose)
[+] [-] eloisant|10 years ago|reply
The response was that a popup that appears when you click a toolbar button was enough.
It's funny to see they're going to release one now that nobody cares about it.
[+] [-] Gys|10 years ago|reply
Screens are more wide then tall and for me my vertical space is more valuable. Every line that holds only static info (address bar, open tabs) is not strictly needed at all times, so I want them either to popup (like the menu bar in full screen view) or at least move to the sides ('cheaper' space).
I am somewhat surprised this is not more common opinion.
[+] [-] ionforce|10 years ago|reply
[+] [-] Mahn|10 years ago|reply
But that's because up until now we couldn't care about it anyway if Chrome didn't support it. Sidebars can easily make a comeback if the functionality proves to be useful, and I can picture many extension developers experimenting with it if it's made available.
[+] [-] digi_owl|10 years ago|reply
[+] [-] Kartificial|10 years ago|reply
"Does this API expose any functionality to the web?"
"No"
[+] [-] amk_|10 years ago|reply
Vivaldi, basically a modernized Opera 11/12, has supported some sidebar elements from the beginning.
Since Opera and Vivaldi are both Chromium-based, it's not surprising to see sidebars getting into upstream.
[+] [-] username3|10 years ago|reply
[+] [-] kuschku|10 years ago|reply
Another idea is vertical tabs.
[+] [-] vyrotek|10 years ago|reply
[+] [-] iolothebard|10 years ago|reply
[+] [-] 7952|10 years ago|reply
[+] [-] wooger|10 years ago|reply
[+] [-] aarohmankad|10 years ago|reply
[1]: https://chrome.google.com/webstore/detail/honey/bmnlcjabgnpn...
[+] [-] highwind|10 years ago|reply
[+] [-] nathanathan|10 years ago|reply
[+] [-] nathan_f77|10 years ago|reply
[+] [-] aarohmankad|10 years ago|reply
[1]: https://chrome.google.com/webstore/detail/honey/bmnlcjabgnpn...
[+] [-] iansilber|10 years ago|reply
[+] [-] spdustin|10 years ago|reply
[+] [-] jebblue|10 years ago|reply
https://msdn.microsoft.com/en-us/library/windows/desktop/cc1...
[+] [-] shwetank|10 years ago|reply
[+] [-] ushi|10 years ago|reply
[0] https://github.com/buunguyen/octotree
[+] [-] hmhrex|10 years ago|reply
[+] [-] collyw|10 years ago|reply
[+] [-] ThomPete|10 years ago|reply
I have been waiting for this for a long long time.
[+] [-] dragthor|10 years ago|reply
[+] [-] jessaustin|10 years ago|reply
[+] [-] ytdht|10 years ago|reply
[+] [-] curiousjorge|10 years ago|reply