"google.maps.Marker is deprecated" warning #121

Activity

1. paodb commented on Apr 22, 2024

   

   paodb

   on Apr 22, 2024

   Last edited by paodb

   MemberAuthor

   More actions

   I did some testing regarding this issue. Following the instructions in the migration link did not work as straight forward at it is supposed to. Problems or differences I found:
   1- To use AdvancedMarkers it is required to define a mapId
   2- AdvancedMarkers library needs to be load from within an async function when needed or add the '&libraries=marker' parameter to the API url

   Then, found this blogpost that mentions that an Advanced Markers Utility Library for JavaScript developers was also released, and can be use to define Advanced Markers. The web component will need to add the import import {Marker} from '@googlemaps/adv-markers-utils'; and the 2 points mentioned above are needed as well.

   Tested both approachs and they both make the demos using markers to break in different ways. For example, icons or colors are not being taken into consideration, clustering does not work (the version of markerclusterer library need to be updated to a newer version to support AdvancedMarkers), there's a setMap method that doesn't seem valid anymore. Logic on how markers are added will need to be reviewed and updated if the migration takes place.
2. javier-godoy

   added

   EPIC

   on May 6, 2024
3. paodb

   added this to Flowing Code Addonson May 6, 2024
4. paodb

   moved this to To Do in Flowing Code Addonson May 6, 2024
5. paodb

   removed

   EPIC

   on Jul 17, 2026
6. paodb

   moved this from To Do to In Progress in Flowing Code Addonson Jul 17, 2026
7. paodb

   self-assigned this

   on Oct 2, 2026
8. paodb commented on Oct 2, 2026

   

   paodb

   on Oct 2, 2026

   Last edited by paodb

   MemberAuthor

   More actions

   Decision: add Advanced Markers as a separate element, keep the legacy marker

   After re-analyzing this issue, the plan is:

   1. Both marker types will coexist.
   google-map-marker (legacy google.maps.Marker) stays as is. A new element, google-map-advanced-marker (AdvancedMarkerElement), is added alongside it.

   Why not replace the legacy marker?
   AdvancedMarkerElement is not a drop-in replacement:

   • It requires a mapId, and with a mapId the map's styles property no longer applies (cloud-based styling is used instead).
   • icon (URL/Symbol), label, animation, optimized and the marker mouse* events have no direct equivalent.
   • Replacing the element would break the web component API and the Java API (GoogleMapMarker#setIcon, etc.), so it would need a major version.

   Users can migrate at their own pace; the legacy marker keeps working (the deprecation warning is Google's, not ours, and not a removal).

   2. The goal is feature parity.
   Everything the legacy marker can do should be achievable with the advanced one. Where there is no native equivalent it will be emulated (e.g. icon URL → <img> content, animation → CSS, mouse events → DOM listeners on the content), or documented as not applicable (optimized).

   3. Delivered in small PRs to ease review.

   1. Core element (position, pin/content, click/drag events, info window, fit-to-markers, clear())
   2. Clustering / google-map.js integration
   3. Parity with the legacy marker (icon, label, animation, mouse events, touch-and-hold)
   4. Java wrapper in this repo (GoogleMapAdvancedMarker)

   Open points to verify in a spike: loading the marker library (the bundled loader does not request it, so likely importLibrary('marker')), and marker clustering with the current @googlemaps/markerclusterer.

   The previous draft PR (FlowingCode/google-map#48) has been closed in favor of this incremental approach.
9. paodb

   added 2 commits that reference this issue on Oct 2, 2026

   feat: load marker library

   ...

   5139921

   feat: load marker library

   ...

   55bcd94
10. paodb

    added 2 commits that reference this issue on Oct 27, 2026

    feat: add GoogleMapAdvancedMarker

    ...

    This issue will close once commit e3697f6 is merged into the 'master' branch.

    e3697f6

    feat: add GoogleMapAdvancedMarker

    ...

    This issue will close once commit 679fe68 is merged into the 'master' branch.

    679fe68
11. paodb

    closed this as completedin #186on Oct 27, 2026
12. paodb

    added a commit that references this issue on Oct 27, 2026

    feat: add GoogleMapAdvancedMarker

    ...

    This issue will close once commit d9f11f4 is merged into the 'master' branch.

    d9f11f4
13. github-project-automation

    moved this from In Progress to Done in Flowing Code Addonson Oct 27, 2026