Hi @JFeltkamp,
I just thought about if COOKiES is already able to block embedded iframe, embed, object, link, img, ... (like Google Maps, OSM, Widgets / Tools)... And if no, how that could be done as there are presumably too many modules and ways Google Maps are embedded?
Some examples are:
So integrations per module could be hard and a lot of work?
Furthermore, we should discuss the same for other map providers like OSM.
Perhaps this might lead to a general submodule providing a text filter which blocks iframes by pattern / host for custom embed cases we can't handle in particular? It should allow defining unlimited providers to block by pattern, category selection and placeholder text.
Of course that won't solve maps generated by modules, just the user defined embeds (but here also other providers)...
Just for raising the discussion so far, as we might run into such cases in the future...
Additionally, the filter should also allow to block external scripts like Flipgorilla:
<div name="flipgorilla" data-id="1234567" style="width: 100%; height: 400px;"><a href="https://www.flipgorilla.com/p/1234567/show" target="_blank">xxxx</a></div><script type="text/javascript" src="//www.flipgorilla.com/fg.js"></script>
Typical way to do this would be by replacing script type with text/plain and adding a class. See for example https://cookie-script.com/how-to-block-third-party-cookies.html
Eventually we need to allow to show / hide a wrapper element (or by id/class) on accept, if it's not only a script, but also a content element, like in the described case. That's quite typical.
Fixed
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.