-
Notifications
You must be signed in to change notification settings - Fork 1
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
Adblockers blocking Google Maps will cause the client to hard-fail #2175
Labels
bug
Something isn't working
Comments
Because loading the Google Maps bundle is currently a blocking operation. Therefore, this bug is also a performance bottleneck that I see all of the time |
Related to #451 |
hudson-newey
added a commit
that referenced
this issue
Dec 6, 2024
7 tasks
hudson-newey
added a commit
that referenced
this issue
Dec 11, 2024
* Fixes a bug where if Google Maps failed to embed, the entire site would hard-fail * Move the embedGoogleMaps.ts helper scripts into a DI service * Lazy load google maps to only embed when we need it for the current page (improving performance) * Asyncronously embed google maps (embedding google maps is no longer a blocking operating, improving performance and reducing the scope for bugs) * Adds loading spinner when Google maps is loading * Adds failure state when Google maps fails to load * Re-enables map component tests Fixes: #2175
hudson-newey
added a commit
that referenced
this issue
Dec 11, 2024
* Fixes a bug where if Google Maps failed to embed, the entire site would hard-fail * Move the embedGoogleMaps.ts helper scripts into a DI service * Lazy load google maps to only embed when we need it for the current page (improving performance) * Asyncronously embed google maps (embedding google maps is no longer a blocking operating, improving performance and reducing the scope for bugs) * Adds loading spinner when Google maps is loading * Adds failure state when Google maps fails to load * Re-enables map component tests Fixes: #2175
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have just experienced a case where my adblocker caused Google maps to break / not load.
This caused the entire application to hard-fail.
This highlights an underlying issue with our architecture.
If Google maps fails to load, only Google maps should stop working and should not cause the entire application to crash.
We should instead allow Google maps to fail, and overlay the error message where the Google maps placeholder would be. Displaying an error message such as "Maps failed to load: Request was blocked by ad blocker" (or similar)
The text was updated successfully, but these errors were encountered: