Hi,
This seems to be a limitation of the Google Maps JavaScript API.
We'll have to investigate if there is a possible workaround available to improve this behavior in a future version.
We'll have to investigate if there is a possible workaround available to improve this behavior in a future version.