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

• #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
  

• 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
  

• 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/
  

This is a problem that I've had with using Cent browser as a maximized window for as long as I can remember. I had hoped that the new version 5.1.1130.82 might have resolved the issue, but it seems to persist...

The problem: when using Cent browser as a maximized window with several open tabs, if the selected tab is *not* the tab furthermost to the right, then there will be a pixel-error between the furthermost (not-selected) tab to the right, and the title bar. Se my uploaded picture for clarification.



This problem is not present when using Cent browser as a restored window.

I haven't seen this problem being addressed in the forums - if it has, I apologize.

Does anyone have an idea what might cause this error? The error is not present when using either Google Chrome, MS Edge or Supermium.

This is a feature request to keep ManifestV2 extension support.

Google has already announced the switchover to ManifestV3 is going to happen this June (2024). It's happening in two months.

uBlock Origin will not be ported to ManifestV3 because the new API doesn't have the features to allow that. uBlock Origin Lite, a ManifestV3 port, has very limited features and can't be a decent substitute of the original ManifestV2 uBlock Origin. I think uBlock Origin is the most important extension for an advanced user. It has many features and deep level of configurability, even via group policies (automatic deployment).

There might be other extensions as well that can't migrate to ManifestV3 for the same reason, so that's why it would be important for a browser like Cent, aimed for Advanced users, to keep ManifestV2.

The code will be in Chromium until 2025 June as enterprise deployments can keep V2 extensions via a group policy. I think one year is enough to figure out how to have a continued support for ManifestV2 extensions thereafter. Firefox has already announced to keep ManifestV2 support, so Cent keeping it could guarantee that we'll not lose any users in favor of Firefox.

If I go to https://www.centbrowser.com/ old version 5.0.1002.35402.354 will be shown and downloaded, which is incorrect. It's a year-old version built on 2023-05-21.

However, if I go to page https://www.centbrowser.com/index.html the latest version will be shown, which is correct.

I suppose that this is some improper linking of index.html and the main page (when requested URL doesn't explicitly refer to index.html).

The search result stopped opening in a new background tab. Opens in a new active tab, regardless of settings.

Hello, recently I got an HDR monitor and screenshots in browser are too bright, in the original Chrome browser screenshots work properly.
Changing force color profile flag to Display P3 helps, but then hdr stops working for hdr videos in browser at all

Example:
   

Release log:
https://www.centbrowser.com/history.html#5.1.1130.129

If some extensions require higher Chromium version, you can try finding an older version in Crx4Chrome or here for now.
Due to changes in data format, if you upgrade to this version and then revert to an older version, your saved passwords may not be visible. Therefore, it is recommended that you export your passwords in advance if you need to revert.


SHA256 values:
64-bit Installer: 3f09c729af863f1e7430f62bc2f387d320483d0b760bfab68acbcd1751a01a6f
64-bit Portable: 2a4e5859cb1bbce799fdd59e4fceae3a9e95bba7e44745dee71a9199bffcd072
32-bit Installer: 160b6c5e86fcfb9d0c946e657a0d2b957c5b2f83cc2cf631c3ffc90b25cd8791
32-bit Portable: 1399cfec3078149f317ddb4b3d1ee18b1dd41b2ea406976d4eaebf9371b50b82

Здравия желаю!

I used to the full-screen mode on F11... but Cent doesn't have that (i do not have)

Is it possible to add this mode to the hotkey menu?

Thanks!

First of all
Thanks alot for creating a beautiful portable browser where chrome profile login and google account remains intact even if we change the pc.

My only concern is that It really irritates me to see so much speed dial or homepage shortcut at once i do not like the shortcut plus the bookmark u send us by default.

Now, i remove each one manually when i extract cent browser 
but if i create a new user profile i need to do it all over again.





THIS IS REALLY IRRITATING 

Please help me 
Please teach me which files to remove /replace or what to do to get those shortcut removed without me manually removing them one by one

If i do not see the shortcut in my homepage that would be amazing

RUS:

Привет, HDR не работает в последней бете, я думаю это связанно с неработающим флагом Force Color Profile.

ENG:

Hello, HDR doesn't work in the latest beta, I think this is due to the not working Force Color Profile flag.

UPD:
RUS: А еще в последней бета-версии, когда у меня включен HDR в Windows, все видео в браузере перенасыщены в течение первых нескольких секунд при запуске.
ENG: And also on the latest beta when I have HDR enabled in Windows, all videos in the browser are oversaturated for the first few seconds when I start it.

Attached Files

Thumbnail(s)