-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Make Chrome Refresh 2023 avoidable in the long term #37770
Comments
@highbaser Thanks for filing the issue, we're taking a look through your points. Also note that this tab design for tabs is still supported if you want to go back to the old look: brave://flags/#brave-horizontal-tabs-update We won't touch that flag until we have a compact mode that will match your expectations for that compact style of toolbar. |
You seem to have slipped up and let some of the Chrome 2023 refresh through. The tab bar is fine, but the menus are now messed up. They take up a lot more space. The Brave menu no longer fits on my screen without having to scroll. And scrolling menus have always been bad UI. Honestly, this was the main reason I switched to Brave, so I'm rather frustrated. I was expecting you to keep the ability to disable the Refresh until you could come up with "compact mode that will fit your expectations" as stated above. |
It's worse than I thought. I hadn't tried right-clicking yet. It still does this weird stuff where the menu won't take up the available space. Chromium right click menus have like 15-20 options, but sometimes the menu will only show 5 items. You have to scroll. Please, please, PLEASE revert whatever change forced the new menus, or at least revert the ability to turn off Chrome 2023 Refresh, and default to it being off again until you can make menus compact again. |
Just switched to Brave a week ago, because of the newly forced atrocious Chrome UI, only to see it back in the latest Brave version. Having to scroll the context menu is just bad, I've made comparison the old menu vs. the new one in Chrome, it's literally 40% larger, for no reason at all, so much wasted space... |
I just switched to Microsoft Edge, they’re on Chromium 126 and they didn’t support the stupid Chrome Refresh 2023 theme, no need to disable flags or anything! so I’ll stick to Microsoft Edge for now |
I'd love to see a way to revert back to old menus too. |
I had to revert back to Brave 1.65 as the huge menus with items scrolling out of the viewport are unusable for me. I hope the Brave team can come up with a general solution for this, and allow users to opt-out of these Chromium/Chrome UX regressions -- I don't think that having normal desktop UX is too much to ask for a desktop application. |
Thank you for making this report. I had to downgrade too. Unfortunately not even disabling As @jspatz mentioned, the right click menus are way too large and items are scrolling out of view. (see also: #38706). It's hard to understand why the chrome/chromium team keeps redesigning these things. I'm not sure if I can mention other browsers, but the biggest competitor made/makes this exact same mistake. Only for people to have to mess around with css or js scripts to fix it. Sometimes it appears as if things are being redesigned just for the sake of it, without any real purpose. A lot of people just want the basic tabs/menu's the way it has always been. To be more specific, there are now also 3 spots with useless padding where people will now accidentally click:
There is no use case for this padding at all, nothing happens when you accidentally click on it and it's completely in the way. All of that said, much respect to the Brave team for at least trying to keep the basic layout alive. I hope these new layout problems can be fixed too. |
@rebron Could you please address the issues above too? |
Hi folks
We intentionally rebase against Chromium and get all the updates. Please believe me - this has been a particularly painful one for us as the removal of the flag has caused a lot of grief in the codebase. Lots of UI regressions. We're doing our best to address specific items. Instead of an issue asking "Revert Chrome Refresh 2023", I'd like to ask if there are specific things we can try to modify. Some folks have already done a great job calling those out above (spacing, etc). Those are things we can definitely address @rebron and others are watching over this. But more specific items would be helpful - this issue (kind of a blanket issue) will likely be closed in favor of more specific issues that we can address. |
@bsclifton Like I said, the main issue for me is the change of how menus work. They not only have too much spacing, but also do not expand to fill the whole screen height anymore, leaving us with like 5 menu items, depending on where you click on the screen. I note that Edge seems to have the same style of menus, but does not have this particular problem. The same is true of Firefox (though I know that's a completely different beast). And, while not entirely open source, it's possible that Vivaldi's ability to just use the native menus is available code. That would be the ideal: just revert back to using the native menus of the OS. Or, at least, have an option to do so. |
Note that what I described above is already a separate bug: #39066 |
@bsclifton I'm not sure why you're asking for specific issues as I opened the issue with linking to specific ones. Also I did my own testing and enumeration about which issues are present (or will likely be present after Chromium rebases) in Brave. So what you're asking for is already done. All of these are painful UX issues, especially those related to increased padding and vertical real-estate wasting, unreadable/blurry fonts, unrecognizable icons. You can see the details in the opening post, with links to issue trackers containing screenshots and videos. |
Restoring the experimental flag deleted by Google and avoiding code conflicts is a difficult task, and I am still waiting for the solution of other Chromium browsers. For those Google Chrome users who want to continue using the old appearance during the waiting period, I found the download links of M122 and M123 versions and shared them with you (I am very sorry that this content is not related to Brave browser but there are no other platforms to discuss this). M122 has an "Extend" version on Windows and macOS, which fixes more vulnerabilities than the normal version. Here is the link: https://gist.github.com/Undefined-User/6e8c3bd7623c168ac3bb3f8dcbe9d562 |
@Undefined-User Supermium has employed the solution of backing out the patch and then sticking with M126 and the extended patches (I believe from Chrome OS LTS). I'm not sure what their plans are when that version expires. But I think Thorium has the solution that Brave could use: they are creating their own UI patch that reverts most of the changes. A beta version already reverts the most important parts, and it is going to be a separate patch file. It is intended for other browsers to use. I also note that Vivaldi doesn't have this issue. It has its own customizable web-based UI, and an option for a "compact" menu. The main downsides are that it has no tab search drop down button, and they have explicitly said they will not retain Mv2 compatibility. Oh, and their built-in adblock is old and not very good compared to Brave's or uBlock Origin. (I am looking into adding back the tab search button, as it's only the button that's missing. The URL for the dropdown still works. And, like I said, the browser UI is customizable.) |
@trlkly |
This is a feature request about handling Chrome Refresh 2023 in the future.
Google started to introduce a UI refresh, starting from M115. The change is called "Chrome Refresh 2023". There are many bug reports, UX issues and negative feedback about this change and Google seems to be stubborn enough not to pay attention and force it upon all of its users. With M125 Chromium release, Google is expiring (and later removing) the flags that can disalbe the changes of Chrome Refresh 2023.
From an advanced desktop user point of view this is an anti-feature that ruins the classic desktop experience (with mouse and keyboard), wastes vertical real estate, replaces icons to colorless unrecognizable ones. These changes are visually incompatible with a conventional desktop and makes the desktop user's life harder.
Chrome Refresh 2023 is already in latest nightly build of Brave (now: 1.67.30) as it's based on M124 and the feature is turned on, however not all anti-features seem to have been adopted. Here is a detailed list of what current Brave seems to have.
Please do not adopt! See: https://issues.chromium.org/issues/330743875
Please consider reverting this change to have consistent looks between icons in the bookmark bar and in the bookmark editor.
Colorless wireframe icons are harder to distinguish from text. Also, the "New folder" button color is harder to read in light orange than before (black). Comparison: brave-bookmark-editor.png
Please do not adopt! See: https://issues.chromium.org/issues/330589210
Please do not adopt! See: https://issues.chromium.org/issues/335553327
See: https://issues.chromium.org/issues/332574933
See: https://issues.chromium.org/issues/327022941
Basically the tab bar of Brave now looks like the same as of Firefox, however the older tab bar was more compact and wasted less vertical real-estate. It would be better to have the more compact look back. Comparison: brave-tabs.png
Please do not adopt! See: https://issues.chromium.org/issues/330753883
So basically I'm asking for the following changes related to Chrome Refresh 2023 manifestation in Brave.
Brave could be a great alternative for advanced desktop users who are disappointed or annoyed by the Chrome Refresh 2023.
Issues
Issues related to Chrome Refresh 2023, from the Chromium Bug Tracker.
Negative user feedback
Negative feedback from mostly advanced users who suffered a UX degradation because of Chrome Refresh 2023.
The text was updated successfully, but these errors were encountered: