mapbox-gl-js version: 1.8.1
browser: Version 80.0.3987.132 (Official Build) (64-bit) macOS Catalina 10.15.3 (19D76)
A cookie associated with a cross-site resource at http://mapbox.com/ was set without the
SameSiteattribute. It has been blocked, as Chrome now only delivers cookies with cross-site requests if they are set withSameSite=NoneandSecure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
-
Display a map in production
Throws warning in console about SameSite attribute cookie and prevents from displaying map.
Thanks for opening this issue, @rafalolszewski94. Would you please provide an example that triggers this console message or point me to a page that you have observed this error? We recommend using https://jsbin.com.
To my knowledge, none of the requests made from GL-JS to mapbox should attempt to set a cookie and should not break as a result of chrome's enforcement of the sameSite guidelines.
But we can certainly double check that assumption.
You can see it here https://dominikkolasa.pl/
I just noticed the same warning today on my Reactjs webapp, appearing on every page on refresh so I guess it comes from one of those two css files:
<link
href="https://api.tiles.mapbox.com/mapbox-gl-js/v1.4.1/mapbox-gl.css"
rel="stylesheet"
type="text/css"
/>
<link
rel="stylesheet"
href="https://api.mapbox.com/mapbox-gl-js/plugins/mapbox-gl-geocoder/v4.5.0/mapbox-gl-geocoder.css"
type="text/css"
/>
Is there any investigation going on this case or is it forgotten ?
This is a warning that only occurs for on browsers where someone has visited and/or signed into https://www.mapbox.com, and not for other users. This can be confirmed by visiting the link in https://github.com/mapbox/mapbox-gl-js/issues/9404#issuecomment-597810206 with an incognito browser or from a Chrome browser that has not visited or logged into https://www.mapbox.com.
Closing here as there is no impact to end users viewing a gl-js map, and there is nothing actionable for this library.
We've changed map to Google embed, that's why it's working now.
Not visiting mapbox.com is not a solution for end users IMHO. Most of them
probably won't visit it, but what if some did?
On Mon, Mar 16, 2020, 08:00 Asheem Mamoowala notifications@github.com
wrote:
This is a warning that only occurs for on browsers where someone has
visited and/or signed into https://www.mapbox.com, and not for other
users. This can be confirmed by visiting the link in #9404 (comment)
https://github.com/mapbox/mapbox-gl-js/issues/9404#issuecomment-597810206
with an incognito browser or from a Chrome browser that has not visited or
logged into https://www.mapbox.com.Closing here as there is no impact to end users viewing a gl-js map, and
there is nothing actionable for this library.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mapbox/mapbox-gl-js/issues/9404#issuecomment-599374704,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJBLIBHY2XLQ4GTJ6337EQDRHXE7PANCNFSM4LFTGKZQ
.
Agreed - relying on users not visiting mapbox.com and saying if they do there's nothing to be done is not really a solution. Cookies on mapbox.com should be structured so that no such problems occur.
Most helpful comment
Agreed - relying on users not visiting mapbox.com and saying if they do there's nothing to be done is not really a solution. Cookies on mapbox.com should be structured so that no such problems occur.