(08-01-2018, 04:03 PM)dmitrah Wrote: [ -> ]Google Chrome 68.0.3440.84 Stable
Hi) Do I have to wait for beta or just release stable? thanks for the browser.
Hi "dmitrah",
Chrome 67 dead? If dead, it is a lot of pity. It has not been a month since the day it was born.
However, there is no need to worry too much, because the Cent technical team will skip version 68, and release version 69 or perhaps 70 to compensate for this sad event immediately. I'm sure of that.
But, not to be too hasty and not to forget the following proverb:
"Haste makes waste"
Greetings,
(08-01-2018, 04:03 PM)dmitrah Wrote: [ -> ]Google Chrome 68.0.3440.84 Stable
Hi) Do I have to wait for beta or just release stable? thanks for the browser.
We will upgrade after the second minor update of Chromium.
cent团队的更新都是在chrome每个大版本+2个小版本更新彻底稳定后才更新，这是很负责任也是一劳永逸的做法，非常赞，而且很高效
(07-24-2018, 06:37 PM)piliq Wrote: [ -> ]I have the same problem with pages too... "Опаньки" in russian. But when the flag "disable-direct-write" is "ENABLED" everything works fine. So i returned to very stable 3.0.4.29 version. It seems to be a problem in Directwrite disabled...
Yes, DiretWrite is the cause of page crush, especially in background... IMHO - 99%
(07-29-2018, 03:30 PM)CentBrowser Wrote: [ -> ]Please try adding "Startup command line":
--no-sandbox
It works! Thanks! But, how can i remove "you are using an unsupported command-line flag no sandbox" when the browser starts?
But, another thing. There is appearing black cmd window for half second on many sites with no sandbox
(07-17-2018, 05:54 AM)ufuksarp Wrote: [ -> ]Anything text rendering related in this build? I'm still on 3.0.4.29.
Same here.
Nothing but DirectWrite problems with the releases of the browser ever since.
If it's not crippling rendering issues, it's different kerning which bugs out my eyes compared to the older versions.
Here's a comparison between 3.0.4.29 and 3.5.3.50
[
attachment=595]
[
attachment=596]
Font looks bolded in 3.5.3 with some weird discoloration outline, kind of like what chromatic aberration does.
Tested 3.4.39 and it's the same. However, the kerning is slightly different with letter spacing in the latest release. Example: Letters after an f are spaced in 3.5.3.50. I think it looks better because the letters were normally mashed together, but the overall bolding of the font is just... off to me.
And to think none of this would've been a problem if developers just left things alone (deprecated) instead of ripping things out of software. Thanks Google!
(08-04-2018, 07:07 AM)piliq Wrote: [ -> ]But, another thing. There is appearing black cmd window for half second on many sites with no sandbox
Yes, this is an issue from long time ago.
(08-04-2018, 08:04 AM)DAOWAce Wrote: [ -> ]Same here.
Nothing but DirectWrite problems with the releases of the browser ever since.
If it's not crippling rendering issues, it's different kerning which bugs out my eyes compared to the older versions.
Here's a comparison between 3.0.4.29 and 3.5.3.50
Font looks bolded in 3.5.3.
Tested 3.4.39 and it's the same. However, the kerning is slightly different with letter spacing in the latest release. Example: Letters after an f are spaced in 3.5.3.50. I think it looks better because the letters were normally mashed together, but the overall bolding of the font is just... off to me.
And to think none of this would've been a problem if developers just left things alone (deprecated) instead of ripping things out of software. Thanks Google!
This may be caused by gamma change.
https://www.centbrowser.com/forum/showth...76#pid8776
(08-04-2018, 04:32 PM)CentBrowser Wrote: [ -> ]This may be caused by gamma change.
https://www.centbrowser.com/forum/showth...76#pid8776
Something like this?
https://bugzilla.mozilla.org/show_bug.cgi?id=1277404
Is it possible to provide the user a way to configure this, or is it limited to source code only changes?
I find it looks worse and it causes my eyes to react strangely to reading it.
Many other users seem to be reporting they dislike the changes as well.. and are annoyed that Disabling DirectWrite has been problematic ever since the release of 3.1.5.52.
Here's a comparison of how things look on my (older) PaleMoon install:
[
attachment=598]
Aside from some spacing changes, the font renders
identically to Cent 3.0.4.29.
And for further comparison, Chrome v51:
[
attachment=599]
Identical.
The sole reason I switched to Cent was because of the ability to disable DirectWrite and keep the same font rendering. DirectWrite causes me to suffer eye strain trying to read text. No other browser besides Firefox lets you disable DirectWrite (but Firefox is full of a bunch of other issues, and I switched to Pale Moon because of the Australis UI update, so using that wasn't a viable option).
We can't stay on 3.0.4.29 forever; some web stuff is looking for newer Chrome versions and there's improved tech in later versions, so I'm really hoping this stuff can get fixed/improved soon.. it's been nearly 9 months.
Edit: Yeah, suffering compatibility issues saying on this older version. Maybe slightly 'bolder' text isn't as bad as being insecure and incompatible with stuff.. but boy does it suck to look at. Not as bad as directwrite, but meh.
Edit2: No wait, after reviewing my screenshots again there is some clear chromatic aberration issue going on with the 'bolder' rendering. It does look pretty bad and negatively affects my eyes.