Repository navigation
[google_maps_web] Migrate legacy Markers to Advanced Markers. #130472
Description
Is there an existing issue for this?
- I have searched the existing issues
- I have read the guide to filing a bug
Use case
The following deprecation notice is starting to show when using regular markers:
As of February 21st, 2024,
google.maps.Markeris deprecated. Please usegoogle.maps.marker.AdvancedMarkerElementinstead.At this time,
google.maps.Markeris not scheduled to be discontinued, butgoogle.maps.marker.AdvancedMarkerElementis recommended overgoogle.maps.Marker.While
google.maps.Markerwill continue to receive bug fixes for any major regressions, existing bugs ingoogle.maps.Markerwill not be addressed.At least 12 months notice will be given before support is discontinued. Please see https://developers.google.com/maps/deprecations for additional details and https://developers.google.com/maps/documentation/javascript/advanced-markers/migration for the migration guide.
We should explore ways to use AdvancedMarkerElements instead of Markers.
The web plugin uses (now) Legacy Markers, which aren't very powerful compared to their mobile counterparts.
Users have complained about the lack of customization, like:
- size
- hue rotation (different colors)
- marker rotation (actually rotate the marker around its center)
Proposal
Migrate to Advanced Markers:
Activity
stuartmorgan-g commentedon Jul 13, 2023
(Things entirely internal to one platform's plugin implementation fall under
team-thatplatformin the new world order.)ditman commentedon Jul 13, 2023
Nobody has asked for this yet (directly), so triaging low-ish.
raphael-bmec-co commentedon Oct 12, 2023
I'll directly ask for this so we can bump it up the priority list. The behaviour of markers on the web at the moment is very limited and I have other open issues that would be resolved by this.
ditman commentedon Apr 27, 2024
Note that migrating to the advanced markers will require creating a Map ID, according to the migration instructions:
raphael-bmec-co commentedon Apr 27, 2024
@ditman any chance of bumping the priority now based on the depreciation 🙏?
We've got a horribly hacky fork of the whole flutter repository going on to work around the patching implementation of web support 🙈
PatrickKanne commentedon Jul 4, 2024
ditman commentedon Jul 9, 2024
No progress on this one yet, my first priorities are to enable the flutter/packages packages to compile with
--wasm, before adding new features. Maps is close, but still pending a migration to the v8.0.0 of a14n's js-interop library.Rexios80 commentedon Jul 22, 2024
For anyone tracking this, there is an in-progress PR for that migration here: flutter/packages#7077
Update `firebase.json` with `/go/google-maps-advanced-markers` for Ad…
aednlaxer commentedon Sep 23, 2024
Sharing a design doc for adding advanced markers support to
google_maps_flutter: #155526That should also resolve the legacy markers deprecation notice on web
cedvdb commentedon Nov 4, 2024
Not directly but #24213 is the 9th most upvoted issue, advanced markers may cover that issue
ditman commentedon Nov 5, 2024
This could maybe be done with a multi-view embedding on the web, I'm not sure about other platforms, and also not sure about the compositing of views, if we want to get super fancy :S
cedvdb commentedon Feb 18, 2025
We are now past (almost) the 12 months notice.
ugh perfs.. Practically speaking there are some overlaps on some of the use cases advanced markers provide and what people actually want in that linked issue (said differently, it's not flutter widgets but it solves some issues found in that thread).
It's also the same idea behind this issue, so the real demand is higher than what may appear on the upvote count of this specific issue
[google_maps_flutter] Add Advanced Markers support (#7882)
[google_maps_flutter] Add Advanced Markers support (flutter#7882)
[google_maps_flutter] Add Advanced Markers support (flutter#7882)