Matthias mprove

While this is not working, you can add a note to the documentation that it does not work for raster layers. This would reduce confusion. https://docs.mapbox.com/mapbox-gl-js/api/map/#map#on

Do we have a drag’n’drop spec (or a set of test cases) for Mirador? i.e. what is suppose to work? /cf. my chapter on IIIF Drag’n’Drop here: https://docs.google.com/document/d/1t9ORxmdeJzSEUJWiK8WIUwtVXj37CboNHKxmL-dzEzk/edit#heading=h.bny1guv9siij

This is still an important suggestion.

I consider it even a regression bug b/c Mirador 2 did support this feature. Was manifest drop dropped deliberately?

It does work with https://view.collections.yale.edu/m3/ and https://projectmirador.org/embed/ It does not work with https://mirador-dev.netlify.app/__tests__/integration/mirador/ linked at https://iiif.io/guides/using_iiif_resources/

Well, it looks clean and simple. But I cannot really comment w/o considering the scenarios that should be supported by this data structure. Let me try. Although this might lead...

Or maybe there can/should be a mapping table for a specific app in the foreground? Sounds compelling but also like a challenging coding task.

ok, works fine for [Chronoscope Word](https://mprove.de/chronoscope/world.html)

I suppose I have solved this in the context of my Chronoscope, see for instance the Chrono CityTour or ChronoPort https://mprove.de/chronolab/world/tour/city.html https://mprove.de/chronolab/world/tour/port.html An internal data record bundles the sets of...

Pan and zoom [Chronoscope’s](https://mprove.de/chronoscope/world.html) view to the search area. Click the Search button (Key F). The map selector will show all maps that fit into or overlap with the view...