-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retire stack layout UI for tabs overview mode #21005
Comments
Resolves brave/brave-browser#21005 Chromium change: chromium/chromium@94a231f Remove unused rendering code in TabLayout Follow up to https://chromium-review.googlesource.com/c/chromium/src/+/3388174 and continues to simplify the Tab rendering logic for phones. Also deletes anything related to tilting/rotating and card backs for the tabs. Bug: 1287653
Resolved by brave/brave-core#12201 |
Resolves brave/brave-browser#21005 Chromium change: chromium/chromium@94a231f Remove unused rendering code in TabLayout Follow up to https://chromium-review.googlesource.com/c/chromium/src/+/3388174 and continues to simplify the Tab rendering logic for phones. Also deletes anything related to tilting/rotating and card backs for the tabs. Bug: 1287653
Resolves brave/brave-browser#21005 Chromium change: chromium/chromium@94a231f Remove unused rendering code in TabLayout Follow up to https://chromium-review.googlesource.com/c/chromium/src/+/3388174 and continues to simplify the Tab rendering logic for phones. Also deletes anything related to tilting/rotating and card backs for the tabs. Bug: 1287653
Resolves brave/brave-browser#21005 Chromium change: chromium/chromium@94a231f Remove unused rendering code in TabLayout Follow up to https://chromium-review.googlesource.com/c/chromium/src/+/3388174 and continues to simplify the Tab rendering logic for phones. Also deletes anything related to tilting/rotating and card backs for the tabs. Bug: 1287653
Resolves brave/brave-browser#21005 Chromium change: chromium/chromium@94a231f Remove unused rendering code in TabLayout Follow up to https://chromium-review.googlesource.com/c/chromium/src/+/3388174 and continues to simplify the Tab rendering logic for phones. Also deletes anything related to tilting/rotating and card backs for the tabs. Bug: 1287653
This requires a CR99 build on 1.36.x. Fix is part of the CR99 commit. cc: @Uni-verse |
This is a horrible decision. Many users including myself left Chrome because this stack feature was removed. Please bring this back. |
Bruh, I realize this is maintenance effort, but you're gonna have to weigh this effort against the possibility of losing a large chunk of your userbase that only came here from chrome because you didn't do that shit. |
Please undo this. I have been completely lost & frustrated after less than a week since tabs were SURPRISINGLY CHANGED to tiles. When chrome did this I completely left & came here. I really like Brave & hope this gets fixed but I can't do this for much longer. It actually opens more tabs than cascade mode. I believe the majority of the community agrees & is ready to change browsers again. |
Created this account just to say that I'm going to another browser if stack layouts are still gone after an update or two. Grid is terrible. |
Hi folks - issue created for re-adding the "Stack View" here: More information about this can be found here: |
I absolutely hate the person who made this post. Do not destroy the only feature that made your browser worth switching to in the first place. I will never use Chrome again, so long as grid view is the only option. It shouldn't even be an option, it's trash. |
Description
Now that we have an option to open in a new tab from the context menu brave/brave-core#12149, users are not forced to group tabs anymore. We should retire stack layout UI for overview mode as it requires more and more resources for maintenance.
Steps to reproduce
Actual result
Expected result
Issue reproduces how often
Version/Channel Information:
Device details
Brave version
Website problems only
Additional information
The text was updated successfully, but these errors were encountered: