1846959 - Enhanced Tracking Protection breaks Yandex Maps functionality

Status: RESOLVED FIXED

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

Description

[Alexander Balagurov]

Attachment: FF bug.png

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/116.0

Steps to reproduce:

Go to https://cdpn.io/sashabeep/fullpage/YzRBJaz?nocache=true&view=

Actual results:

Blank page with error in console
"Resource https://yastatic.net/s3/front-maps-static/maps-front-jsapi-v2-1/2.1.79-12002154/build/release/full-70275b62ece2fd2ab62f973df06797d58e0c96b5.js was blocked because of data protextion"

All the Yandex maps widgets on every site does not work for me. Yesterday i've worked with this api and everything works fine, but not today.

I tried incognito mode with the same result, tried to logout at yandex services, tried to disable all the browser extensions, but maps are working only if i untick Enhanced Tracking Protection at the urlbar. Can somebody tell me how to start Firefox on mac with blank profile without losing my current profile to prove is it work or not

Expected results:

Map should be displayed. Attached screenshot from Firefox Developer Edition - it works

Comment 1

[Alexander Balagurov]

Attachment: Firefox developer - works

Comment 2

[Alexander Balagurov]

Attachment: video

Comment 3

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

The Bugbug bot thinks this bug should belong to the 'Core::Privacy: Anti-Tracking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 4

[Emma Zühlcke [:emz]]

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.

Comment 5

[Alexander Balagurov]

(In reply to Paul Zühlcke [:pbz] from comment #4)

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.

Switched to Standard level and it works in both browsers - Firefox and developer Edition. The other two, strict and personal is not. Yesterday it works with personal level with all the checkboxes filled, now it doesnt work even with strict

Comment 6

[Emma Zühlcke [:emz]]

Thanks for confirming! To clarify, does it work in strict after step (2) and (3)?

Comment 7

[Alexander Balagurov]

about:urlclassifier(In reply to Paul Zühlcke [:pbz] from comment #6)

Thanks for confirming! To clarify, does it work in strict after step (2) and (3)?

Using blank profile tes page works at all the levels, i can't understand how it works

Comment 8

[Alexander Balagurov]

(In reply to Alexander Balagurov from comment #7)

about:urlclassifier(In reply to Paul Zühlcke [:pbz] from comment #6)

Thanks for confirming! To clarify, does it work in strict after step (2) and (3)?

Using blank profile tes page works at all the levels, i can't understand how it works

Go to about:urlclassifier showing incorrect address message in both versions - dev edition and default firefox

Comment 9

[Alexander Balagurov]

btw, listing yandex static services as advertisment is insane. This domain is for assets serving like code.google.com

Comment 10

[Emma Zühlcke [:emz]]

(In reply to Alexander Balagurov from comment #7)

about:urlclassifier(In reply to Paul Zühlcke [:pbz] from comment #6)

Thanks for confirming! To clarify, does it work in strict after step (2) and (3)?

Using blank profile tes page works at all the levels, i can't understand how it works

The reason is that we shipped the wrong version of the ETP anti-tracking list briefly. While old profiles may take a while to pick up on the list changes, new profiles get the correct version straight away when they first query the list after creation.

(In reply to Alexander Balagurov from comment #8)

(In reply to Alexander Balagurov from comment #7)

about:urlclassifier(In reply to Paul Zühlcke [:pbz] from comment #6)

Thanks for confirming! To clarify, does it work in strict after step (2) and (3)?

Using blank profile tes page works at all the levels, i can't understand how it works

Go to about:urlclassifier showing incorrect address message in both versions - dev edition and default firefox

Sorry, I made a typo, it's about:url-classifier. Could you please try again? Much appreciated!

Comment 11

[Alexander Balagurov]

(In reply to Paul Zühlcke [:pbz] from comment #10)

(In reply to Alexander Balagurov from comment #7)

about:urlclassifier(In reply to Paul Zühlcke [:pbz] from comment #6)

Thanks for confirming! To clarify, does it work in strict after step (2) and (3)?

Using blank profile tes page works at all the levels, i can't understand how it works

The reason is that we shipped the wrong version of the ETP anti-tracking list briefly. While old profiles may take a while to pick up on the list changes, new profiles get the correct version straight away when they first query the list after creation.

(In reply to Alexander Balagurov from comment #8)

(In reply to Alexander Balagurov from comment #7)

about:urlclassifier(In reply to Paul Zühlcke [:pbz] from comment #6)

Thanks for confirming! To clarify, does it work in strict after step (2) and (3)?

Using blank profile tes page works at all the levels, i can't understand how it works

Go to about:urlclassifier showing incorrect address message in both versions - dev edition and default firefox

Sorry, I made a typo, it's about:url-classifier. Could you please try again? Much appreciated!

Looks like "trigger update" button does some stuff. Now maps widget shows up on the any level of ETP

Comment 12

[Emma Zühlcke [:emz]]

Awesome! Thanks for confirming. Looks like Release isn't affected anymore. I'm keeping this bug for Nightly. It's also less severe given it only affects ETP strict where this kind of breakage is more expected.

Comment 13

[Alexander Balagurov]

(In reply to Paul Zühlcke [:pbz] from comment #12)

Awesome! Thanks for confirming. Looks like Release isn't affected anymore. I'm keeping this bug for Nightly. It's also less severe given it only affects ETP strict where this kind of breakage is more expected.

I want to say thank you very much. In fact, it was technical support, not a problem report. Thank you for your time.

Comment 14

[Emma Zühlcke [:emz]]

Should be fixed in Nightly now too. Could you test this again to make sure it's still working? Much appreciated!

Comment 15

[Alexander Balagurov]

I don't have Nightly version, only regular and Dev Edition. Everything sa ok on both versions

Comment 16

[Emma Zühlcke [:emz]]

Thanks!
Fixed by latest ETP list update.