webkit2gtk (2.24.1-2) unstable; urgency=high

  Since version 2.24.0, i386 builds of WebKitGTK require an SSE2-capable
  CPU. This instruction set was first introduced with the Pentium 4 in
  year 2000. Support for older processors was dropped in WebKitGTK
  upstream and is unfortunately not expected to come back.

 -- Alberto Garcia <berto@igalia.com>  Fri, 10 May 2019 15:40:28 +0300

webkit2gtk (2.20.0-2) unstable; urgency=medium

  webkit2gtk 2.20.0 contains a security feature named Gigacage that
  requires a virtual memory region of several gigabytes and is used for
  variable-length random-access allocations.

  One consequence of this is that webkit-based applications may not run if
  their maximum virtual memory size is restricted (e.g. using ulimit -v).

  If it's not possible to remove the VM size limits the Gigacage can be
  disabled by setting the environment variable GIGACAGE_ENABLED=no. Keep
  in mind that you will be making your system less secure by doing this.

 -- Alberto Garcia <berto@igalia.com>  Wed, 21 Mar 2018 14:14:44 +0200

webkit2gtk (2.10.4+dfsg1-1) unstable; urgency=medium

  Since webkit2gtk 2.10.4, support for GTK+2-based plugins (Adobe
  Flash, Google Talk/Hangouts) has been moved to a separate package
  called libwebkit2gtk-4.0-37-gtk2.

  This removes the GTK+ 2 dependency from the main libwebkit2gtk package
  and makes it much smaller, so if you don't want to use any of those
  plugins you don't need to install this new package.

 -- Alberto Garcia <berto@igalia.com>  Thu, 12 Nov 2015 20:40:18 +0200