Bug 62490 – accepting cookies

• Status: RESOLVED
• Resolution: WONTFIX
• Component: New Bugs

[Robert Visser]

On a number of sites where having cookies enabled is a requirement to post, I have been having a recurrent issue. I've experienced this on Twitter and Facebook as well as with the Google URL shortener. Generally, I have cookies enabled and Private Browsing off. However, when I suspect a new follower of sending spam I do enable both. Once I've verified the link I'd wanted to check was or was not spam, I turn Private Browsing off and set the Accept Cookies to Only from sites I visit. What has been happening with Webkit Nightly builds r88232 -- r88541 is that once I return to Twitter to send a Tweet, Facebook to send an Update, or to use either's API to login to a third party tool or extension I receive an error message. I've found that upon clearing the cache and reloading the page I can proceed as normal. Quitting and restarting Webkit also works if at the time restart is implemented the Preferences are set to enable cookies. If I have to go to Preferences to enable cookies after a restart the issue of having to clear the cache and reload the page is still present.

With Google's URL shortener the issue is that although the tool will produce shortened URLs it doesn't provide a tracking record unless cookies are enabled. Hence, when this issue occurs there is no tracking unless I've remembered to clear the cache and reload the page or have quit & restarted the browser before shortening a new URL.

It appears to me that the issue is that the Preference setting to re-enable cookies is either not turning them back on or at least isn't clearing the Never Accept cookies setting.

I've also found this to be the case when placing comments on articles on searchengineland.com, aimclear.com and readwriteweb.com. In the case of AimClear the login was w/ the Facebook API. WIth both Search Engine Land and ReadWriteWeb the login was through the Twitter API.

Next time it happens I'll post a screen grab of the error message.

[Robert Visser]

Created attachment 96838 [details]
Screen shot of an error message attempting to send a tweet. Cleared the cache and re-laoded the page, Tweet was sent.

Error occurred again attempting to send a Tweet. Attached is the error message. Had initially thought this was a Twitter thing. But, when it occurred on Facebook and when making comments on sites where the login was via the Twitter or Facebook API, I began to think it was Webkit related. Incidentally, while it does occur with both the recent Webkit Nightlies and Safari 5.0.5, it doesn't occur (or hasn't yet) with Chrome 12.0.742.91.

[Ahmad Saleem]

Twitter (now X) and Safari / WebKit has now evolved over the years and if there are still errors, we have coverage through WPT and other test to figure out the issue.

If it was an issue, it might not exist today or if it is - we might have newer bug reports with reproducible test reports. Without test case, this is not actionable and also since the site has changed and have login mechanism (so we can do 'Wayback Archive' route to find reduction).

Marking this as 'RESOLVED WONTFIX' because it was never confirmed.