STABLE version -- 5.1.1130.129

[QZMTCH]

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 

[tamer]

considering the fact that the browser developer updates not to the latest versions, but to ~5 versions lower, it doesn't matter 

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.

[molio]

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.