Default network.cookie.cookieBehavior setting in Beta 64 and Nightly 65 disables background extraction

[biancadanforth]

In Issue #72 , we implemented behavior changes in the extension based on various privacy contexts (#72 (comment)).

One of those changes was to disable background extraction (price polling) when certain cookie restrictions were in place. The current behavior is to disable background extraction for the following values of network.cookie.cookieBehavior:

• 1: 'reject_third_party'
• 2: 'reject_all'
• 4: 'reject_trackers'

A patch just landed in Nightly to set this preference's default value to 4, which means if left as-is, the extension's background extraction and telemetry will be disabled by default in Firefox 64+.

Previously, groovecoder had expressed this requirement for enabling background extraction in this situation:

I think it would be okay to continue price-polling even with cookieBehavior set to 4 so long as there’s an extra opt-in interstitial in the experiment. Something like what I commented in #72 (comment)

@groovecoder , @chuckharmston : Are there any blocking changes needed here for the MVP? Post-MVP?

Engineering-wise, background updates shouldn't violate whatever cookie policy is in place. With groovecoder's help, I compared the Cookies header value between a product page in the content process and loaded for background extraction, and they were the same for a setting of 3.

[chuckharmston]

I don't think this blocks launch, but I would like to make sure this is released before any major marketing pushes past Test Pilot's regular social media and newsletter ones (e.g. if we do a snippet, CFR, or FOMO promo).

I'm going to create a milestone for issues I'd like to hit pre-launch and post-MVP, but wouldn't block launch if there's a pinch. This will go there.