Closed Bug 1432650 Opened 7 years ago Closed 6 years ago is always blocked by TP because of the entry


(Firefox :: Protections UI, enhancement, P2)




Tracking Status
platform-rel --- ?


(Reporter: francois, Assigned: groovecoder)



(Whiteboard: tp-base [platform-rel-yandex]) is in Disconnect's "Content" category:

and so it should only be blocked when a user enables the "strict" list.

However, the bare domain,, is listed under the "Advertising" category:

and has the effect of also matching URLs under the domain, making the entry in Content ineffective.

We need to report this to Disconnect to see if they could use the fully-qualified hostnames instead of the top-level domain in the Advertising section.

Before doing that however, we should write a script to check whether or not there are other cases like that.
Whiteboard: tp-base
platform-rel: --- → ?
Whiteboard: tp-base → tp-base [platform-rel-yandex]
I've started the code to check whether or not there are other cases where an upper domain is already in a block-list.

Since it's part of it will automatically run on all PRs and fail the PR if a duplicate upper domain exists. I just need to debug its output.
Assignee: nobody → lcrouch
Priority: -- → P2
Is there any progress on the issue? 
I see no activity for almost a month and we still have thousands of users facing the issue with maps.
Luke, am I right in thinking that your results on mean that is the only affected entry in the list?
Flags: needinfo?(lcrouch)
Yes, that's the only affected entry.
Flags: needinfo?(lcrouch)
Hi everyone!
Again no progress for 2 months and Yandex.Maps still unavailable for Mozilla users with tracking protection enabled. 
Am I right that we can recommend our users who need "incognito" mode to switch to other browsers?
We are still waiting on from Disconnect.

FWIW, I haven't seen the end-user bug for this. I created a fresh Firefox profile, running Firefox Nightly 62.0a1 (2018-05-22), and I am able to use without any problems?
(In reply to Luke Crouch [:groovecoder] from comment #8)
> FWIW, I haven't seen the end-user bug for this. I created a fresh Firefox
> profile, running Firefox Nightly 62.0a1 (2018-05-22), and I am able to use
> without any problems?

It would have to be on a third-party domain. If you're doing it on, that's a related domain to (the domain where the blocked resource is hosted) and so we automatically allow it to go through.
Luke, you could try for example

If you visit this URL with tracking protection enabled, map won't load. However, it present w/o tracking protection.

I even encountered it on our goverment site ( and I had to use other browser to change my driving license —  I was blocked on "select police office to visit" step :-) 

So, I think this bug is actually showstopper for using tracking protection in Russia. Embedded yandex map is virtually everywhere.
Another broken site: (one of big shops).
Is there any way I could help or contribute to have this fixed? I could do some coding :-)
It's really most frustrating bug in Fx for me.
Not really. This needs an upstream fix by Disconnect:
Luke, I see that Mozilla actually have some patches on your level for Disconnect lists
May be it could be done on that level for Yandex too?
The issue here is that Yandex *Content* elements (like are served from domains *under* Analytics domains ( (See

If we made a yandex_mapping.json with "" under Content, we would put "" under Analytics, which would result in the same problem.

So, we need Disconnect to enumerate and make the categorical decisions about all the domains, and/or paths. (See
I don't understand. Could we use yandex_mapping.json to map:
to Analytics, 
all other to Content?

I understand that it better be done on Disconnect level, but according to Github thread I don't see them do it anytime soon.
Yes that would be possible. And yes - it needs to be done by Disconnect: they have full editorial control of the block-list.
Luke, sorry to repeat my initial question — if Mozilla patches this list on their level for Google, why it couldn't be done for Yandex?
We could map Yandex domains + paths to categories like we do with Google domains, but Disconnect must decide the domains & paths to include on the list in the first place. The above domains & paths may be comprehensive or they may not, so that's what we need Disconnect to decide.
You don't have bandwidth and/or expertise to decide if paths are correct in first place, do you? And obv. you can't trust random guy from Internet for it.... Have I understood problem correctly? 
Could we get someone from Yandex to give you the list or you couldn't trust them cause of intrest conflict? 

I'm pushing because disconnects is sitting on the bug for half-year and they seems just hope to get Yandex to move their analytics servers to another domains — it's best decision technically, but unlikely to happen over night, and probably will never happen.
That's correct. It's a tough spot. :(
Hi Luke! I've pinged Disconnect team once more and asked about the list of paths they assume to be analytics so you could make a patch. Anyway I'm concerned that tracking black list somehow transforms into whitelist in case of Yandex.  

Also I'd like to point that current settings block only Maps API and several similar widgets. Case is the following:
- all requests (even considered analytics) are allowed on Yandex' own domains;
- Maps API is blocked regardless it doesn't make any requests from analytics list.

As a result in* case none of "tracking" requests are blocked, only API resources loading. You may check it yourself and I hope it would be a reason to exclude* rule.
I've also noticed a Yandex map not showing up on my website in a private tab when tracking protection is off. This applied not just to a script at$_api_success&onerror=_$_api_error, but also to a static map image from (e.g.,53.217362&z=5&pt=45.1,53.19,org&size=650,450&l=map&lang=en_GB). The website shows it to users while the JS version gets initialised.
A breakthrough: we received and merged updated blocklist content from Disconnect that included changes to the yandex domains.

It's been merged, and the updated lists are being served to Firefox clients now. (Clients check for list updates approx. every 30m)

I checked on a Fresh Firefox 63.0.1 and both and are now showing maps!

Marking this RESOLVED:FIXED!
Closed: 6 years ago
Resolution: --- → FIXED
I also confirm that Yandex maps are finally working on my website when Firefox tracking protection is enabled. This applies to JS maps as well as static maps (which I load first to make the website feel faster):

Many thanks for resolving this issue folks, much appreciated! 🎉
Feeling like it's my birthday =)
Great news! Thank you guys!
You need to log in before you can comment on or make changes to this bug.