Bug 3710 - Fancy plugin: Upgrade to webkit2 ?
Summary: Fancy plugin: Upgrade to webkit2 ?
Status: RESOLVED DUPLICATE of bug 2371
Alias: None
Product: Claws Mail
Classification: Unclassified
Component: Plugins/Fancy (show other bugs)
Version: 3.14.0
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2016-10-09 11:57 CEST by Klaus Kusche
Modified: 2016-10-09 14:36 CEST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Klaus Kusche 2016-10-09 11:57:16 CEST
Webkit 2.4.x (the last release with webkit1 api support)
is deprecated, unmaintained for almsot 3 years, does not support gtk3,
and has not even received security fixes for quite some time.

Any chance to switch to webkit versions based on the current webkit2 api?
Comment 1 Paul 2016-10-09 13:46:02 CEST
newer versions of webkit api do not support GTK 2, only GTK 3. Claws Mail is GTK 2.
bug #2371 is RFE for 'port to gtk 3', when that happens the fancy plugin will have to be updated, so this separate RFE doesn't make sense. Therefore I'm closing it as a duplicate.

*** This bug has been marked as a duplicate of bug 2371 ***
Comment 2 Klaus Kusche 2016-10-09 14:14:19 CEST
This is not just a RFE. It is a security problem:

As far as I know, up to now close to 200 security fixes have been committed
to the webkit2 versions which have not been applied to 2.4.x (i.e. webkit1).

And there is a definite statement of the webkit development team
that there will be no security backports to old webkit versions.
See e.g. 
https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-security-updates/

The linux distribution I use is already discussing if and when webkit 2.4.x 
should be dropped for security reasons.

If claws really wants long-term gtk2 support,
I think it would have to switch from webkit to cef for html mail support.
Comment 3 Paul 2016-10-09 14:36:51 CEST
(In reply to comment #2)
That is now a different issue. Re-closing.

*** This bug has been marked as a duplicate of bug 2371 ***