ICEfaces
  1. ICEfaces
  2. ICE-11570

Update Google Maps components to use newer API features

          Details

          • Type: Improvement Improvement
          • Status: Open
          • Priority: Major Major
          • Resolution: Unresolved
          • Affects Version/s: EE-4.3.0.GA_P07, EE-3.3.0.GA_P13
          • Fix Version/s: None
          • Component/s: ACE-Components
          • Labels:
            None
          • Environment:
            Any

            Description

            The google.maps.Marker and google.maps.places.Autocomplete objects are marked as deprecated, as a warning sign appears in the browser console when using these objects. While the same message specifies that those objects will continue to be supported, it recommends migrating to their replacements google.maps.marker.AdvancedMarkerElement and google.maps.places.PlaceAutocompleteElement, respectively. The same warning message also mentions that at least 12 month notice will be given before support is discontinued.

            This JIRA is to make the necessary changes in our code to support the newer API objects while maintaining backwards compatibility.

              Activity

              Hide
              Permalink
              Arturo Zambrano added a comment -

              An initial attempt to migrate to the newer API objects proved to be more complex that expected, mainly due to the various interactions between our ace:gmap* components. The newer objects use a very different approach to setting properties and the new AdvancedMarkerElement doesn't support animations out of the box and doesn't have the same look as the original marker.

              Also, in order to maintain backwards compatibility and not to force app developers to migrate to the newer objects right away, a boolean attribute should be added to the main gmap component wrapper to choose between the legacy objects and the newer objects. The default should be set to using the legacy objects.

              Show
              Arturo Zambrano added a comment - An initial attempt to migrate to the newer API objects proved to be more complex that expected, mainly due to the various interactions between our ace:gmap* components. The newer objects use a very different approach to setting properties and the new AdvancedMarkerElement doesn't support animations out of the box and doesn't have the same look as the original marker. Also, in order to maintain backwards compatibility and not to force app developers to migrate to the newer objects right away, a boolean attribute should be added to the main gmap component wrapper to choose between the legacy objects and the newer objects. The default should be set to using the legacy objects.

                People

                • Assignee:
                  Arturo Zambrano
                  Reporter:
                  Arturo Zambrano
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated: