CentBrowser Forum

This is a blatant suggestion on my part  but I see no other way out.

Cent Browser is developing rapidly and has many useful features for end user, unlike Chromium and Google Chrome.
In Cent 1.7.6.15/1.8.9.28 (48/49) no longer work NPAPI plugins. In Chromium 50 already cut code for XP and Vista, so Cent Browser team will be difficult to maintain these OS.

I propose to create on basis of version 1.6.10.21 or older (it does not matter, at discretion Cent Browser team) stable updated build with full support NPAPI and old OS. Analogue Firefox ESR (Extended Support Release), with the gradual addition of new useful features (eg. Startup Command line switches, Tab positioning, etc.).

Yes, two branches of browser development not easy to maintain, but positive effects I can note that in major version Cent, would not need to test and to take care of compatibility with older plugins, certificates, OS, etc. All users that want to use older technology, can be sent on this old version.

Another argument in favor of this build is that many users of Windows 7, 8, 10 need support Unity, Java Applet, Silverlight, many corporate decisions based on NPAPI... but they are now forced to use Firefox. With this build can easily use familiar browser 2-3 years.

Just please don't say just "No". Think about this proposal. Who still uses Windows XP or Vista will not hurry. We can wait patiently. We do not care which version number of Chrome under the hood at Cent Browser - 49, 47, 44 or 35... It is important that browser can properly display and play the web content, which Chrome can not already do.

I wish Cent Browser team every success in their work and hope for a positive decision on this issue 

Thanks for your detailed suggestion.
I think the main problem of this branch is not its workload, but the complexity.
If we keep compatibility with NPAPI and XP/Vista, then it will become very difficult on base version upgrade.
There will be many conflicts when merging source code, and the stability of the browser also suffers.
The best solution is that we release a version for NPAPI and XP/Vista, but we do not release its upgrade version in the future.
Maybe Chromium 49 is the last version suitable to do this.
And we will have a try.

CentBrowser
You have given hope!

Quote:If we keep compatibility with NPAPI and XP/Vista, then it will become very difficult on base version upgrade.
There will be many conflicts when merging source code, and the stability of the browser also suffers.

Yes, in base version is necessary to completely remove support NPAPI and XP/Vista, as it is a waste of time and effort.

Quote:The best solution is that we release a version for NPAPI and XP/Vista, but we do not release its upgrade version in the future.

This version already exists! In 1.6.10.21 good support NPAPI and XP/Vista! Update Chromium version does not need!
It is only necessary to add excellent functions you implemented in next versions (1.7.x - 1.8.x) and also fix minor bugs.
If in future there will be interesting functions, you would add them to this ESR-build.

Quote:Maybe Chromium 49 is the last version suitable to do this.

It would have been nice, but maybe you are just wasting your time... That's why I initially suggest using Cent 1.6.10.21.

We will choose a version to implement ESR.
And for ESR, we would not update it frequently.Maybe update once every half year or longer.
Severe security vulnerabilities will be patched regularly.
The policy is just like Adobe Flash ESR.

Great news!
We believe in success of Cent team!
Thank you very much.

CentBrowser

Quote:The best solution is that we release a version for NPAPI and XP/Vista, but we do not release its upgrade version in the future.
Maybe Chromium 49 is the last version suitable to do this.

ESR version on 49 engine would be the best solution and the latest version, works to XP/Vista, and a version including the latest innovations.

1.6.x is too old.

Thank you!

(04-07-2016, 03:27 PM)DrWatson Wrote: [ -> ]ESR version on 49 engine would be the best solution and the latest version, works to XP/Vista, and a version including the latest innovations.

1.6.x is too old.

Thank you!

Yes, we also think so.But we are not sure whether there will be bugs if use 49.

1.8.9.24 with NPAPI work fine for me.

(04-07-2016, 07:13 PM)DrWatson Wrote: [ -> ]1.8.9.24 with NPAPI work fine for me.

NO, NPAPI on 1.8.9.24 doesn't work correctly!!!
(Tested by me on DjVu Plugin & Foxit Reader Plugin.)

But 1.7.6.15 (and 1.6.10.21, of course) with NPAPI work fine.

(04-07-2016, 09:04 PM)F777 Wrote: [ -> ]But 1.7.6.15 (and 1.6.10.21, of course) with NPAPI work fine.

In 1.7.6.15, there are some problems with Flash, Unity and Java. Sound is, and no video.
In Slimjet 8.x (48) was same error. In version 9.0.2 (49) fixed all, works fine, I checked.

DrWatson
Будь другом, проверяй и тестируй тщательнее... Если у тебя работают 2 внутренних плагина (я даже знаю каких), то это не означает, что с NPAPI в 1.8.9.24 проблем нет. Браузер тупо крашился при использовании Unity, Silverlight или Flash, и автор правильно сделал, что в следующей версии заблочил NPAPI.
Или указывай конкретно, что у тебя работает, а что ты не проверял, т.к. тебе "это нафиг не нужно", или не трахай мозги разработчикам и юзерам.

Про номерки версий даже говорить не хочется... После местного уникума под ником reactor, ты самый версиазозависимый пользователь, уж в русском сегменте точно.
Тебе "шашечки или ехать"?
Для тебя версия трехмесячной давности безнадежно устарела?
Тебе в "устаревших версиях" не хватает свежих гугловских анальных зондов?
Ты что-то знаешь такое о версии с номерком побольше, чего не знает больше никто? Может оперативки стала жрать поменьше или поддержку Висты обрубать передумали?
Может сайты какие требуют только последнюю версию? Примеры конкретные есть?
Объясни, пожалуйста, что полезного появилось в Хроме для конечного пользователя за последние, скажем так, версий 15?

Я серьёзно... потому что песня про "устаревший движок" уже осточертела. Одно дело, слышать это от нубов, им простительно - они воспитаны гуглом и эплом, другое дело от людей, которые давно в теме...

Получится у автора восстановить, то что уже вырезано в 49 Хроме - хорошо. Если потом полгода придется глюки отлавливать, то мне такая ESR нафиг не уперлась. Поэтому и предлагал к нормальной 1.6.х прикрутить новые фичи, а дальше видно будет...