Hello Centbrowser team,
Hope you're doing well.
I'd like to expose a new problem with Centbrowser. Since some days, I had really strange behavior with ads, particulary on twitter and mgnet.com. In fact, I noticed this some days ago, when ublock origins was updated on april 18. My guess is that some changes are (sadly) only compatibles with an updated Chromium core OR maybe centbrowser have problems with these changes.
my setup :
twitter :
mgnet.com :
(These are only some examples...)
The only way I found to avoid this : using (temporary) another adblocker (Adguard Adblocker), but it's not as great/useful as uBlock Origin, so I really hope a new revision will come, free of this bug
ps : this thread is not intended to ask you when a new revision will come...but to inform you about this bug so it can (hopefully) be resolved before a new release.
Hope you're doing well.
I'd like to expose a new problem with Centbrowser. Since some days, I had really strange behavior with ads, particulary on twitter and mgnet.com. In fact, I noticed this some days ago, when ublock origins was updated on april 18. My guess is that some changes are (sadly) only compatibles with an updated Chromium core OR maybe centbrowser have problems with these changes.
my setup :
- Centbrowser x64 5.0.1002.295 (installed) + ublock origin 1.49.0 + antiadblock killer 10.0 + all good filters (the ones coming natively with the extension + antiadblock killer one)
- catsxp + exactly the same setup
twitter :
- CB → ads are not filtered. one ad every three messages
(people using this without adblockers are crazy, seriously !)
- catsxp → no problem, all ads are filtered
mgnet.com :
- CB → a lot of scam, aggressive ads, etc.
- catsxp → no problem !
(These are only some examples...)
The only way I found to avoid this : using (temporary) another adblocker (Adguard Adblocker), but it's not as great/useful as uBlock Origin, so I really hope a new revision will come, free of this bug
ps : this thread is not intended to ask you when a new revision will come...but to inform you about this bug so it can (hopefully) be resolved before a new release.