09-10-2022, 08:42 PM
(08-11-2022, 03:18 AM)tamer Wrote: Happens when DirectWrite is disabled and GPU rasterization enabled.
(08-11-2022, 03:48 PM)CentBrowser Wrote: You are right.
Now DisableDW is incompatible with GPU raterization.
(08-19-2022, 10:25 AM)tamer Wrote: Can you check what patches GDIChromium have applied? https://github.com/GTANAdam/GDIChromium
Somehow it seems it does work with GDI.
Please check out this heavy ugly monster site: https://www.tabnine.com/pricing
Video (Cent):
https://www.veed.io/view/e69b2feb-29d5-4...204f16fd23
But if it's hard to implement I'd rather choose DisableDW option over rasterization.
(08-22-2022, 02:19 PM)CentBrowser Wrote: GDIChromium patch disables sandbox for renderer process.
This is an important feature.
So we will not adopt it.
Well this is a big yikes.
Having to disable GPU rasterization is a problem, as there's a lot of GPU accelerated content on the web these days, and this option is really old (v37)
Obviously, enabling DirectWrite is a non-solution; this the reason a bunch of us have been using Cent for years. GDIChromium would be a good alternative.. if we could use it in other browsers, as there's no way I'm ever installing native Chrome again. It's either Cent or Vivaldi.
Either way, we can still control this sandbox thing with --disable-features=RendererCodeIntegrity , and disabling it is pretty much required to get MacType working in Chromium. For someone like me, it doesn't really pose a security risk as I vet everything I visit beforehand. The general populace? Who knows, but using a custom fork of a browser is already putting the userbase into "power user" territory.
Anyway, it's nice to see Cent finally being updated after all this time, but migrating all of Cent's features to Chromium's current codebase is gonna be a nightmare, as many users have already shown pointing out numerous bugs. I myself am turned off by any UI changes, but I'll be waiting until bugs are ironed out in the stable release before testing how much of a departure the newer version is compared to my 3.0.4 and deciding if it's worth the hassle of not switching to Vivaldi to run things that are broken in 3.0.4.
As an aside, any plans to introduce a feature to adjust history retention? Losing things after 3 months has been a thorn in my side ever since switching to Chrome. Vivaldi has an option for infinite retention, but I'd be fine with 1-2 years if a compromise has to be made due to access times to the history database.
