@gdstuart,
Thanks for testing. So what I would do is turn Shields back on so that the issue appears again, then open the Shields panel and disable each protection one at a time until you find the offending protection. That will give us more information to go on.
Changing “Aggressively Block Fingerprinting” to “Block Fingerprinting” solved it. I assume I can leave that setting and it will enable the maps all the time when I’m on the visible.com site. What about other sites that utilize Mapbox? I probably won’t remember this one exception, so I’ll be right back in the same situation six months from now.
@gdstuart,
You can set your global Shields settings such that all sites start with Block fingerprinting by default (Settings --> Shields). But yes you’re right, the settings set in the Shields panel (specifically) is a site specific setting.