04-22-2024, 01:28 PM
This is a suggestion 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, 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 Cent Browser (now 5.1.1130.82) as it's based on M118 but the feature is turned off by default via flags.
My suggestion is either to keep flags related to Chrome Refresh 2023 or to introduce a configuration option under Settings > Appearance to turn on/off the whole (or parts of this) UI change.
Chrome Refresh 2023 flags
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.
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 Cent Browser (now 5.1.1130.82) as it's based on M118 but the feature is turned off by default via flags.
My suggestion is either to keep flags related to Chrome Refresh 2023 or to introduce a configuration option under Settings > Appearance to turn on/off the whole (or parts of this) UI change.
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 Panel
This 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.
- https://issues.chromium.org/issues/335553327
- https://issues.chromium.org/issues/332574933
- https://issues.chromium.org/issues/332081796
- https://issues.chromium.org/issues/330842283
- https://issues.chromium.org/issues/330743875
- https://issues.chromium.org/issues/330753883
- https://issues.chromium.org/issues/330589210
- https://issues.chromium.org/issues/330443177
- https://issues.chromium.org/issues/330373923
- https://issues.chromium.org/issues/329953462
- https://issues.chromium.org/issues/327022941
- https://issues.chromium.org/issues/41490387
- https://issues.chromium.org/issues/40947720
Negative user feedback
Negative feedback from mostly advanced users who suffered a UX degradation because of Chrome Refresh 2023.
- https://support.google.com/chrome/thread/269780757
- https://support.google.com/chrome/thread/269812926
- https://support.google.com/chrome/thread/269774466
- https://support.google.com/chrome/thread/269868881
- https://support.google.com/chrome/thread/269982965
- https://support.google.com/chrome/thread/269956094
- https://support.google.com/chrome/thread/269946774
- https://support.google.com/chrome/thread/269800018
- https://www.reddit.com/r/chrome/comments...misplaced/
- https://www.reddit.com/r/chrome/comments...to_normal/
- https://www.reddit.com/r/chrome/comments...ze_chrome/
- https://www.reddit.com/r/chrome/comments...ow_to_fix/
- https://www.reddit.com/r/chrome/comments...an_normal/