The following warnings occurred:
Warning [2] Undefined property: MyLanguage::$archive_pages - Line: 2 - File: printthread.php(287) : eval()'d code PHP 8.2.13 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/printthread.php(287) : eval()'d code 2 errorHandler->error_callback
/printthread.php 287 eval
/printthread.php 117 printthread_multipage



CentBrowser Forum
STABLE version -- 5.1.1130.129 - Printable Version

+- CentBrowser Forum (https://www.centbrowser.net/en)
+-- Forum: Product Related (https://www.centbrowser.net/en/forumdisplay.php?fid=1)
+--- Forum: Release Channel (https://www.centbrowser.net/en/forumdisplay.php?fid=2)
+--- Thread: STABLE version -- 5.1.1130.129 (/showthread.php?tid=6850)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49

RE: STABLE version -- 5.1.1130.129 - QZMTCH - 11-27-2024

(11-27-2024, 11:53 AM)tamer Wrote: Never had any issues caused by this flag, it just enables the newest js features that would be available in the next few releases. I would even make it enabled by default on cent.
I think it would take some time to update. There were many unpleasant changes recently. And the latest stable v130 had some nasty bugs, ex. the Fetch with Promise caused 10-15 requests per query and some other bugs.
considering the fact that the browser developer updates not to the latest versions, but to ~5 versions lower, it doesn't matter  Dodgy

RE: STABLE version -- 5.1.1130.129 - tamer - 11-27-2024

(11-27-2024, 03:33 PM)QZMTCH Wrote: considering the fact that the browser developer updates not to the latest versions, but to ~5 versions lower, it doesn't matter  Dodgy

Well, that single flag would solve most of the issues raised on the forum. I think the modern versioning just confuses many. Previously we had v3.25 and 3.41 released the next year and no one complained and expected some drastic improvements. Check out the latest stable chromeos LTS released just a week ago, it's v126 and not 131.

RE: STABLE version -- 5.1.1130.129 - molio - 11-29-2024

(11-27-2024, 05:20 PM)tamer Wrote: Well, that single flag would solve most of the issues raised on the forum. I think the modern versioning just confuses many. Previously we had v3.25 and 3.41 released the next year and no one complained and expected some drastic improvements. Check out the latest stable chromeos LTS released just a week ago, it's v126 and not 131.
Agreed.
The development based on LTS should be welcomed.

Considering the burden on the Cent developers, the fact that they have to start all over again after a month of development, and the fact that problems can be found in the released Cent, as was the case this May, it makes sense to develop on the stable LTS version.

It is hoped that the occasional “soon” or “ASAP” from the developers will be less than three months away.

RE: STABLE version -- 5.1.1130.129 - filth - 12-06-2024

It looks like it's time to update your browser: at the moment it is no longer possible to log in to https://www.twitch.tv Here is what twitch responds to:
[Image: sshot-1.png]

Changing the user agent does not help. (currently using user agent 131.0.6778.870)

RE: STABLE version -- 5.1.1130.129 - tamer - 12-06-2024

(12-06-2024, 07:09 PM)filth Wrote: It looks like it's time to update your browser: at the moment it is no longer possible to log in to https://www.twitch.tv Here is what twitch responds to:
[Image: sshot-1.png]

Changing the user agent does not help. (currently using user agent 131.0.6778.870)

Works just fine with #enable-javascript-harmony flag. Here's the prOOfs.  Exclamation

[Image: TjBVULk.jpeg]

RE: STABLE version -- 5.1.1130.129 - kopa - 12-06-2024

(12-06-2024, 07:09 PM)грязь Wrote: Похоже, пришло время обновления браузера: в данный момент больше невозможно войти на https://www.twitch.tv Вот что отвечает twitch: Изменение пользовательского агента не помогает. (в настоящее время используется пользовательский агент 131.0.6778.870)
[Image: sshot-1.png]


RE: STABLE version -- 5.1.1130.129 - filth - 12-07-2024

(12-06-2024, 09:42 PM)tamer Wrote: Works just fine with #enable-javascript-harmony flag. Here's the prOOfs. 
Doesn't help. Can you log out of your account and try to log in again? Is that how it works?

kopa The site opens but authorization fails.

RE: STABLE version -- 5.1.1130.129 - tamer - 12-07-2024

(12-07-2024, 01:17 AM)filth Wrote: Can you log out of your account and try to log in again? Is that how it works?

Tried to re-login, works just fine for me. 

[Image: pzq4521.png]

I don't spoof the version, it's a pretty lame solution and makes more harm than solves anything.

[Image: nCRfwZe.png]

RE: STABLE version -- 5.1.1130.129 - filth - 12-07-2024

(12-07-2024, 12:16 PM)tamer Wrote: Tried to re-login, works just fine for me. 

[Image: pzq4521.png]

I don't spoof the version, it's a pretty lame solution and makes more harm than solves anything.

[Image: nCRfwZe.png]
If you do not redo the version, some extensions will not be installed, such as Enhancer for YouTube™

RE: STABLE version -- 5.1.1130.129 - Archer - 12-07-2024

На твич не логинится.
С флагом #enable-javascript-harmony просто висит окно логина и ничего не происходит.
Если почистить куки, то все равно появляется ошибка версии браузера