-
-
Notifications
You must be signed in to change notification settings - Fork 724
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inform users they need to unblock 3rd party browser cookies in Firefox to make /map work #8230
Comments
I tested this in multiple staging and prod servers and it doesnt happen always, in many cases the error is triggered but for some reason the page still works.. |
In 1 week of bugsnagJS, this error was seen in the browser of 102 users in France, 20 users in AUS and 16 users in UK. |
Could be a specific browser plugin? I use several for blocking ads and cookies... |
This could take a little digging into how to detect that third party cookies are disabled... this answer looks relevant: https://stackoverflow.com/questions/3550790/check-if-third-party-cookies-are-enabled#7104048 At first glance it looks larger than a papercut. |
What website currently does this? @luisramos0, can you name one for us? I think that would be helpful. Otherwise, my vote probably does not count but id say, try not to reinvent the wheel. And the issue should just be closed as a browser specific issue. |
The TypeError mentioned above is from the search bar and is a downstream effect of the map not rendering. It's reproducible in local development by turning off the network and loading the map page. Although users would unlikely reach this error in staging or prod via network failure, it does identify an area we can respond and tell the user 3rd party cookie settings may need to be checked. Opening a PR shortly with a potential solution for further discussion. |
Description
Currently if user has disabled 3rd party cookies, for example in Firefox:
When the user goes to /map the map wont show correctly
And bugsnagJS errors will be created like:
https://app.bugsnag.com/yaycode/open-food-network-js-katuma/errors/5e8c6364df4e9c0017b280c6?filters[event.since][0]=30d&filters[error.status][0]=open
But the user is not informed about this error in any way. So for the user, the OFN map is broken.
We could make a very simple change in OFN to detect this problem and show an error message to the user indicating they should enable third-party cookies if they want to see the OFN map.
All occurrences of this error in bugsnagJS (121 in France) are on Firefox, so this is a Firefox specific issue. The map works correctly in chrome even if 3rd party cookies are disabled.
Acceptance Criteria & Tests
Users who have disabled 3rd party cookies are warned when they visit /map that they can enable 3rd party cookies to see the map.
The text was updated successfully, but these errors were encountered: