New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 51084 link

Starred by 473 users

Comments by non-members will not trigger notification emails to users who starred this issue.

Issue metadata

Status: Duplicate
Merged: issue 477424
Owner: ----
Closed: Aug 2015
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature

Restricted
  • Only users with EditIssue permission may comment.



Sign in to add a comment

Add sidebar surface for extensions

Project Member Reported by joi@chromium.org, Aug 3 2010

Issue description

Sidebar API proposal to follow.
 
Showing comments 6 - 105 of 105 Older

Comment 6 by joi@chromium.org, Aug 19 2010

CCing Aleksey so he can respond to comments made on this bug (including those above).

Note that Aleksey's API proposal document for this API has been posted at http://www.chromium.org/developers/design-documents/extensions/sidebar-extension-api and may answer some of the questions that have been asked here.

Making the API per tab was a compromise between designing the API to be more powerful vs. designing it to help ensure that the user's experience is as consistent and Chrome-like (i.e. fairly minimalistic) as possible.
@mats.ahlgren: I think the reason that is there is to allow extensions that only affect certain websites. For instance, an extension might want to display content when the user is on Wikipedia, but not on other sites.

It should still be possible to make global extensions work, it would just require you to show the sidebar on every tab, similar to how page actions work.


@Chrome team:
To clarify my previous point, Tree Style Tabs indents the tabs when they are children of the previous tab. Doing this indentation while the sidebar is on the right side looks weird (in my opinion) so having the sidebar on the left is important.

Also, what about things like the Web Inspector when it's docked? Will extension authors be able to place UI at the top or bottom of the page, rather than just the right side? That arguably should belong in the sidebar API.

Comment 8 by alekseys@google.com, Aug 19 2010

Sidebar UI layout and it's place in the browser window UI hierarchy implies "per tab" scope of its content and, as @pcxunlimited mentioned already, global content can be emulated by showing sidebar for every tab.

To keep Chrome UX consistent, sidebar is always displayed on the right side of the window, left side is reserved for the page content. For the same reason, as of now there are no plans to let extension authors to control sidebar placement.
I understand the point of consistency, but can you point to a single browser that displays the sidebar on the right side? Firefox, in particular, uses the left side for the sidebar, so placing it on the left would be more consistent with user's expectations.

Comment 10 Deleted

(@pcxunlimited: I actually prefer my tree-style tabs on the right side.)

But I predict a large number of users would be upset *whichever side* the bar was put on. If it would just take a few lines of code and a UI option to allow the user to switch the side, there doesn't seem anything wrong with that? Clean/minimalist need not mean unconfigurable.

I am not recommending anything except "this side is better because people expect it" is hard to justify.


One could also make an argument for the right side since most people are right-handed and may find it more convenient on tablet devices. Better would be a usability study, or arguments such as:

Pro-leftside:
- left-sidebar is expected from Firefox and MIE
- left-sidebar puts left-justified pages more in-center of user screen

Pro-rightside:
- assuming that most pages on the internet are left-justified, a per-tab left-sidebar could very annoying because the user's eyes would not know where to expect text (especially if the sidebar was large); this argument would dictate that the sidebar appear on the left by default for right-to-left languages
- most users are right-handed, so a right-handed sidebar may work better for tablet devices

Pro-either:
- may not be hard to code
- may otherwise annoy many users
@mats.ahlgren: I agree with you, that both positions make sense in different situations, and also that different users will prefer different things.

I think this is yet another example of where an about:config page would be very good to have.

That way, more advanced users would be capable of changing things within Chrome, while normal users would have a clean and minimal Wrench -> Options page.
The biggest problem I've faced with right handed side bars is that it makes hitting the scroll bar much more difficult - can't just throw the mouse to the side of the screen.
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=57898 

------------------------------------------------------------------------
r57898 | thakis@chromium.org | 2010-08-30 13:31:54 -0700 (Mon, 30 Aug 2010) | 11 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/app/nibs/TabContents.xib?r1=57898&r2=57897
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/browser_window_cocoa.h?r1=57898&r2=57897
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/browser_window_cocoa.mm?r1=57898&r2=57897
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/browser_window_controller.h?r1=57898&r2=57897
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/browser_window_controller.mm?r1=57898&r2=57897
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/tab_contents_controller.h?r1=57898&r2=57897
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/tab_contents_controller.mm?r1=57898&r2=57897
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/tab_strip_controller.h?r1=57898&r2=57897
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/tab_strip_controller.mm?r1=57898&r2=57897
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/view_id_util_browsertest.mm?r1=57898&r2=57897

Sidebar view, Mac implementation (common sidebar code and Windows version is already submitted).
TabContents.xib changes: it was converted to the latest IB version and vertical NSSplitView was added to it
as a child for existing horizontal NSSplitView hosting devTools; new one hosts page content and sidebar content.
BrowserWindowCocoa instance listen to SIDEBAR_CHANGED notification and updates sidebar content view according
to the sidebar state linked to the current tab (adds or removes the corresponding view).
Sidebar API design doc: http://www.chromium.org/developers/design-documents/extensions/sidebar-extension-api.
BUG= 51084 
TEST=Run browser_tests and interactive_ui_tests.

Review URL: http://codereview.chromium.org/3228003
Patch from Aleksey Shlyapnikov <alekseys@chromium.org>.
------------------------------------------------------------------------

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=57965 

------------------------------------------------------------------------
r57965 | aa@chromium.org | 2010-08-30 22:39:58 -0700 (Mon, 30 Aug 2010) | 7 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/extensions/extension_sidebar_api.cc?r1=57965&r2=57964
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/extensions/extension_sidebar_api.h?r1=57965&r2=57964
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/sidebar/sidebar_container.cc?r1=57965&r2=57964
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/sidebar/sidebar_container.h?r1=57965&r2=57964
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/sidebar/sidebar_manager.cc?r1=57965&r2=57964

Unify sidebar identification in the chrome.experimental.sidebar extension API implementation.

BUG= 51084 
TEST=Run interactive_ui_tests and browser_tests.

Review URL: http://codereview.chromium.org/3212005
Patch from Aleksey Shlyapnikov <alekseys@google.com>.
------------------------------------------------------------------------

@Chrome team: If you won't add in an about:config page, how about a command line switch? Something like --sidebar-on-left. Normal users will get the sidebar on the right, but if a power user wants it on the left, they can use the command switch.

Comment 17 by aa@chromium.org, Sep 15 2010

 Issue 30553  has been merged into this issue.
After reading the API, I assume that since an Extension owns a Sidepanel, can I assume that changes in one tab's sidepanel can instantly be reflected as changes in another tab's sidepanel? Or even better, can I assume that many tabs an have the same page open in the sidepanel, so that (for example) a focused element in one panel stays focused between tabs?

I'd also like to humbly propose the following three test cases and/or design choices, without which the sidebar will not work nicely for many use cases:
A: One should be able to code a very simple Vertical Tab Bar with the API.
B: Switching between tabs in example (A), by holding down a keybinding, should be just as fast as using ctrl-up/down normally; furthermore this test should not hiccup due to race conditions.
C: The sidebar should work on the homepage, about:blank page, Oh Snap! pages, Certificate/Trust warning pages, and every other type of page not mentioned.
D: Switching between tabs X and Y should not produce flickering if the sidepanels of X and Y are open to the same page.

Comment 19 by joi@chromium.org, Sep 16 2010

@mats, I would expect each sidepanel instance to have its own instance of whatever page you point it to (via URL) just like different tabs showing the same URL have their own instance.  This is a more general case, while for some extensions the case you propose might be useful.  I think there may be tricks to do what you proposed, I think I've seen some extensions that keep a page around and let you instantly switch to it (no load time) but I'm not sure what the trick is.
@mats, each tab's sidepanel has its own instance, so it's an extension responsibility  to keep them in sync should it need to show the same content for all tabs (please refer to earlier comments for pros and cons). To the test cases, we'll consider A; B, C and D do work as described and we'll keep them this way.

Comment 21 Deleted

Comment 22 by joi@chromium.org, Sep 23 2010

Assigning to Aleksey now that he has an @chromium.org address.
Labels: -Dev-TestPlan-No Dev-QAReview-No
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=66332

------------------------------------------------------------------------
r66332 | alekseys@chromium.org | Tue Nov 16 14:33:03 PST 2010

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/tab_contents/tab_contents_container.cc?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/frame/browser_view.h?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/tab_contents/tab_contents_container.h?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/browser_window_controller.mm?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/browser_window_cocoa.mm?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/render_widget_host_view_win.h?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/tab_contents_controller.mm?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/sidebar_controller.h?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/tab_strip_controller.mm?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/render_view_host_delegate.cc?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/browser_window_controller.h?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/gtk/browser_window_gtk.cc?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/gtk/browser_window_gtk.h?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/test_browser_window.h?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/dev_tools_controller.mm?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/render_view_host.h?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/render_widget_host_view.h?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/render_messages_params.cc?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/render_messages_params.h?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/frame/browser_view.cc?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/render_widget_host.cc?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/render_widget_host.h?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/sidebar_controller.mm?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/instant/instant_loader.cc?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/dev_tools_controller.h?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/browser_window.h?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/render_widget_host_view_win.cc?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/browser.cc?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/tab_contents/tab_contents_delegate.cc?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/browser.h?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/tab_contents/tab_contents_delegate.h?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/browser_window_cocoa.h?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/render_view_host_delegate.h?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/renderer/render_widget.cc?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/tab_contents/tab_contents.cc?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/tab_contents/tab_contents.h?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/render_view_host.cc?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/tab_contents_controller.h?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/tab_strip_controller.h?r1=66332&r2=66331&pathrev=66332
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/render_widget_host_unittest.cc?r1=66332&r2=66331&pathrev=66332

Handle resize corner layout entirely in the BrowserView (views) or BrowserWindow* (Mac)
and extend RenderViewHost with a concept of reserved contents rect, a place to show extra stuff,
such as Sidebar's mini tab UI.
sidebar UI implementation warranted this change (mini tabs UI and resize corner area for sidebar
contents).

TabContentsDelegate::GetRootWindowResizerRect() is no more, reserved contents area is now cached
in RenderWidgetHostView and updated upon view resize.

Views: BrowserView is responsible for the actual layout and reserved contents area update.

Mac: TabContentsController now manages all TabContents views in the main browser window to solve
two problems, first to prevent contents flickering during tab change not only for the page,
but for the sidebar and devtools contents too and, second, to monitor contents view frame changes
and update reserved contents area accordingly.


BUG= 51084 
TEST=All tests should pass, this is a refactoring CL.

Review URL: http://codereview.chromium.org/3547008
------------------------------------------------------------------------
Project Member

Comment 25 by bugdroid1@chromium.org, Jan 12 2011

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=71230

------------------------------------------------------------------------
r71230 | alekseys@chromium.org | Wed Jan 12 12:57:44 PST 2011

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/views/controls/single_split_view.cc?r1=71230&r2=71229&pathrev=71230
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/frame/browser_view_layout.h?r1=71230&r2=71229&pathrev=71230
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/tab_contents/tab_contents_container.cc?r1=71230&r2=71229&pathrev=71230
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/tab_contents/tab_contents_container.h?r1=71230&r2=71229&pathrev=71230
 M http://src.chromium.org/viewvc/chrome/trunk/src/views/examples/single_split_view_example.h?r1=71230&r2=71229&pathrev=71230
 A http://src.chromium.org/viewvc/chrome/trunk/src/views/controls/single_split_view_unittest.cc?r1=71230&r2=71229&pathrev=71230
 M http://src.chromium.org/viewvc/chrome/trunk/src/views/views.gyp?r1=71230&r2=71229&pathrev=71230
 M http://src.chromium.org/viewvc/chrome/trunk/src/views/controls/single_split_view.h?r1=71230&r2=71229&pathrev=71230
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/frame/browser_view_layout.cc?r1=71230&r2=71229&pathrev=71230
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/frame/browser_view.cc?r1=71230&r2=71229&pathrev=71230
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/frame/browser_view.h?r1=71230&r2=71229&pathrev=71230
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/chrome_tests.gypi?r1=71230&r2=71229&pathrev=71230

Streamline the layout of the BrowserView's children TabContents views.
Modify SingleSplitView to calculate its children view's bounds, but do not actually resize them
and change BrowserViewLayout accordingly (BrowserViewLayout resizes all views now).
Do all reserved contents rect calculations before resizing TabContents views.

Rationale: to do all BrowserView layout related actions in the context of
BrowserViewLayout::Layout call and to minimize actual contents re-layouts.

BUG= 51084 
TEST=All tests should pass

Review URL: http://codereview.chromium.org/5606012
------------------------------------------------------------------------
Project Member

Comment 26 by bugdroid1@chromium.org, Jan 12 2011

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=71252

------------------------------------------------------------------------
r71252 | eroman@chromium.org | Wed Jan 12 14:58:52 PST 2011

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/views/controls/single_split_view.cc?r1=71252&r2=71251&pathrev=71252
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/frame/browser_view_layout.h?r1=71252&r2=71251&pathrev=71252
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/tab_contents/tab_contents_container.cc?r1=71252&r2=71251&pathrev=71252
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/tab_contents/tab_contents_container.h?r1=71252&r2=71251&pathrev=71252
 M http://src.chromium.org/viewvc/chrome/trunk/src/views/examples/single_split_view_example.h?r1=71252&r2=71251&pathrev=71252
 D http://src.chromium.org/viewvc/chrome/trunk/src/views/controls/single_split_view_unittest.cc?r1=71252&r2=71251&pathrev=71252
 M http://src.chromium.org/viewvc/chrome/trunk/src/views/views.gyp?r1=71252&r2=71251&pathrev=71252
 M http://src.chromium.org/viewvc/chrome/trunk/src/views/controls/single_split_view.h?r1=71252&r2=71251&pathrev=71252
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/frame/browser_view_layout.cc?r1=71252&r2=71251&pathrev=71252
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/frame/browser_view.cc?r1=71252&r2=71251&pathrev=71252
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/frame/browser_view.h?r1=71252&r2=71251&pathrev=71252
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/chrome_tests.gypi?r1=71252&r2=71251&pathrev=71252

Revert 71230 to see if it is related to hang on linux interactive_ui_tests.

Original CL description:

 Streamline the layout of the BrowserView's children TabContents views.
Modify SingleSplitView to calculate its children view's bounds, but do not actually resize them
and change BrowserViewLayout accordingly (BrowserViewLayout resizes all views now).
Do all reserved contents rect calculations before resizing TabContents views.

Rationale: to do all BrowserView layout related actions in the context of
BrowserViewLayout::Layout call and to minimize actual contents re-layouts.

BUG= 51084 
TEST=All tests should pass

Review URL: http://codereview.chromium.org/5606012

TBR=alekseys@chromium.org
Review URL: http://codereview.chromium.org/6121007
------------------------------------------------------------------------
Project Member

Comment 27 by bugdroid1@chromium.org, Jan 13 2011

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=71259

------------------------------------------------------------------------
r71259 | eroman@chromium.org | Wed Jan 12 16:12:35 PST 2011

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/views/controls/single_split_view.cc?r1=71259&r2=71258&pathrev=71259
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/frame/browser_view_layout.h?r1=71259&r2=71258&pathrev=71259
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/tab_contents/tab_contents_container.cc?r1=71259&r2=71258&pathrev=71259
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/tab_contents/tab_contents_container.h?r1=71259&r2=71258&pathrev=71259
 M http://src.chromium.org/viewvc/chrome/trunk/src/views/examples/single_split_view_example.h?r1=71259&r2=71258&pathrev=71259
 A http://src.chromium.org/viewvc/chrome/trunk/src/views/controls/single_split_view_unittest.cc?r1=71259&r2=71258&pathrev=71259
 M http://src.chromium.org/viewvc/chrome/trunk/src/views/views.gyp?r1=71259&r2=71258&pathrev=71259
 M http://src.chromium.org/viewvc/chrome/trunk/src/views/controls/single_split_view.h?r1=71259&r2=71258&pathrev=71259
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/frame/browser_view_layout.cc?r1=71259&r2=71258&pathrev=71259
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/frame/browser_view.cc?r1=71259&r2=71258&pathrev=71259
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/frame/browser_view.h?r1=71259&r2=71258&pathrev=71259
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/chrome_tests.gypi?r1=71259&r2=71258&pathrev=71259

Re-land 71230.

This restores 71230 which was reverted in 71252 by sheriff (to see if it was responsible for a linux test failure -- it was not).

Original change by alekseys:

 Streamline the layout of the BrowserView's children TabContents views.
Modify SingleSplitView to calculate its children view's bounds, but do not actually resize them
and change BrowserViewLayout accordingly (BrowserViewLayout resizes all views now).
Do all reserved contents rect calculations before resizing TabContents views.

Rationale: to do all BrowserView layout related actions in the context of
BrowserViewLayout::Layout call and to minimize actual contents re-layouts.

BUG= 51084 
TEST=All tests should pass

Review URL: http://codereview.chromium.org/5606012
Review URL: http://codereview.chromium.org/6247001
------------------------------------------------------------------------
What we need is a sidebar - nota bene, to the left side of the window - that can be toggled on and off via «Ctrl+b», as in Firefox. In my case, I want to be able to display my Delicious Bookmarks on the panel. Provision of such a panel would be all that I require to make Chromium my default browser....

Henri   
Project Member

Comment 29 by bugdroid1@chromium.org, Jan 20 2011

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=71993

------------------------------------------------------------------------
r71993 | alekseys@chromium.org | Thu Jan 20 12:30:06 PST 2011

Changed paths:
 A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/manifest_tests/sidebar_icon_empty.json?r1=71993&r2=71992&pathrev=71993
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension.h?r1=71993&r2=71992&pathrev=71993
 A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/manifest_tests/sidebar_no_permissions.json?r1=71993&r2=71992&pathrev=71993
 A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/manifest_tests/sidebar.json?r1=71993&r2=71992&pathrev=71993
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_manifests_unittest.cc?r1=71993&r2=71992&pathrev=71993
 A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_sidebar_defaults.h?r1=71993&r2=71992&pathrev=71993
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension.cc?r1=71993&r2=71992&pathrev=71993
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/chrome_common.gypi?r1=71993&r2=71992&pathrev=71993
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/sidebar/sidebar_container.cc?r1=71993&r2=71992&pathrev=71993
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/sidebar/sidebar_manager.h?r1=71993&r2=71992&pathrev=71993
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/extensions/extension_sidebar_api.cc?r1=71993&r2=71992&pathrev=71993
 A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/sidebar/manifest.json?r1=71993&r2=71992&pathrev=71993
 A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/manifest_tests/sidebar_external_url.json?r1=71993&r2=71992&pathrev=71993
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/api_test/sidebar/manifest.json?r1=71993&r2=71992&pathrev=71993
 A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/sidebar/sidebar_browsertest.cc?r1=71993&r2=71992&pathrev=71993
 A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_sidebar_utils.h?r1=71993&r2=71992&pathrev=71993
 A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/manifest_tests/sidebar_url_no_permissions.json?r1=71993&r2=71992&pathrev=71993
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_constants.h?r1=71993&r2=71992&pathrev=71993
 A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/manifest_tests/sidebar_url_invalid_type.json?r1=71993&r2=71992&pathrev=71993
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_constants.cc?r1=71993&r2=71992&pathrev=71993
 A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_sidebar_utils.cc?r1=71993&r2=71992&pathrev=71993
 A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/manifest_tests/sidebar_icon_invalid_type.json?r1=71993&r2=71992&pathrev=71993
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/chrome_tests.gypi?r1=71993&r2=71992&pathrev=71993
 A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/manifest_tests/sidebar_url_invalid.json?r1=71993&r2=71992&pathrev=71993
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/sidebar/sidebar_container.h?r1=71993&r2=71992&pathrev=71993
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/sidebar/sidebar_manager.cc?r1=71993&r2=71992&pathrev=71993
 A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/manifest_tests/sidebar_title_invalid_type.json?r1=71993&r2=71992&pathrev=71993
 D http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/sidebar/sidebar_test.cc?r1=71993&r2=71992&pathrev=71993

Add "sidebar" section to extension manifest:

  "sidebar": {
    "default_url": "",
    "default_title": "",
    "default_icon": ""
  }

Allow extension to access experimental.sidebar API only in presence of this section.

BUG= 51084 
TEST=unit_tests, ExtensionManifestTest.Sidebar

Review URL: http://codereview.chromium.org/6321006
------------------------------------------------------------------------
Project Member

Comment 30 by bugdroid1@chromium.org, Jan 25 2011

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=72514

------------------------------------------------------------------------
r72514 | alekseys@chromium.org | Tue Jan 25 10:33:26 PST 2011

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_file_util.cc?r1=72514&r2=72513&pathrev=72514
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/manifest_tests/sidebar_icon_empty.json?r1=72514&r2=72513&pathrev=72514
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/manifest_tests/sidebar_no_permissions.json?r1=72514&r2=72513&pathrev=72514
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/manifest_tests/sidebar.json?r1=72514&r2=72513&pathrev=72514
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_manifests_unittest.cc?r1=72514&r2=72513&pathrev=72514
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_sidebar_defaults.h?r1=72514&r2=72513&pathrev=72514
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension.cc?r1=72514&r2=72513&pathrev=72514
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/experimental.sidebar.html?r1=72514&r2=72513&pathrev=72514
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/api/extension_api.json?r1=72514&r2=72513&pathrev=72514
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/sidebar/sidebar_container.cc?r1=72514&r2=72513&pathrev=72514
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/extensions/extension_sidebar_api.cc?r1=72514&r2=72513&pathrev=72514
 A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/manifest_tests/sidebar_page_empty.json?r1=72514&r2=72513&pathrev=72514
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/api_test/sidebar/test.js?r1=72514&r2=72513&pathrev=72514
 D http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/manifest_tests/sidebar_external_url.json?r1=72514&r2=72513&pathrev=72514
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_sidebar_utils.h?r1=72514&r2=72513&pathrev=72514
 A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/manifest_tests/sidebar_page_invalid_type.json?r1=72514&r2=72513&pathrev=72514
 D http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/manifest_tests/sidebar_url_no_permissions.json?r1=72514&r2=72513&pathrev=72514
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/app/generated_resources.grd?r1=72514&r2=72513&pathrev=72514
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_constants.h?r1=72514&r2=72513&pathrev=72514
 D http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/manifest_tests/sidebar_url_invalid_type.json?r1=72514&r2=72513&pathrev=72514
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_constants.cc?r1=72514&r2=72513&pathrev=72514
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/extension_sidebar_utils.cc?r1=72514&r2=72513&pathrev=72514
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/manifest_tests/sidebar_icon_invalid_type.json?r1=72514&r2=72513&pathrev=72514
 D http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/manifest_tests/sidebar_url_invalid.json?r1=72514&r2=72513&pathrev=72514
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/sidebar/sidebar_container.h?r1=72514&r2=72513&pathrev=72514
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/extensions/manifest_tests/sidebar_title_invalid_type.json?r1=72514&r2=72513&pathrev=72514

Only allow extension pages to be displayed in the sidebar to be consistent
with the rest of the extension system.

Change extension manifest "sidebar" section and sidebar API accordingly:

"sidebar": {
  "default_icon": "",
  "default_page": "",
  "default_title": ""
}

chrome.experimental.sidebar.navigate({tabId: ..., path: ...})

BUG= 51084 
TEST=browser_tests::Sidebar.*, unit_tests::ExtensionManifestTest.Sidebar

Review URL: http://codereview.chromium.org/6378009
------------------------------------------------------------------------
Project Member

Comment 31 by bugdroid1@chromium.org, Feb 4 2011

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=73822

------------------------------------------------------------------------
r73822 | alekseys@chromium.org | Fri Feb 04 10:47:23 PST 2011

Changed paths:
 A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/app/theme/sidebar_tab_active.png?r1=73822&r2=73821&pathrev=73822
 A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/app/theme/sidebar_tab_inactive.png?r1=73822&r2=73821&pathrev=73822

Adding new resources for http://codereview.chromium.org/6250141/ to be able to run it on trybots.

BUG= 51084 
TEST=none

Review URL: http://codereview.chromium.org/6368089
------------------------------------------------------------------------

Comment 32 by guria...@gmail.com, Apr 15 2011

I've noticed that now sidebar can't navigated to internet urls. I understand that it was made for consistent and security reasons.
But can we expect to place hosted apps in sidebars via container option in manifest?
Labels: -mstone-x

Comment 34 by mkte...@gmail.com, May 21 2011

 Issue 83406  has been merged into this issue.
When will it get fixed in the Linux version of Chrome? Testing my extension now and noticed that although it works fine on Windows and Mac, the sidebar is not showing up in Linux (both beta and latest 13.0.772.0 dev). No errors of any kind and even the sidebar's page loads (can see it in the active views) but the sidebar just doesn't appear in the UI.

Oh, and any idea on when this will graduate from experimental?

Thanks!

Comment 36 by sky@chromium.org, Jul 15 2011

 Issue 85315  has been merged into this issue.
One of my first chrome extensions use sidebars, I work on Ubuntu so imagine my surprise not seeing the sidebar never and the code "working without errors".

I test with the unstable chrome and beta for linux without good results, but with the beta on Windows everything works flawless.

Thanks in advance for the answer.

Comment 38 by met...@gmail.com, Oct 5 2011

A comment in  issue 62701  speculates that the experimental sidebar is being pulled. Aleksey can you comment on the future of the sidebar?

Comment 39 by Deleted ...@, Oct 10 2011

Also curious on the status of the sidebar. Started working on a project specifically because of the sidebar only to see it might be pulled. Any status?
Need to know here as well. Thanks!

Comment 41 by aa@chromium.org, Nov 9 2011

Owner: ----
Status: Untriaged
The sidebar's on ice for now. We're going to go through an API prioritization exercise near the end of the year to figure out what's important for 2012, so there's some chance it could resurface. I'd put the probability pretty low though.

Comment 42 by aa@chromium.org, Nov 9 2011

That last comment was more negative than it should have been. Let me try again:

I think there's still broad interest in having a sidebar surface for extensions, but we need to prioritize it against other new features and improvements that we also need to do.

Right now, it looks to me like it's lower priority than some other things we'll be working on for the next year, but we need to look through all the use cases to be sure. I hope to have a more clear picture in the next month.

Comment 43 by mkte...@gmail.com, Nov 10 2011

Thanks for the update!  I know lots of people still want a bookmark sidebar in some form (e.g.  Issue 45365 ).

Comment 44 by Deleted ...@, Dec 3 2011

Just installed Chrome and hardly missing a bookmark sidebar. Very bad, because Chrome is much faster and better than Firefox. But I will use Firefox again until there is a Sidebar available.
The thread (http://www.google.com/support/forum/p/Chrome/thread?fid=4c5bdb5b16092e680004b30670f68c3b&hl=en) suggesting the addition of a customisable sidebar to Chrome/Chromium on the Google Chrome fora now has some 233 posts, almost all of them requesting this feature. I fail to understand why the Chrome/Chromium developers, who have otherwise done such a splendid job with the browser, persist in their failure to address this problem. No explanation from them as to why such a sidebar would be undesirable has ever been provided....

Henri 
Status: Available
Mozilla is probably thrilled that no persistent bookmark sidebar is available for Chrome - it's one of the most cited reasons for staying with Firefox.

Comment 48 Deleted

It is certainly one of the most important reasons for me....

Henri
Labels: Restrict-AddIssueComment-Commit
Summary: Add extension capabilities sufficient to deal with use cases like persistent bookmark surfaces
No one wants to just leave users in the lurch.  There's been some consideration about whether we can do something that would not only allow for "sidebar-like" experiences but also be more generally flexible and powerful.  One of the current suggestions is to provide the ability to "tear off and dock" browser action bubbles/panels or other surfaces.  This would not only allow people to set up bookmark sidebars but potentially provide other convenient, configurable surfaces for extension use.  (This is vague because we haven't thought it through in detail yet.)

Accordingly, I'm morphing this bug to be about the broader issue of finding some way to accommodate the use cases of people who use bookmark sidebars in other browsers.  This makes it clear that even though we're going to remove the unfinished current work we still want to tackle this problem.

I'm also going to temporarily close this for comments; we can reopen it at the point when we have a meaningful-enough proposal that it's ready for outside feedback.  Thanks for all your interest in this issue so far.
Project Member

Comment 51 by bugdroid1@chromium.org, Mar 10 2013

Labels: -Feature-Extensions Cr-Platform-Extensions

Comment 52 by laforge@google.com, Mar 13 2013

Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue

Comment 53 by joi@chromium.org, Mar 29 2014

Cc: -joi@chromium.org
Labels: -Restrict-AddIssueComment-EditIssue
Summary: Add sidebar surface for extensions (was: Add extension capabilities sufficient to deal with use cases like persistent bookmark surfaces)
Morphing this back to being explicitly about sidebars.  As far as I can tell from various discussions the primary issue is a lack of manpower to implement this.  I haven't heard either serious alternatives to sidebars proposed, or principled opposition to the sidebar concept from the UI leads.

Also reopening this so that serious individuals who want to work on implementing this can say so.  Note that if this turns into a "me too" bug where people spam comments asking for this to be implemented, it will be re-locked.  Please don't reply unless you have substantive design and implementation comments to add.  If you simply want this to happen, star the issue instead.
I would strongly recommend to use Tree Style Tab from FF as a design reference. Styling could be simplified, as well as autohide, all other features should be implemented as is. 

Link to the extension just in case: https://addons.mozilla.org/en-US/firefox/addon/tree-style-tab/
I use and love All-In-One Sidebar for FF: https://addons.mozilla.org/en-US/firefox/addon/all-in-one-sidebar/
I really like the sidebar but I also use the sidebar panels quite a lot. This is a very handy feature with great implementation by AiOS. I am able to create shortcuts to extension but also open Bookmarks, History, Downloads, even an extensions panel that lets me manage my Add-Ons and Extensions and their options in one place. 
Honestly this is the killer feature for me that is the only reason why I haven't completely switched over to Chrome.
I mean I can leave open my QuickNote in the sidebar and toggel it off and on with ease. If Chrome could do that I would have no reason to stay with FF.
I'd just be happy with a bare-bones toggled bookmark sidebar... that should maybe be what people are shooting for, in terms of a preliminary project.

Thanks for opening the issue back up again!
The default bookmarks manager (chrome://bookmarks/#1) have a bookmarks sidebar. This can be a good start to integrate it in the interface for the navigation.

Also this can be useful. Neater Bookmarks have already everything needed to make a bookmark sidebar and is open source.

https://chrome.google.com/webstore/detail/neater-bookmarks/ofgjggbjanlhbgaemjbkiegeebmccifi

And thanks for opening the issue back up again!
Thank you, Peter. As far as manpower goes, I can provide help with that problem. My company is willing sponsor development of this feature.

I can start working immediately on a CL to revert https://codereview.chromium.org/9006027 and add back the old experimental sidebar implementation. However, there may be product/UI considerations that would make another implementation preferable. Please feel free to share with me any requirements for a sidebar. If this discussion is better had over email, phone, or in person, I'm happy to do that as well. Additionally, if there's anyone who wants to collaborate on this, please feel free to email me.

A real sidebar would very considerably improve one of our products, which is a sidebar extension used by a good chunk of Silicon Valley and over a quarter of the Fortune 100. We run into lots of problems with our workaround of injecting an iframe into pages.
I was working for another big company in 2011 building a chrome extension that its UI used a sidebar. When the previous code was removed I had bassically a few options to go:
- doesn't update the chrome (bad)
- move to firefox (bad)
- change back to iframe inject (bad)
- implement a sidebar-like ui using panel windows (done)

A few weeks ago I retest the code in recent chrome and it stills works. If there are people that still wants this, I can refactor the snipets and extract to a public extension skeleton. IMHO it works pretty well since I manage windows resizing, etc.
@benjamin and JJLo, great to see the enthusiasm! I really hope we can get one or both of these running, I'd love to have a moveable button on the chromium toolbar that toggles a sidebar while resizing the main window. I'm confident that with that functionality in place all sorts of plans can be realized by extension devs... including the tree-based bookmark panel. :) Really the only thing that's kept me using firefox all these years.

Wherever you both decide to converse with other devs on this, I hope you'll keep us updated here! And I would gladly test this feature out, for what it's worth. Good luck!
Cc: asargent@chromium.org miket@chromium.org ainslie@chromium.org kalman@chromium.org
 Issue 319130  has been merged into this issue.
@55: This bug isn't about tree-style tabs.  Please be sure to stay on topic.

@58: I am not sure, but I believe the sidebar in the bookmarks manager is simply web content.  An extension sidebar would be a different beast, as it would need to be a native UI surface (that could then presumably contain extension content).  I doubt that any existing extension or built-in page is going to be very usable as a base for the implementation of this feature.

@59: Done.

@60: I don't know enough to advise for sure, but I suspect the old CL, while a useful reference, might not be the best current implementation.  You might ping sky@chromium.org to see if he has advice for how to proceed or who the best people are to provide input.
@#54:

Here is an existing fully implemented solution for side tabs that works around the missing sidebar API: https://chrome.google.com/webstore/detail/tabs-outliner/eggkanocgddhmamlbiijnphhppkpkmkl?hl=en

I'm sure the author would express interest in building his plugin into the actual sidebar instead of a separate window (and I would love him for it too).
Hopefully the implementation of the sidebar would be generic, as the title suggests, and not be a purpose-built solution for tab management. A lot of developers would get mileage out of sidebar real-estate without having to hack the DOM of target sites.

Comment 67 Deleted

@65/66: This bug has absolutely nothing to do with tab management, side tabs/tree-style tabs or otherwise.  This bug is only about a general-purpose sidebar surface for extension use.  Tab management is one of many possible use cases for such a surface, for certain, but discussion of that would fit best elsewhere.

(Hopefully this is clear enough -- if in the future people start talking more about tab stuff rather than sidebar stuff I may quietly delete comments just to try to minimize the risk of the bug getting off-track and taking away from the work to implement this.)
Understood, don't mean to hijack the topic and you're more than welcome to delete my post at your discretion.  Just wanted to point out an already implemented case that would benefit from this feature. 

Comment 70 by omn...@gmail.com, Jan 21 2015

>>>
Here is an existing fully implemented solution for side tabs that works around the missing sidebar API: TabsOutliner
I'm sure the author would express interest in building his plugin into the actual sidebar instead of a separate window (and I would love him for it too).
>>>
I am the author. And i can tell that this is really one of the most common request of my users.

There a lot of other uses for such a sidebar. For example for my Tabs Management extension it's not very needed - as my extension have a list of all windows, as currently opened as saved, and so it's illogical to have this list in a soem sort of sidebar that is common for all windows. But there is a lot of other very useful and interesting cases for actually having a sidebar

MY extension is not just tabs manager, but also a personal information manager, and it's provide possibility for example to add comments to tabs (for example when you reading an article and make notes along the way), i myself use this very often, and it will be awesome to have and edit such comments in sidebar. I myself plan to implement this through inpage script, but for this need to declare access rights to modify the page? and in general it's an ugly hack with a lot of drawbacks - will be awesome to have natively supported sidebars

And yes, having tabs tree in a sidebar, is a very common request for my users, there is a category of users who always have only one window, often maximized. For sure i will add a support for tabs in sidebar when such possibility will be present. 

Comment 71 Deleted

I hope people stop posting yet more pointless +1/MeToo comments. (Yes, that was aimed at you m.thaeml...). Please don't reply -- if you care about this you should "star" the issue and *not* comment unless you have something substantive to say. This has already been made clear repeatedly be the people in charge.

(I recognize the urge, but it's not constructive.)
As you probably know, Opera recently implemented sidebarAction[1] for their UI. When they were asked why they did it in opr.sidebarAction, instead of chrome.sidebarAction they said -- because it's UI feature and it's not related to Chromium project, which I believe is a good point since they have different UI.

So my point is -- maybe you (Chrome Team) are able to contact Opera Team to share that implementation? I understand what you UI is different and what it's their proprietary implementation, but Google and Opera might cooperate and make better extension experience for users of both browsers. Thanks.
 
[1] http://blogs.opera.com/desktop/2015/03/sidebar-extensions-speed-dial-syncing-customizable-shortcuts-opera-developer-29/

Comment 74 by cg.gu...@gmail.com, Mar 30 2015

If Chrome team don't see urge in sidepanel implementation, I think they should.

Opera's sidepanel is now in beta, but next month it will be official.
For folks who want simple vertical tabs:
https://addons.opera.com/en/extensions/details/simple-vertical-tabs/?display=en
And Bookmarks:
https://addons.opera.com/en/extensions/details/bookmarks-by-the-side/?display=en

Guy who started thread, which pushed the idea, probably there are more threads like this:
https://forums.opera.com/discussion/1860038/sidepanel#Item_27

Comment 75 Deleted

Comment 76 Deleted

Hi, please don't treat the bug tracker as a forum. We have been working on a sidebar implementation for several months. More details to come in the near future.
Just wanted to remind that when this feature will be implemented there needs to be an option to hide top tab bar. The "user" and "close-minimize" buttons could be easily moved to main panel near the menu button. I tried side tabs in Opera and it is confusing to have browser tabs in two places simultaneously. I understand that this feature is developed not only for side tabs but judging by activity here and in other places side tabs will be the primary use case for it.

Comment 79 by ka...@jagiello.it, Apr 22 2015

Hi I'm the author of this extension:
https://addons.opera.com/en/extensions/details/simple-vertical-tabs/?display=en
Good to see some movement here :)
I will convert my extension as soon as I see implementation of sidebar in Chrome, so you have to be patient. For now you can try to use Opera dev or beta, in a week or two Opera 29 will be released as stable, but I'm not sure if sidebar will be enabled by default. Probably not, but it's easy to be enabled in about:flags.
Cc: -erikkay@chromium.org
Can we have an update on the sidebar feature please ?

I found that but there don't seem to have much activitie these days
https://code.google.com/p/chromium/issues/detail?id=477424
My company and another have partnered to work on the sidebar. The old code had severely bit rotted, so it's taken us until now to get something decent up and running. There are a lot of edge cases though in a product as large and widely used as Chrome, so it's going to take a good amount of time still to get right. We're making continuous progress though and will post here as soon as there's something real to share.
Thank you very much for the update !
Thank you very much, Benjamin, for this information ; I am sure that many users are looking forward to having a sidebar into which, e g, a bookmarks field can be inserted, in Chrome. That would make an excellent browser truly great !... :-)

Henri
Benjamin, I saw that it's seems you planned to have the sidebar only on the right side. Please let the user choose if he want it on the right or on the left. 
Thank you
Agree with Jeremy ; I want to have mine on the left....

Henri

Comment 87 by choz...@gmail.com, Jul 5 2015

@people-saying-this-is-not-about-tree-style-tabs

Well - it is a little, as extensions like https://addons.mozilla.org/en-US/firefox/addon/tree-style-tab/ are really important to many FF users - myself included.

If this feature would not allow creation of a similar plugin - it'd be no good to us!
For a starter, Choz, I - and I assume many FF users like myself - would be happy just to get a sidebar the placement of which we can control. Tree-style tabs could be a later development, but the important thing is that sidebar !... ;-)

Henri

Comment 89 by isol...@gmail.com, Jul 5 2015

Would you all please leave the topic with irrelevant chatter as was requested many times?
Agreed, I think it's way too early to talk whether the top tab bar can be hidden or if the side tabs can be placed left or right. I'm sure those details can be worked out later.
Guys, I just love reading this thread for 3+ years... In Firefox... With Tree Style Tabs installed. And yes, we need to focus on the core feature - sidebar itself, no matter why and how it will be used.

Please, don't take it too serious :) 
For Firefox users still using the old "tree style tab" extension check this out: https://addons.mozilla.org/es/firefox/addon/tabkit-2nd-edition/ Is an improved version with more features. I recommend also installing: https://addons.mozilla.org/es/firefox/addon/tab-kit-tab-highlighter/ (from the same author).


FFS, when will you people stop shitposting your offtopic spam?! The Chromium bug tracker is not a goddamn forum, go create a Google group and post your Firefox tab extensions crap there — it has *nothing* to do with this issue!

Or are you assholes purposely trying to get this issue locked again?
Thank you, «KBirz...» for your courteous and tactful intervention on this thread. A model poster is what you are.... ;-)

Henri

Comment 95 by rob@robwu.nl, Jul 6 2015

Blockedon: chromium:477424
I'm linking this issue to  issue 477424 , so that everyone can easily see that this feature is being worked on. Don't expect quick results though: in the worst case the full feature set might not be available this year, but next year (according to McCann, the one who implements the feature, by private mail).

And please do not post any comments that do not add anything to what's already been said, including comments that ask others to stop posting off-topic comments. Every new comment can trigger 450+ mails...
Mergedinto: 477424
Status: Duplicate
It looks like kalman opened a new bug for this; duping.
Blockedon: -chromium:477424
That's very disappointing... They have killed the sidebar !

https://code.google.com/p/chromium/issues/detail?id=477424#c82 
Yeah, totally sucks. Firefox is really getting crappy lately, so now what?
That is indeed a disappointing decision ; the notion that adding a sidebar to Chrome would violate its basic design philosophy, i e, simplicity, is, to my mind, absurd. A sidebar containing, e g, one's bookmarks, is no more complicated and no less simple than a horizontal bookmarks bar, and far easier to scroll....

Henri

Comment 102 by joe...@gmail.com, Jan 10 2016

Opting for simplicity is a mistake when the resultant UX is deficient. But perhaps we should just be resigned to Chrome's tab-bar navigation being near useless with more than a few dozen tabs.

Comment 103 by ka...@jagiello.it, Jan 10 2016

There is no other option left... Just leave chrome and go with Vivaldi or Opera

Comment 104 by choz...@gmail.com, Jan 11 2016

Yep, chrome can have web-based spelling checks, and form filling - things which could happily be in an extension... but a side-bar, like the  one already in developer tools - but that extensions can use? outside of scope...

Well - happily, chromium is FOSS, so if someone feels strongly they can fork it (I really want a sidebar, mostly for tree style tabs, but not enough to bother forking yet)
Labels: Restrict-AddIssueComment-EditIssue
Feel free to continue the discussion on the chromium-discuss mailing list at https://groups.google.com/a/chromium.org/forum/#!forum/chromium-discuss




Showing comments 6 - 105 of 105 Older

Sign in to add a comment