QtWebEngine doesn't contain *all* of chromium. It contains Blink; uses the
Skia rendering library over the Qt rendering system; the Chromium networking
stack and cookie management. A more extensive list of features can be found
here: https://doc.qt.io/qt-5/qtwebengine-features.html
Apart from
[[[ To any NSA and FBI agents reading my email: please consider]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> hopefully people migrating to the chromium engine are sympathetic with
> the
On Sat, 14 Jan 2017 20:05:52 -0600
Isaac David wrote:
> It could very well be free by now, but only if you are willing to
> overlook the fact that it's not actually being built from sources.
> The chromium repository still distributes and uses some object
> code,
Le lun. 9 janv. 2017 à 15:24, Hanno Böck a écrit :
I've read through the entire thread now and tried to follow the links,
yet I can't find any evidence for the claim that chromium is nonfree.
It could very well be free by now, but only if you are willing to
overlook the fact
Hanno Böck writes:
> I'd also want to note that there are good reasons why people want to
> move from webkit to the chrome rendering engine. Many applications
> using webkit have been stuck with unfixed security vulnerabilities in
> the past. The chromium engine is well
Hi,
On Sat, 7 Jan 2017 23:15:44 -0300
André Silva wrote:
> Hi guys, since Chromium is blacklisted as nonfree software [0] we
> have a serious issue. KDE is migrating their apps to QTWebEngine
> which contains Chromium as the embed engine inside it. [1]
I've read through
On 01/08/2017 01:06 PM, Adonay Felipe Nogueira wrote:
> I guess that we could contact the KDE project and tell them the issue so
> they can rethink about their move.
Would you like report about it to them? it could be a good idea.
signature.asc
Description: OpenPGP digital signature