IssueTracker

Thanks for your suggestion!

We'll be reviewing this for further consideration. Please star this issue to get updates and leave comments for additional information. Please note that starring the issue also provides our product team with valuable feedback on the importance of the issue to our customers.

✨

Thank you for waiting.

We have verified and logged this issue internally. Please note that we cannot give you any timelines, but you can star the issue to get notifications.

Apologies for the confusion. As an improvement to accessibility InfoWindows are now treated as ARIA dialogs and use a heuristic to automatically focus keyboard navigable contents when opened. If an InfoWindows is being pulled into focus when it should not, you can opt out of this behavior by passing shouldFocus:false . e.g.

// old:
infoWindow.open(map, marker);
// new:
infoWindow.open({anchor: marker, shouldFocus: false});

Yes, the map argument is not required when the anchor/marker is already associated with a map! (For those who need the map argument with shouldFocus, we will be adding that ability in the next weekly release.)

See also: https://developers.google.com/maps/documentation/javascript/reference/info-window#InfoWindowOpenOptions.shouldFocus

Please let us know if that helps?

I am not sure, if that's the case. On a customers page on which multiple InfoWindows should be shown (without focus) after user interaction, i refactored the code so that: All InfoWindows are closed. After closing all the InfoWindows and opening just a single one with the same properties does not seem to do the trick.

If I refactor the code to version 3.43 with just a map as given param, it works. With single and multiple windows.

Hope this helps

Ran into the same issue on my site.

• close() before opening the infoWindow seemed to do the trick. shouldfocus property is not working on the already opened infoWindow.
• Like mentioned above, you don't need the map reference anymore when calling infoWindow.open().

This is what worked for me -

//old: 
        infoWindow = new google.maps.InfoWindow({maxWidth: 400, content: contentString});
        infoWindow.open(buMap, storeMarker);

//new: 
        infoWindow = new google.maps.InfoWindow({maxWidth: 400, content: contentString});
        infoWindow.close();
	infoWindow.open({shouldFocus: false, anchor: storeMarker}); 

Hello. This should be fixed with the next release of the API (v3.45.3). Marking this resolved for now, but please let us know if that is not the case after v3.45.3 is released.

Using open({ shouldFocus: false, ... }) correctly prevents the map from being focused. However, calling infoWindow.close() is still causing the map to be focused.