Page MenuHomePhabricator

Thank you cookies not setting on non-chrome browsers
Closed, ResolvedPublic


A donor reported that his browser was not setting Thank-you cookies from the Thankyou page.

User is using Seamonkey with a number of other plugins.

A second wave of testing confirmed correct cookie setting on Edge, Chrome and Firefox.

Will follow up with donor for further debugging.

Event Timeline

Jseddon created this task.Mar 21 2018, 9:17 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 21 2018, 9:17 PM
Ejegg added a subscriber: Ejegg.Mar 21 2018, 9:26 PM

Seems to be working correctly in a non-private browsing session on Firefox 58.0b14.

I deleted my centralnotice_hide_fundraising cookie on enwiki and went to the TY page, then back to enwiki.

The TY page successfully loads the pixels from et al, which come back with set-cookie headers adding the centralnotice_hide_fundraising cookie right back. Then going to enwiki, I see the new cookie is indeed sent with the request.

Testing order:

  1. Load wikipedia page with cookies cleared on in private browsing
  2. Load thank you page
  3. Reload wikipedia
DStrine triaged this task as High priority.Mar 21 2018, 9:32 PM

Update: A second wave of testing showed this isn't as board an issue as first thought.. Cookie seems to setting correctly for majority of browsers. Will follow up with donor and continue to debug.

Phab task to be updated

More notes from the user who reported this in Seamonkey (Version: 2.49.1):

< ejegg> Gabrolf: so were you using private browsing in Seamonkey?
< Gabrolf> No, actually. However it wouldn't be surprising if I had some setting or extension that I interferes with this.
< Gabrolf > Well I have RequestPolicy that initially blocked all those requests to the other domains, but I did try after white-listing them and even after allowing all requests (and I still didn't get the cookie).
< ejegg> Hmm, I'm unfamiliar with RequestPolicy - is that in Seamonkey's about:config, or is it an extension?
< Gabrolf> No it's an extension
< Gabrolf> NoScript is a good candidate for the culprit, I did allow all the scripts I got from that page but it has many features (some which don't give raise to alerts) that might have blocked this.

Jseddon claimed this task.Mar 21 2018, 10:06 PM
Jseddon lowered the priority of this task from High to Lowest.
Jseddon updated the task description. (Show Details)

Are there any standard browsers or setups (without extensions such as those mentioned above) where it the issue has been reproduced? Thanks!!! :)

I'm the donor mentioned above, I subsequently found out that I had simply blocked third-party cookies (which are of course required for this to work) in the browser.

I'm sorry for all the fuss that I may have provoked, after I got the impression that others confirmed the problem I thought it was not something on my part and the third-party setting didn't spring to mind.

I verified that by default, even in Seamonkey, all cookies are allowed.

As I'm at it, in case others who keep third-party cookies blocked end up on this bug report, you can make the feature work by simply allowing them for a moment, refreshing the page and then right away set them to "blocked" again, at least on Firefox the ones that got set up to that moment do not get deleted when you change back the setting.
By the way, the cookie responsible for blocking the banners is centralnotice_hide_fundraising, it gets set for and all the various domains on which fundraising banners are displayed.
For Firefox the setting that I'm referring to is network.cookie.cookieBehavior.

Jseddon closed this task as Resolved.Mar 23 2018, 9:01 AM