Message from discussion Getting logged out of applications using Fluid (SSBs)/Webkit
Received: by 10.150.191.15 with SMTP id o15mr938434ybf.25.1230699816134; Tue,
30 Dec 2008 21:03:36 -0800 (PST)
Date: Tue, 30 Dec 2008 21:03:36 -0800 (PST)
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
rv:126.96.36.199) Gecko/2008120121 Firefox/3.0.5,gzip(gfe),gzip(gfe)
Subject: Re: Getting logged out of applications using Fluid (SSBs)/Webkit
From: Benjamin Stein <benst...@gmail.com>
To: fluidapp <email@example.com>
Content-Type: text/plain; charset=ISO-8859-1
Yes, it started happening to me as soon as I upgraded to 10.5.6. I
also upgraded to Safari 3.2.1 (5525.27.1) in the same system update,
so I can't confirm if it's one or the other.
Just some more notes, in case it's helpful:
I do get the logout problem in Facebook, but I'm also getting strange
Gmail functionality. After some period of time, it appears to think
60 seconds" message). And then other times Gmail.app just displays
"Bad Request Error 400". I need to restart the app (reload or new
window doesn't help). This started happening right after my update,
so I can only conclude it's just a different manifestation of the same
On Dec 30, 11:03=A0pm, todd.ditchend...@gmail.com wrote:
> Update folks:
> I have been able to reproduce this same behavior using other webkit-
> based applications on two separate macs. Specifically NetNewsWire and
> Shiira. Both NNW and Shiira use the WebKit located on your system.
> just like Fluid. I *cannot* reproduce this in OmniWeb which ships with
> its *own*, private (presumably custom) WebKit framework.
> In other words, this behavior is *not* specific to Fluid SSBs, but
> rather seems to be affecting any WebKit-based application that uses
> the WebKit framework already located on your system.
> As soon as you perform some network activity in one of these apps, it
> seems to clobber cookie changes you've made in safari. (note launching
> the app is not enough. you have to do something that performs a
> network request... looks like ajax or traditional http requests both
> do the trick). I even used HTTPScoop.app to confirm this. It happens
> immediately after a silent/background ajax request.
> So if this is a bug (and it seems like it probably is), its looking
> like a bug in WebKit. I'm not sure if this behavior is new to 10.5.6,
> or some specific version of WebKit, but I dont recall seeing or
> hearing about this before... plz correct me on that if i'm wrong.