Currently, all the mochitests are running with ETP (Enhanced Tracking Protection). If we switch the protection mode from ETP to TCP for automation tests, **~60 mochitests would fail when TCP is enabled.** We believe most or even all failures were caused because the test behaviors do not comply with TCP's assumption about storage (i.e. storage should be partitioned). It means these failures do not represent malfunction in the product code. However, we need to make all the tests compatible with TCP to guarantee the product quality before shipping TCP to Firefox Release users. Notes: - network.cookie.cookieBehavior = 4 -> ETP (Enhanced Tracking Protection) - network.cookie.cookieBehavior = 5 -> TCP (Total Cookie Protection), aka dFPI - The file `mozilla-central/testing/profiles/mochitest/user.js` overwrites the default value of the cookieBehavior pref.
Bug 1746646 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Currently, all the mochitests are running with ETP (Enhanced Tracking Protection). If we switch the protection mode from ETP to TCP for automation tests, **~60 mochitests would fail when TCP is enabled.** We believe most or even all these failures were caused because the test behaviors do not comply with TCP's assumption about storage (i.e. storage should be partitioned). It means these failures do not represent malfunction in the product code. However, we need to make all the tests compatible with TCP to guarantee the product quality before shipping TCP to Firefox Release users. Notes: - network.cookie.cookieBehavior = 4 -> ETP (Enhanced Tracking Protection) - network.cookie.cookieBehavior = 5 -> TCP (Total Cookie Protection), aka dFPI - The file `mozilla-central/testing/profiles/mochitest/user.js` overwrites the default value of the cookieBehavior pref.