**Affected versions** * Nightly 78.0a1 (2020-05-20) **Affected platforms** * Windows 10 x64 * Ubuntu 18.04 x64 **Steps to reproduce** 1. Launch Firefox and set "fission.autostart" pref to true in about:config. Restart Firefox. 2. Open a New private browsing window. 3. Go to https://senglehardt.com/test/trackingprotection/test_pages/tracking_protection.html . 4. Open Web Console (Menu -> Tools -> Web Developer). **Expected result** * Two warning messages with the following form should be displayed: * The resource at “<URL>” was blocked because content blocking is enabled. * Request to access cookie or storage on “<URL>” was blocked because it came from a tracker and content blocking is enabled. **Actual result** * Only one warning message is displayed when the "fission.autostart" pref is set to true: * The resource at “<URL>” was blocked because content blocking is enabled. **Regression range** * Will check if one ASAP. **Additional notes** * See attachment "issue.png". * When the "fission.autostart" pref is set to false, both warning messages are displayed in the Web Console: * The resource at “<URL>” was blocked because content blocking is enabled. * Request to access cookie or storage on “<URL>” was blocked because it came from a tracker and content blocking is enabled.
Bug 1639851 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.
**Affected versions** * Nightly 78.0a1 (2020-05-20) **Affected platforms** * Windows 10 x64 * Ubuntu 18.04 x64 * macOS 10.15 **Steps to reproduce** 1. Launch Firefox and set "fission.autostart" pref to true in about:config. Restart Firefox. 2. Open a New private browsing window. 3. Go to https://senglehardt.com/test/trackingprotection/test_pages/tracking_protection.html . 4. Open Web Console (Menu -> Tools -> Web Developer). **Expected result** * Two warning messages with the following form should be displayed: * The resource at “<URL>” was blocked because content blocking is enabled. * Request to access cookie or storage on “<URL>” was blocked because it came from a tracker and content blocking is enabled. **Actual result** * Only one warning message is displayed when the "fission.autostart" pref is set to true: * The resource at “<URL>” was blocked because content blocking is enabled. **Regression range** * Will check if one ASAP. **Additional notes** * See attachment "issue.png". * When the "fission.autostart" pref is set to false, both warning messages are displayed in the Web Console: * The resource at “<URL>” was blocked because content blocking is enabled. * Request to access cookie or storage on “<URL>” was blocked because it came from a tracker and content blocking is enabled.