Thread Rating:
  • 5 Vote(s) - 2.6 Average
  • 1
  • 2
  • 3
  • 4
  • 5
STABLE version -- 4.2.10.171
(09-13-2020, 05:47 PM)cb-user Wrote: Even the Windows version cannot be determined? This was in the younger versions of the browser.
And please explain what this actually means:
1. Version - ca97ba107095b2a88cf04f9135463301e685cbb0-refs / branch-heads / 3538 @ {# 1094}?
2. Options - d74ef32b-c7113149?
What do these sets of numbers stand for?
1 is tag information in Git repository.
2 is Chromium field trial parameters.
Reply
(09-20-2020, 09:31 AM)CentBrowser Wrote: 1 is tag information in Git repository.
2 is Chromium field trial parameters.

1. Why information about tags on GitHub is not available in all browser versions?
2. Why is the Windows version not defined correctly in all browser versions?
3. Why are the chromium field trial parameters not available in all browser versions?
Reply
Hi. Are there any updates about the next release date?
With love from Russia)
Reply
(09-20-2020, 06:54 PM)xghoster Wrote: Hi. Are there any updates about the next release date?

Even if they say anything about a release date, it's extremely hard to believe as every month they have said that the update would come has been completely false. Honestly you might as well look into a different browser as you have a better chance of finding one that is up to date and will stay updated better than this browser.
Creator/Maintainer of the CentBrowser Chocolatey Package
Reply
And yet again a question for the developer:

Why not just close the holes and vulnerabilities with security patches in time without switching to another kernel? How the 360 Extreme Explorer developers do it. At the same time, bring one of the best and most problem-free Chromium engine to perfection.
Why can't you follow this path?

Why is this constant race for the numbers of new versions?!!
Reply
(09-20-2020, 08:17 PM)cb-user Wrote: And yet again a question for the developer:

Why not just close the holes and vulnerabilities with security patches in time without switching to another kernel? How the 360 Extreme Explorer developers do it. At the same time, bring one of the best and most problem-free Chromium engine to perfection.
Why can't you follow this path?

Why is this constant race for the numbers of new versions?!!

I totally agree with cb-user.
A chromium-based browser doesn't mean it must be based on the NEWEST chromium.
Reply
That 360 browser is too bloated.. but compared to Cent Browser, that beta based on chromium 86 was so darn fast. the #disable-direct-write worked perfectly fine with MacType.
I'm not far from having #disable-direct-write fully implemented, by the way.
Reply


Forum Jump:


Users browsing this thread: ttomomo, 4 Guest(s)