Enable WebKit sandboxing (and tidy up a bit)

[chorizo.git] / CHANGES

diff --git a/CHANGES b/CHANGES
index 4abfd9b9b53a7a53b5dcf0788fdb075d348e5bb9..2255781898031a4ad863e2833ecb5a1221d05557 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,5 +1,21 @@
 Release history for lariza
 
+next
+  [Changed]
+  - lariza now uses native GTK tabs instead of relying on suckless
+    tabbed. See also:
+    https://www.uninformativ.de/blog/postings/2020-04-26/0/POSTING-en.html
+  - Keyword searches have been removed, as these code paths were
+    unmaintained. See also:
+    https://www.uninformativ.de/blog/postings/2020-05-01/0/POSTING-en.html
+  - The "external URI handler" has been removed, as these code paths
+    were unmaintained. See also:
+    https://www.uninformativ.de/blog/postings/2020-05-01/0/POSTING-en.html
+  - WebKit sandboxing is now enabled. While considered stable, it is a
+    rather new feature. Please report breakages. This also requires you
+    to run at least WebKitGTK 2.26 (released 2019-09-09). See also:
+    https://blogs.gnome.org/mcatanzaro/2020/03/31/sandboxing-webkitgtk-apps/
+
 v20.04  2020-04-22
   [Fixed]
   - Minor fixes to manpages.