-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Revert Chrome Refresh 2023 or keep it avoidable #77
Comments
@highbaser I've already done this in regular Thorium M123 because I hate it too. When this repo gets rebased on Chromium/Supermium 123, it will have those fixes too. However, Chromium 125 completely removes all the older code related to non-CR23 UI. In that case it will be alot harder to maintain, and depending on the amount of files involved, I might use CR23 UI. I would like to make a patch to at least put the tab search button back on the right side again though. |
As far as I know, Supermium devs have reworked the entire tab drawing logic in order to have a look&feel that fits into the XP ecosystem. You advertise thorium-legacy (Thorium-Win7) as something that fits into the Win7 ecosystem aero glass tab bar, etc. Chrome Refresh 2023 ruins this all so I think it's as much vital to keep it as important it was to create all your compatibility patches for Win7, like the one that keeps Aero glass support. Also, Supermium is planning to keep the UI before refresh in the long term. So I don't think you'll need to write these patches from scratch past M125. |
It seems these imbeciles can't help but change for the sake of change and not let people choose their damn design. If it were so good people wouldn't be trying to avoid it like the plague it is. This kind of thing made me abandon Firefox years ago. |
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, like they did with DirectWrite, however this change has already received even more negative feedback. With M125 release, Google is expiring (and later removing) the flags that can disalbe the changes of Chrome Refresh 2023.
Chrome Refresh 2023 is already in latest Thorium-Win7 (now: 122.0.6261.168) as it's based on M122 but the feature is turned off by default via flags. From a desktop user point of view it's 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 even visually incompatible with a compact desktop running Windows 7, Vista or XP.
My suggestions are the following, whichever is easier to implement.
I don't think any desktop user would miss a change that makes their browser look like a dumb tablet.
Chrome Refresh 2023 flags
#chrome-refresh-2023
Chrome Refresh 2023#chrome-refresh-2023-ntb
Chrome Refresh 2023 New Tab Button#chrome-refresh-2023-top-chrome-font
Chrome Refresh 2023 Top Chrome Font Style#chrome-webui-refresh-2023
Chrome WebUI Refresh 2023#customize-chrome-side-panel
Customize Chrome Side PanelThis may not be necessary. It's about a bug that if you don't turn this flag to Disabled, Chrome Refresh 2023 flags are all ignored. See: https://issues.chromium.org/issues/330756862
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: