The number of ways to isolate requests is becoming increasingly large, and it is not feasible to keep updating extensions to support all scenarios: - Container tabs (this bug at first, following discussion from bug 1578405) - Private browsing mode (similar, following discussion from bug 1578405 , where `incognito: "split"` is used to force an isolation) - Cache Partitioning (bug 1687569) - (dynamic) First-Party isolation - HTTPS-Only mode (bug 1685862 has some discussion but we need a new bug) - Features tied to first-partiness (e.g. tracking protection, sameSite cookies) It affects APIs that trigger requests, such as: - `browser.downloads.download` - `fetch` / `XMLHttpRequest`
Bug 1670278 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The number of ways to isolate requests is becoming increasingly large, and it is not feasible to keep updating extensions to support all scenarios: - Container tabs (this bug at first, following discussion from bug 1578405) - Private browsing mode (similar, following discussion from bug 1578405 , where `incognito: "split"` is used to force an isolation) - Cache Partitioning (bug 1687569) - (dynamic) First-Party isolation - HTTPS-Only mode (bug 1685862 has some discussion but we need a new bug) - Features tied to first-partiness (e.g. tracking protection, sameSite cookies) It affects APIs that trigger requests, such as: - `browser.downloads.download` - `fetch` / `XMLHttpRequest` There are other APIs where the context may be relevant, such as: - `browsingData` (removing all data associated with a specific origin/partition/whatever form of isolation we have).