Google Chrome 80 Release and SameSite Cookies Behavior
The Chrome 80 release, scheduled for February 2020, changes the default cross-domain (SameSite) behavior of cookies. For more information on this release, see this blog post from Chromium.
Impact on Cobrowse
Glance's core cobrowsing functionality does not leverage cross-site cookies, so it is unlikely this change will cause an issue.
If you want to test in your own site, set "SameSite by default cookies" to Enable in "chrome://flags" and run a test session.
If you see warnings or errors in your console during a cobrowse session related to cross-site cookies from glance.net, it's likely because you have previously visited our website and therefore have some cookies from glance.net in your browser. Those cookies are not needed for cobrowse.
To prevent the console errors from displaying, you can either:
- Delete your glance.net cookies before starting cobrowse. Or,
- Run the cobrowse session in an incognito window, the warnings should no longer appear.
Impact on Glance for Salesforce
Salesforce Orgs on the Winter 20 release will see negative impacts to some Salesforce integrations. This is not isolated to Glance, and Salesforce is aware of the issue and has a fix in place for the Spring 20 release. See this Salesforce help article for more information.
According to Salesforce, all orgs should be upgraded to the Spring 20 release before the changes in Chrome happen, and therefore there should be no issue with the Glance for Salesforce package.
If for some reason the Chrome changes happen before all Salesforce orgs are updated, there are some workaround options:
- Agents could manually revert the change in Chrome to the previous setting
- Agents could (temporarily) use a different browser, like Firefox