[Webkit-unassigned] [Bug 62490] New: accepting cookies

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jun 10 16:22:10 PDT 2011


https://bugs.webkit.org/show_bug.cgi?id=62490

           Summary: accepting cookies
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: New Bugs
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: contact at pagerank-seo.com
                CC: contact at pagerank-seo.com


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 af
 ter 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.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list