Установил версию 5.1.1130.82 и не могу настроить панель загрузки файлов у нижнего края экрана, как это было у меня всегда до этой версии. Выглядело это так    Для этого было достаточно убрать ползунок в настройках - Внешний вид - Показывать кнопку загрузки. 
А теперь панель выглядит только так,       независимо от того, включен ползунок или нет. Вот доказательство    На скрине видно, что ползунок отключен, но кнопка все равно появляется  при загрузке файлов. Я так понимаю это баг новой версии, тогда большая просьба к разработчикам исправить ее, если нет, то прошу помочь с настройкой. Может я чего не доглядел.

moin

weiss jemand wie man die fehlermeldung (nach einem hardcore absturzt stromausfall etc) verhindern kann

hier ein bild:


das diese meldung total verschwinden. und gemäss einstellung letzte seiten wiederherstellen automatisch abläuft. 
bei opera oder auch maxthone gibt es diese art von fehlermeldungen nicht. die letzten seiten werden da automatisch geöffnet.
ich habe wegen dieser meldung via google nach lösungen gesucht. leider führte nichts zum erfolgt nachdem ich gewisse daten änderte im chrome verzeichnis... diese meldung MUSS irgend wie verhindern werden können. es ist ein riesen dilemma für mich, da ich nicht in europa lebe und oft von kurzen stromausfällen betroffen bin und PCs bei mir danach alle mit dieser sinnlosen meldung wieder per klick wiederhergestellt werden müssen..
vielleicht schafft das ein freak durch experimentieren die meldung zu entfernen. falls ja WICHTIG!! mir hier keine lösungsansätze anbieten da. sondern:  mir eine portable version 64bit zu extrahieren (winrar oder zip). mir als download zur verfügung stellen
wer das schafft bekommt ein geschenk von mir. ich arbeite bei der firma pcloud.com (die cloud dienste anbietet wie dropebox und onedrive) und werde dir als "geschenk" ein 500 GB abo auslösen auf deine email adresse  

english:
i want prevent die message "restore page" crashes after a hardcore session.
that this message will completely disappear. and according to the setting, restore last pages runs automatically.
This type of error message does not exist with Opera or Maxthone. the last pages will be opened automatically.
I searched for solutions via Google because of this message. Unfortunately nothing happened after I changed certain data in the chrome directory... this message MUST be prevented somehow. It's a huge dilemma for me because I don't live in Europe and am often affected by short power outages and my PCs then all have to be restored with a click with this meaningless message.
Maybe a freak will be able to remove the message through experimentation. if so IMPORTANT!! I can't offer any solutions here. but:  to extract a portable version 64bit (winrar or zip). Make it available to me as a download
Whoever manages that will get a gift from me. I work for the company pcloud.com (which offers cloud services such as Dropebox and OneDrive) and will send you a 500 GB subscription as a "gift" to your email address

good luck

gruss
tony

moin

weiss jemand wie man die fehlermeldung (nach einem hardcore absturzt stromausfall etc) verhindern kann

hier ein bild:


das diese meldung total verschwinden. und gemäss einstellung letzte seiten wiederherstellen automatisch abläuft. 
bei opera oder auch maxthone gibt es diese art von fehlermeldungen nicht. die letzten seiten werden da automatisch geöffnet.
ich habe wegen dieser meldung via google nach lösungen gesucht. leider führte nichts zum erfolgt nachdem ich gewisse daten änderte im chrome verzeichnis... diese meldung MUSS irgend wie verhindern werden können. es ist ein riesen dilemma für mich, da ich nicht in europa lebe und oft von kurzen stromausfällen betroffen bin und PCs bei mir danach alle mit dieser sinnlosen meldung wieder per klick wiederhergestellt werden müssen..
vielleicht schafft das ein freak durch experimentieren die meldung zu entfernen. falls ja WICHTIG!! mir hier keine lösungsansätze anbieten da. sondern:  mir eine portable version 64bit zu extrahieren (winrar oder zip). mir als download zur verfügung stellen
wer das schafft bekommt ein geschenk von mir. ich arbeite bei der firma pcloud.com (die cloud dienste anbietet wie dropebox und onedrive) und werde dir als "geschenk" ein 500 GB abo auslösen auf deine email adresse  
in diesem sinne
good luck

gruss
tony

Здравствуйте, этот вопрос был отправлен на мою электронную почту с ответом человека, приславшего мне фотографию. Когда я щелкнул правой кнопкой мыши и выбрал «открыть изображение в новой вкладке», загрузка файла началась и не открылась в новом окне. Как я могу решить эту проблему? Версия 5.1.1130.82
https://i.postimg.cc/52192KFd/Zw-X9-R3sbz-Y.jpg

I really appreciate developers of Cent Browser in releasing the latest Version: 5.1.1130.82.
Thanks a million for all your efforts.

After using the latest Version: 5.1.1130.82, I notice that texts in tabs are a bit blurry even if the "DirectWrite" flag has already been disabled.

Please see the attached picture below:
   

Hope this issue can be fixed.

SOS
Help pls
The unloaded tab is loaded when you hover it with the mouse - a mini preview of the window open = tab loaded
Open popup window in tab - inactive, but this window still appears and loads the tab
AT EVERY START-UP BROWSER, and single once
In a session after unloading everything works fine, even the preview of the unloaded tab remains... BUT, at every start browser i needed load and unload ALL TAB it's terrible
I don't need 'Memory saver'(is disable). I unload tabs manually
sry for my terrible Eng... I'm very bad at it

This is a suggestion about refining release cycles of Cent Browser.

According to the History page, Cent is released once a year which also means that it may lag behind with security fixes of other browsers.

Developers could make it more secure and stable by merging (backporting) security and stability fixes to the same Chromium branch, a major release is shipped with. For example, right now the latest Cent Browser is 5.1.1130.82, based on M118 Chromium. Chromium is at M124 and contains multiple security and bug fixes compared to M118. Cent developers could take these and cherry-pick or backport to the M118 branch and release security updates with the fixes only and without any feature updates or moving to another main branch of Chromium.

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.