Allow extensions to modify Chrome browser UI and change how tabs are shown.
Reported by
galchenk...@yandex.ru,
Jun 28 2017
|
||||
Issue descriptionTO WHOM IT WILL CONSIDER What do you want? Hello, today I want to discuss Chromium-based plug-ins and extensions. Nowdays Chromium has a huge amount of extensions, which allows people to block ads, to change their IP-adress, to check mailbox fastly, to control their new tab page etc. Yes, it is brilliant. But there are access limits for extensions in Chromium, especially if our attention stops on the user interface. Let's look at the head of the browser. We will see navigation buttons, reload page button, home button (if it is turned on in settings), adress bar, toolbox and a context menu. The same thing with other elements in the head. If they satisfy a user, it is brilliant, but what happens if a user is not satisfied with this construction due to personal or work conditions? A person will be finding the way how to change the browser's interface. But now it is impossible. The head stays like a monolith and does not allow to realise changes. The feature request, which I offer, is to unlock this head and expand the range of Chromium-extensions influence. It will satisfy thousands of users giving them more freedom in the personalizing. For example, look at the attached file. Yes, it would be a Chromium browser under influence theese plug-ins. Why do you want it? This ability would help to fix some issues and do browsing easier. The best example is a popular issue #188: https://bugs.chromium.org/p/chromium/issues/detail?id=188 and all other merged ones, which report about tab overflow and which are not fixed yet (why?). If you read all the comments, you will see many ways to fix it. Many people — many points of view. The best solution offers comment #167: "I think adding options in preferences for a user to choose which tab management scheme they want to use would be the best solution. That way everyone is happy, and chrome would still get to keep its default look and feel. I would vote for the options being: Default - the current tab scheme Scrollable - like the way firefox is by default Multi-Row - such as the way tab mix plus for firefox behaves and automatically adds up to a set limit number of rows (and then scrolls the rows when there are too many tabs for the rows open) Multi-Row with autohide - such as has been suggested before where only one tab row is displayed until a user mouseovers the tab bar, then more rows are displayed and i'm sure other users have more management schemes they could suggest". What the result? Quotation from developers (https://blog.chromium.org/2009/01/tabbed-browsing-in-google-chrome.html): "Many Tab Overflow We don't have a complete system for handling many open tabs right now. We let tabs grow infinitely smaller. This ends up looking bad when there are a very large number of tabs open. We chose not to go with an overflow menu or scrolling tab strip like in some other browsers because we think there are other usability problems with those approaches. Specifically, when you implement an overflow solution you generally pick a minimum "readable" width for the tab and overflow tabs when there are too many at that width to fit. The problem is usually that that width seems to be too wide, so there can be unnecessary overflow in conditions where a smaller tab width would have meant all of the tabs would have fit. We also don't really like the drop-down menu approach as it has a spatial disconnect (vertical scanning vs. horizontal tabs) that makes it clumsy to use quickly. In the end, we would like a system that doesn't over-zealously clip tabs out of the tab strip so that people with many tabs can still access their tabs with one click." "Yery good". The first question is how long will you be developing this system? It was January 6, 2009, when this post had been published. Now it is June 2017. What had changed? Nothing. So, we could approximately wait for twenty years more? But how can we manage the overflow theese twenty years? I absolutly agree with the comment #185. This solution is the best to fix it. I could give other examples, which are connected with other toolkits, but it would be boring to listen to them. THE STATEMENT: "If you want to get some special features, you can also download another Chromium-based browser. There is an enough wide of them: Torch, Cent browser, Slimjet, Uran etc.". THE ANSWER: Theese projects provide a normal user a certain number of features. If you want to get the functions, which are provided in separate ones, you should not combine them (of course, it is crazy idea to do this). For example, if you want to get a specific download manager and mouse gestures. The first function is realised in a browser #1, the second — in a browser #2. The feature, which I offer, will provide a personal constructor for Chromium. The features, which are required, will be founded, downloaded from Chrome web store and managed in extensions menu. Is it possible to do it? I am looking forward to hearing from you.
,
Feb 13 2018
,
Jan 10
Issue moved from a project with a different set of status labels. "New" is not a supported status in /p/chromium, so these ended up in a black-hole.
,
Jan 11
[Extensions Triage] This seems to be a feature request to allow extensions to modify the Chrome browser UI, particularly for tab management. AFAIK, the extensions team doesn't have any current plans for this. Marking as Available. |
||||
►
Sign in to add a comment |
||||
Comment 1 by seanmccullough@chromium.org
, Jun 28 2017