[Sugar-devel] Browse, vulnerable

[Tony Anderson]

Hi, James

What is needed to provide Browse with WebKit2? I spent almost a year 
moving everything in Karma Learning System from Firefox (distributed 
with some
releases of Sugar) to WebKit because that was introduced as the future 
direction for Sugar. Naturally, I don't want to even think about 
starting over again.
Is anyone working on this? Is this the long-term solution (e.g. good for 
five+ years)?

Tony

On 02/03/2016 09:56 AM, James Cameron wrote:
> An interesting blog post describing the situation with WebKit security
> updates:
>
> https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-security-updates/
>
> Browse in Sugar is without security updates because it depends on
> an old WebKit version of WebKitGTK+, and the great API break called
> WebKit2 has not yet been fixed in a Browse release.
>