GeolocateControl issue

Nobody has claimed this yet.

When creating a mapboxgl.GeolocateControl, adding the map and adding a event listener the geolocate callback sends the geolocate object instead of the navigator Geo object.

Example

geoTracking = new mapboxgl.GeolocateControl({
positionOptions: {
enableHighAccuracy: true,
timeout: 1000
},
trackUserLocation: true,
showUserHeading: true,
showUserLocation: true,
trackUserLocation: true,

});
map.addControl(geoTracking, 'bottom-right');
geoTracking.on('geolocate', (y) => {
//y is not the a GeolocationPosition like https://docs.mapbox.com/mapbox-gl-js/api/markers/#geolocatecontrol.event:geolocate
//instead y is the geolocate event

});

Start at the GeolocateControl geolocate event and compare its callback payload with the GeolocationPosition described in the linked API documentation. Reproduce the behavior using the example in the issue, then verify that the callback receives the navigator GeolocationPosition rather than the geolocate event object.

Written by the indexing model from the issue text.