mapbox-gl-js version:
https://api.mapbox.com/mapbox-gl-js/v0.24.0/mapbox-gl.js


When I update to a newer version of Mapbox the error is fixed. However updating breaks the geocoder, and the newer version does not support the geocoder (https://github.com/mapbox/mapbox-gl-geocoder/blob/master/CHANGELOG.md) to be placed in a different container as the map.
The map should load properly without returning an error
When the map is being loaded it returns an error:

As far as I understand, this is more of an issue with the new geocoder behavior than anything we should fix on the GL JS side (as you say that the issue was already fixed). So I have to close here, but I'd suggest moving the container outside manually with something like div.appendChild(geocoderContainer — there should be nothing preventing you from doing this.
I updated Mapbox unfortunately I still get the same result. I think when I tested I was testing on an http connection. The error changed a bit because of the updated but still returns dom exception 18:

Could we reopen the issue?
@martinrisseeuw please read the following section of the readme: https://github.com/mapbox/mapbox-gl-js#using-mapbox-gl-js-with-csp
@mourner Thanks for the info. Unfortunately it seems I can't update the Content-Security-Policy response header because the website is hosted by Shopify. When I look at the response headers it should allow https://*.
The issue only appears in: Version 10.0.2 (12602.3.12.0.1) of Safari. Do you have any other suggestions that I can try?
@mourner having the same issue here also on shopify and using mapbox gl js 0.31.
It works fine on Chrome, but fails to load the map in Safari. Could you elaborate on the suggested solution? The link appears to be broken https://github.com/mapbox/mapbox-gl-js#using-mapbox-gl-js-with-csp
That documentation recently moved to INSTALL.md: https://github.com/mapbox/mapbox-gl-js/blob/master/INSTALL.md#using-mapbox-with-csp
Hi @jfirebaugh thanks for your prompt reply. Somehow I do not get past this even if I add the following meta-tag to the header:
<meta http-equiv="Content-Security-Policy" content="default-src 'self' https://* blob: data:; script-src https://* 'unsafe-eval'; style-src 'unsafe-inline' https://*; child-src *;connect-src https://*;">
@felixLam Can you please open a new issue and include a minimal self-contained example that demonstrates the issue?
@jfirebaugh See http://codepen.io/anon/pen/dNZzxO and click settings to verify or modify the meta tag CSP.
Most helpful comment
Hi @jfirebaugh thanks for your prompt reply. Somehow I do not get past this even if I add the following meta-tag to the header: