Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
beta version (5.1.1130.26)
(03-20-2024, 10:31 AM)Spuner Wrote: With the frequency with which Cent is updated, which is once a year. This is not applicable... You are talking about websites here, but you also forget about extensions. If we wait a year for a new version of the browser on a new engine, during this time some extensions will begin to fail on the old engines. I switched from the 102 engine mainly only because, for example, the Checker Plus for Gmail extension stopped supporting the 102 engine. Updates should be released at least once every 6 months.
Yes, we will try to upgrade Chromium version every 4~6 months.
However, new Chromium version also breaks old extensions and old websites.
So there may not be a perfect solution.
Reply
   
(03-20-2024, 04:09 PM)CentBrowser Wrote: Yes, we will try to upgrade Chromium version every 4~6 months.
However, new Chromium version also breaks old extensions and old websites.
So there may not be a perfect solution.
Is there a way to split the screen like in vivaldi or edge?
Reply
(03-17-2024, 03:48 PM)CentBrowser Wrote: Do you mean "scroll the tabs" or "scroll the tab bar"?
Even this option is disabled, the tab bar still can be scrolled with mouse wheel.

   
Reply
(03-20-2024, 04:09 PM)CentBrowser Wrote: Yes, we will try to upgrade Chromium version every 4~6 months.

I really hope these are not just words... Wink
Reply
(03-20-2024, 12:31 PM)QZMTCH Wrote: I use 102 cent, I still haven’t switched to 118 because it’s no better, and I see problems with 102
and believe me, almost all major sites will introduce new JavaScript standards and new CSS functions, and if you don’t update your browser, your site’s layout will be broken (at least)
and yes, extensions are also quite an important thing
There are more and more extensions that not only write a version, but also use the functions of new versions of the engine, and even version 118 is already becoming old

I'm also on version 102 and haven't noticed any major issues. If a particular extension stops working, I revert back to one of the previous versions that worked. So far, I haven't had any display issues with sites – at most I couldn't access some of them, but that was fixed by switching the user agent.
Maybe we're just talking about different things. I don't dispute that something can break, or work incorrectly. But I don't see why I should keep updating my browser or extensions, if everything works fine on previous versions.
Updating CSS rules can cause old websites that haven't been updated for a while to display incorrectly. I don't know any specific examples, but it's possible that it could happen. There's no way to tell for sure, but I can't see any reason why it wouldn't be possible in theory. There doesn't seem to be a middle ground here.
Reply
(03-20-2024, 08:32 PM)Cyanide Wrote: I'm also on version 102 and haven't noticed any major issues. If a particular extension stops working, I revert back to one of the previous versions that worked. So far, I haven't had any display issues with sites – at most I couldn't access some of them, but that was fixed by switching the user agent.
Maybe we're just talking about different things. I don't dispute that something can break, or work incorrectly. But I don't see why I should keep updating my browser or extensions, if everything works fine on previous versions.
Updating CSS rules can cause old websites that haven't been updated for a while to display incorrectly. I don't know any specific examples, but it's possible that it could happen. There's no way to tell for sure, but I can't see any reason why it wouldn't be possible in theory. There doesn't seem to be a middle ground here.
For example, a page https://market.yandex.ru/catalog--med-i-...?hid=91345 looks like this on engine 102 https://i.imgur.com/980oDAH.png and so on 118 https://i.imgur.com/Kbjp6MB.png 
if you don't see problems, it doesn't mean they don't exist

PS https://webextension.org/listing/gmail-notifier.html and about extensions, this does not work on old engines, but what does work (previous versions) their functions no longer work mark as read
Reply
(03-22-2024, 03:30 PM)QZMTCH Wrote: For example, a page https://market.yandex.ru/catalog--med-i-...?hid=91345 looks like this on engine 102 https://i.imgur.com/980oDAH.png and so on 118 https://i.imgur.com/Kbjp6MB.png 
if you don't see problems, it doesn't mean they don't exist

PS https://webextension.org/listing/gmail-notifier.html and about extensions, this does not work on old engines, but what does work (previous versions) their functions no longer work mark as read

You're kinda ignoring what I'm saying. I don't deny there are problems, but I don't think it's necessary to focus on Yandex and other "trend watchers". For example, the Checker Plus for Gmail extension works fine on version 102, with all its features. Why don't you contact Yandex and tell them to stop using those solutions that don't work on older browsers? If tomorrow, they introduce some new features into their Yandex Browser and rewrite all their services to focus on it, will you require Chrome developers to adapt for these changes?
Reply
not working properly

https://musclewiki.com/
Reply
(03-23-2024, 07:12 AM)34ero Wrote: not working properly
https://musclewiki.com/

Hi!
How should it work? That's how I see it: 1, 2.
Reply
(03-23-2024, 09:35 AM)Cyanide Wrote: Hi!
How should it work? That's how I see it: 1, 2.
   

it's fixed now
Reply


Forum Jump:


Users browsing this thread: 8 Guest(s)