Currently, the app loads with the map set to a specific default pan/zoom. This does not take screen size into consideration. On small screens, the metro region will be cropped. On large screens, there'll be wasted space around the region.
The default pan/zoom should fitBounds so that the metro region fill the allotted space in the map.
Q for @daragoldberg et al: Should the previous/next buttons reset the pan/zoom? If you've zoomed in and then go to prev/next narrative, I think we should zoom out to tell the story of the whole region. If you select a map from the dropdowns, perhaps the pan/zoom can/should persist.
Currently, the app loads with the map set to a specific default pan/zoom. This does not take screen size into consideration. On small screens, the metro region will be cropped. On large screens, there'll be wasted space around the region.
The default pan/zoom should
fitBoundsso that the metro region fill the allotted space in the map.Q for @daragoldberg et al: Should the previous/next buttons reset the pan/zoom? If you've zoomed in and then go to prev/next narrative, I think we should zoom out to tell the story of the whole region. If you select a map from the dropdowns, perhaps the pan/zoom can/should persist.