Non-interleaved GoogleMapsOverlay layers render above map controls

[camden-obertop]

Hello!

In my team's implementation of deck.gl, we are using the Google Maps API with a vector map id. We are using a GoogleMapsOverlay with interleaved set to false. When we set interleaved to true, the layers render behind our custom OverlayView implementations. We do not want to upgrade our OverlayViews to WebGlOverlayViews at the moment because that would be a large scale lift for the team.

The one problem I have run into and not been able to reconcile is that the deck.gl layers are now drawn above the Google Maps map controls. The image below shows what happens when rendering this scatterplot layer from the documentation

...
// set up deck.gl overlay and layer
const layer = new ScatterplotLayer({
  id: 'ScatterplotLayer',
  data: 'https://raw.githubusercontent.com/visgl/deck.gl-data/master/website/bart-stations.json',
  stroked: true,
  getPosition: d => d.coordinates,
  getRadius: d => Math.sqrt(d.exits),
  getFillColor: [255, 140, 0],
  getLineColor: [0, 0, 0],
  getLineWidth: 10,
  radiusScale: 6,
  pickable: true
});

const overlay = new GoogleMapsOverlay({
  layers: [layer],
  interleaved: true,
});

// associate the deck.gl overlay with the google map
overlay.setMap(map);

I found in the deck.gl source code where it decides to create the overlay with google maps rendering type being Vector and interleaved being false. I think it would work if we could specify to use normal OverlayView instead of WebGLOverlayView

All this is to say - is this a problem on our end? Is it a bug in deck.gl? Or is it maybe a bug in Google Maps itself? Thanks!