Thanks for the report! We've had an issue yesterday where we delivered a pre-release version of the ETP list to release clients. This should be fixed now. The pre-release list contains https://yastatic.net/ as an ad tracker. The release version does not. Could you please try the following: 1. Switch to ETP "standard" (if you have previously been on strict) and test again. If you're on ETP If you have been on ETP strict before step 1 please go back to it before testing (2) and (3). 2. Go to `about:urlclassifier` and press the "Trigger Update" button in the table for the "mozilla" provider. Then reload the test page and see if the embed loads properly. 3. Create a new profile (e.g. via about:profiles) and test if the embed loads there. You can always open / revert to your old profile again via that page. Repeat this step with ETP switched to strict.
Bug 1846959 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Thanks for the report! We've had an issue yesterday where we delivered a pre-release version of the ETP list to release clients. This should be fixed now. The pre-release list contains https://yastatic.net/ as an ad tracker. The release version does not. Could you please try the following: 1. Switch to ETP "standard" (if you have previously been on strict) and test again. If you have been on ETP strict before step 1 please go back to it before testing (2) and (3). 2. Go to `about:urlclassifier` and press the "Trigger Update" button in the table for the "mozilla" provider. Then reload the test page and see if the embed loads properly. 3. Create a new profile (e.g. via about:profiles) and test if the embed loads there. You can always open / revert to your old profile again via that page. Repeat this step with ETP switched to strict.