I'm using your leaflet plug in and am running into two (related) issues:
1. the url for the script I'm loading is http://www.mapquestapi.com/sdk/leaflet/v2.s/mq-map.js?key=[keyremoved], and recently (in the past few days) some things stopped working without any changes on my end. Did you guys release a new version of the plugin and does the above link mean "use the newest version available"? If so, how can I target the specific older version? I need to be sure that your underlying plugin code is not changing from under me because your new code has not been quality assurance tested by my company (and in this case, it would have broken on a production system).
2. The specific issue I noticed in #1 is that we have to hook the attribution links that you guys add because the map is being hosted in an iframe, so we have to catch the click, pass it to the main page, and then have the main page navigate to it. This would be fine and dandy but it looks like you do not use the attribution control that leaflet creates, so when I go to look for your attribution links they aren't there:
<div class="leaflet-bottom leaflet-right">
<div class="mq-attribution-control leaflet-control">
©2016 MapQuest, <a href="http://hello.mapquest.com/attributions-mapbox">© Mapbox</a>, © TomTom | <a class="termsLink" id="terms" href="http://hello.mapquest.com/terms-of-use" target="_blank">Terms</a>
<div class="leaflet-control-attribution leaflet-control"></div>
the ".leaflet-control-attribution" element is what is returned by the leaflet API map.attributionControl.getContainer(), but you add your own control ".mq-attribution-control" to house your attribution links, which makes it really gross to support multiple sources for map tiles. I should be able to call map.attributionControl.getContainer() and get the control that holds your attribution links.
Like I said, this used to work just fine, but stopped working in the past few days. For reference, I'm using leaflet 0.7.5. Please advise.