Thread Rating:
  • 2 Vote(s) - 2.5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Cent Browser 3.6.8.99(for Windows) Released
#11
(11-01-2018, 02:09 PM)CentBrowser Wrote: Screenshot tool has been improved in this version, and you can use Alt+I to save full size screen capture now.
If you want to restore old UI, you can change "chrome://flags/#top-chrome-md" to "Normal" or "Hybrid", but we are not sure whether this can work forever.
Some users reported rendering issue with DirectWrite disabled, if you encountered please post your browser version and OS version here.

Release log:
https://www.centbrowser.com/history.html#3.6.8.99

32-bit installer       32-bit portable
64-bit installer       64-bit portable

Here's my testing of rendering issue with DirectWrite disabled (all in a fresh installed virtual machine):
Win7 x86: https://imgur.com/fPLzLY5
Win10 1607 x64: https://imgur.com/r11iuka
I also tested in Win10 1803 but interestingly it ran fine without any issue.

So it seems like it may only happen in older versions of windows?

I haven't tested in 3.6.8.99 yet but every other version after 3.4.3.39 all have this issue for me so I'd think it's the same for 3.6.8.99
which is also why I'm still stuck with 3.4.3.39
Reply
#12
(11-01-2018, 04:58 PM)filth Wrote: On the contrary) 
It is necessary to download) and it plays back ... this window does not appear:

[Image: 2a6ea7c3c5b0409f903a7bdd707d2820.jpg]

OK, we will look into this issue.
And you can also use "Save as" to download m4v file, or press Ctrl+S to save it if it plays in a separate tab.
Reply
#13
(11-01-2018, 10:02 PM)Alex Wrote: I have 3.5.3.50 portable 32 bit (Win 10) and it refuse to update. Why?
[Image: 45.png]

It won't auto update until we push on the server side.
Reply
#14
(11-02-2018, 02:53 AM)m53aal Wrote: Here's my testing of rendering issue with DirectWrite disabled (all in a fresh installed virtual machine):
Win7 x86: https://imgur.com/fPLzLY5
Win10 1607 x64: https://imgur.com/r11iuka
I also tested in Win10 1803 but interestingly it ran fine without any issue.

So it seems like it may only happen in older versions of windows?

I haven't tested in 3.6.8.99 yet but every other version after 3.4.3.39 all have this issue for me so I'd think it's the same for 3.6.8.99
which is also why I'm still stuck with 3.4.3.39

There may be conflict between some Windows feature and our current DisableDW implementation.
But we have tested on 7 computers from Win7 SP1 to Win10 1809, still can't reproduce.
So this is quite weird issue.
Reply
#15
(11-02-2018, 04:13 PM)CentBrowser Wrote: It won't auto update until we push on the server side.
Ok,  I understand. It`s already update to the current version, so everything just fine so far. Thank You.
Reply
#16
I guess we just need to be updated to chrome base version 70, but that will come whenever Smile
Reply
#17
(11-02-2018, 04:16 PM)CentBrowser Wrote: There may be conflict between some Windows feature and our current DisableDW implementation.
But we have tested on 7 computers from Win7 SP1 to Win10 1809, still can't reproduce.
So this is quite weird issue.

Would it help if I share the virtual machines I've tested in?
Reply
#18
tell me how to make this version work in the background. I'm having trouble doing it.
Reply
#19
(11-03-2018, 12:06 PM)m53aal Wrote: Would it help if I share the virtual machines I've tested in?

We have already downloaded that virtual machine and tested, but get no result.
Reply
#20
(11-03-2018, 01:29 PM)Yuriy222 Wrote: tell me how to make this version work in the background.  I'm having trouble doing it.

Sorry but not quite understand.
Do you mean you want to hide the browser window?
Reply


Forum Jump:


Users browsing this thread: 9 Guest(s)