1684004 - Can't export Google Contacts on Nightly

Status: RESOLVED FIXED

(Core :: Privacy: Anti-Tracking, defect, P2)

Description

[Francesco Lodolo [:flod]]

Currently on Firefox 86 macOS (Nightly, 20201222215026). I tried exporting my Contact from Google, and after selecting the format (e.g. CSV Google) and clicking Export, nothing happens.

In Google Chrome, a download is initiated right after clicking. I can't see anything useful in the console or the Network panel.

More notes:

• It works normally in release (84) and beta (85.0b4), but it fails also in a new profile with the same Nightly.
• Fission is enabled in my everyday profile, and disabled in the new one, so that's not the cause.
• Tried disabling all experiments, and disabling some options in Tracking Protection, but no luck.

Comment 1

[Francesco Lodolo [:flod]]

I tried with mozregression, going back to mid October (83, 20201015215335), and it still fails. So, it must be some settings that it's on by default on Nightly.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Comment 3

[Hubert Boma Manilla (:bomsy)]

This does not look like a devtools issue

Comment 4

[Dave Townsend [:mossop]]

I see Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified logged when attempting to export so this sounds like an issue with either bad CSP on Google's end or bad interpretation of CSP on our end.

Comment 5

[Christoph Kerschbaumer [:ckerschb]]

Lukas, maybe a problem on Google's end?

Comment 6

[Daniel Veditz [:dveditz]]

That's just a normal CSP warning on Google's part. Their CSP uses strict-dynamic but also includes unsafe-inline for backwards compatibility with older browsers that don't support strict-dynamic. It's just letting a dev know that part was ignored in case they were depending on it. It does not indicate CSP is broken for this page.

Comment 7

[Lukas Weichselbaum]

Unfortunately, it's quite common that these warnings for required fallbacks in CSP lead to confusion.
I'm wondering if we could turn these warnings into informational items in the console. E.g. unsafe-inline being ignored in presence of a CSP nonce or hash is positive for security.

Comment 8

[Daniel Veditz [:dveditz]]

Lukas: that's a good point about our warnings being overly verbose, but our question for you was if you knew why the download itself was broken on Firefox (since the CSP warning is irrelevant).

Comment 9

[Lukas Weichselbaum]

Sorry, my fault.
I don't have much context on Google Contacts, but iirc they're using a "safe downloader" which is using a sandboxed iframe and blobs to allow "safe" downloads. Since this is still working in Chrome, the downloader itself doesn't seem to be broken.
Maybe FF nightly treats blob downloads in sandboxed iframes differently now?

Comment 10

[Tom S [:evilpie]]

I don't have much context on Google Contacts, but iirc they're using a "safe downloader" which is using a sandboxed iframe and blobs to allow "safe" downloads

This is a good hint. So this is caused by bug 1658878 "Isolate BlobURLs per agent-cluster". Disabling the pref privacy.partition.bloburl_per_agent_cluster makes downloads work again.

Comment 11

[Tom S [:evilpie]]

This code definitely should have some kind of warning logged to the console to make this debuggable.

Comment 12

[Johann Hofmann [:johannh]]

(In reply to Tom Schuster [:evilpie] from comment #11)

This code definitely should have some kind of warning logged to the console to make this debuggable.

Filed bug 1686441

Comment 13

[Henri Sivonen (:hsivonen)]

Is this possible to fix on our side with the privacy properties that we want to uphold?

Comment 14

[Dennis Schubert [:denschub]]

Ksenia, can you verify if this is still an issue?

Comment 15

[Ksenia Berezina [:ksenia]]

This is still an issue (if I enable privacy.partition.bloburl_per_agent_cluster). This pref seems to be disabled by default though, so based on that setting webcompat priority as P3.

Comment 16

[Abhishek Madan[:abhishekmadan]]

This issues was caused by the pref : privacy.partition.bloburl_per_agent_cluster. This pref is now disabled by default and current implementation of blob url partitioning using the pref : privacy.partition.bloburl_per_partition_key has been tested and has been shown to not cause breakages with sandbox iframes.