Hi, thanks for the report.
The browser difference makes content filtering a plausible cause, especially because Brave enables the EasyList Cookie filter by default. I do not want to call that confirmed yet, though. Firefox no longer has a built-in cookie-banner blocker, so please also tell me whether you use uBlock Origin, AdGuard, or another privacy extension or filter list there.
One important detail is that the two symptoms may have different causes. The floating cookie icon normally appears after a consent decision has already been stored, while the “Accept cookies” button shown over Google Maps belongs to the content placeholder and is separate from the banner. A cosmetic rule hiding the banner would therefore not, by itself, explain why the placeholder button does nothing.
Could you please send me:
- the site URL and the exact page containing the map;
- the FAZ Cookie Manager version;
- the Firefox extensions or filter lists you use;
- any errors shown in the browser Console?
For a clean comparison, please clear the site’s data in Firefox and Brave, temporarily disable uBlock or AdGuard for the site and disable Brave Shields, then reload. A private window alone is not sufficient if an extension is allowed to run in private browsing. If both problems disappear with filtering disabled, that confirms the direction.
If only the banner is being cosmetically hidden, FAZ Cookie Manager 1.29.0 includes Settings > Banner Control > “Keep banner visible against ad blockers”. If the FAZ frontend bundle itself is blocked, “Ad-blocker compatibility mode” is the separate relevant setting. Neither option can make Google Maps load if the browser is directly blocking Google’s request.
Thread Starter
baga
(@baga)
Hi Fabio,
thanks for getting back. Here the details:
- site URL: https://www.residencevillaavisio.it/
- FAZ version 1.29.0
- Extensions: Authenticator, Awesome Screenshot, Save webP as PNG or JPEG, SponsorBlock per YouTube, uBlock Origin, Wikiwand – Wikipedia Modernized
- No errors in console
Already tried “Keep banner visible against ad blockers” but same behaviour.
Thanks for your help!