Quoth Bjartur Thorlacius:
> On 4/7/11, Adam Strzelecki wrote:
> > (2) surf-2-delete-_SURF_GO-once-received.patch
> >
> > This xprop (atom) may be used to tell *surf* to go to specific URL. It is
> > safer to remove this atom just after it is set in case we send some URL
> > containing passwords or
On 4/7/11, Adam Strzelecki wrote:
> Below you will find patches for latest HG head of *surf* which I am using in
> my project using integrated Linux station.
>
> (1) surf-1-respect-GNOME-URL-handlers.patch
>
> This patch makes *surf* respect URL schema handlers registered in
> GNOME/Gtk/GConf, whe
>> Anyway _SURF_URI will represents current page URL, so keeping _SURF_GO makes
>> no sense. In our case it is matter of safety to not expose this one.
>
> Cool, good idea. Can't _SURF_URI have login/password info in
> too (I haven't checked)?
AFAIK no, that one is taken out from WebKit (webkit_
On Thu, Apr 07, 2011 at 02:15:11PM +0200, Adam Strzelecki wrote:
> (2) surf-2-delete-_SURF_GO-once-received.patch
>
> This xprop (atom) may be used to tell *surf* to go to specific URL. It is
> safer to remove this atom just after it is set in case we send some URL
> containing passwords or auth
Below you will find patches for latest HG head of *surf* which I am using in my
project using integrated Linux station.
(1) surf-1-respect-GNOME-URL-handlers.patch
This patch makes *surf* respect URL schema handlers registered in
GNOME/Gtk/GConf, when requested url is using other schemas than h
