Skip to main content
Topic: affected by chromium dropping support ? (Read 77 times)

affected by chromium dropping support ?

i realy don't know how this works
but are chromium "project", and by extend webkit/blink and QtWeb(kit) connected ?

i ask this, b'coz now chromium dropped support for anything below winblows 10
will this reflect on QtWeb(kit) based browsers or they are unrelated ?

Re: affected by chromium dropping support ?

Reply #1
Depending on which functionality it might affect QtWebEngine, but it wouldn't affect QtWebKit.

 

Re: affected by chromium dropping support ?

Reply #2
and what does Otter use ? :P

Re: affected by chromium dropping support ?

Reply #3
Both. ;) The default is QtWebKit, but you can switch either specific domains or everything to QtWebEngine if it was compiled with support for that. (The reverse might be true as well if you compile it that way?)

Re: affected by chromium dropping support ?

Reply #4
and this is another huge problem to me

i used to use Otter on daily "use", then the builds started to have no more than 3 times a year release,
on main page user see weekly or monthly "reports" but theres nothing to download
i tried once to "build" from source, and i got lost on what the hell ordinary user needs to install full
bag of garbage for something that should be simplified for ordinary user to download a script that would ultimately
either download by itself all needed components and start compiling or whatever...

but honestly because of this i havent used otter in years now...
which is sad..., and whenever some release does gets out, we get it in some shitty 32bit edition -_-