From 35b3a029f208648970840686d0a62fb09efaa669 Mon Sep 17 00:00:00 2001
From: bill-auger You're using qutebrowser with the QtWebKit backend. Unfortunately, QtWebKit hasn't seen a release (including security updates)
--since June 2017, and it also lacks various security features (process
--isolation/sandboxing) present in QtWebEngine. QtWebKit lacks various security features (process isolation/sandboxing). Because of those security issues and the maintaince burden coming with
- supporting QtWebKit, support for it will be dropped in a future qutebrowser
--release. It's recommended that you use QtWebEngine instead. It's recommended that you use QtWebEngine instead. Most reasons why people preferred the QtWebKit backend aren't relevant anymore: PDF.js support: This qutebrowser release comes with PDF.js support
--for QtWebEngine. PDF.js support: Supported with QtWebEngine since qutebrowser v1.5.0. Missing control over Referer header: This qutebrowser release
--supports content.headers.referer for QtWebEngine. Missing control over Referer header: content.headers.referer is supported with QtWebEngine since
+-qutebrowser v1.5.0. Missing control over cookies: With Qt 5.11 or newer, the content.cookies.accept setting works on QtWebEngine.{{ title }}
@@ -11,23 +11,20 @@ index 2797ea2..022a458 100644
(Outdated) reasons to use QtWebKit
-
Missing support for notifications: Those aren't supported yet in --Qt, but support is planned to be added in Qt 5.13, released around May 2019.
+-Missing support for notifications: With qutebrowser v1.7.0, initial +-notification support was added for Qt 5.13.0.
- --Resource usage: This release adds the Resource usage: qutebrowser v1.5.0 added the qt.process_model and qt.low_end_device_mode settings which can be used to -decrease the resource usage of QtWebEngine (but come with other drawbacks).
@@ -55,10 +51,8 @@ index 2797ea2..022a458 100644 -rendering. With Qt 5.13 (~May 2019) it might be possible to run with Nouveau -without software rendering. - --Wayland: It's possible to use QtWebEngine with XWayland. Some users --also seem to be able to run it natively with Qt 5.11, but currently, QUTE_SKIP_WAYLAND_CHECK=1 needs to be set in the --environment to do so.
+-Wayland: It's possible to use QtWebEngine with XWayland. With Qt +-5.11.2 or newer, qutebrowser also runs natively with Wayland.
- -Instability on FreeBSD: Those seem to be FreeBSD-specific crashes, -and unfortunately nobody has looked into them yet so far...
@@ -74,15 +68,15 @@ index 2797ea2..022a458 100644 -QtWebEngine being unavailable on Parabola: Claims of Parabola -developers about QtWebEngine being "non-free" have repeatedly been disputed, -and so far nobody came up with solid evidence about that being the case. Also, --note that their qutebrowser package is orphaned and was often outdated in the --past (even qutebrowser security fixes took months to arrive there). You --might be better off chosing an alternative install --method.
+-note that their qutebrowser package was often outdated in the past (even +-qutebrowser security fixes took months to arrive there). You might be better +-off chosing an +-alternative install method. - -White flashing between loads with a custom stylesheet: This doesn't -seem to happen with qt.process_model = single-process -set. However, note that that setting comes with decreased security and -stability, but QtWebKit doesn't have any process isolation at all.
-+release. ++If that bothers you, it is recommended that you use another web browser instead, ++such as IceCat or IceWeasel.
{% endblock %} -- cgit v1.2.3