Some people use the desktop website on mobile devices. Kartographer works suboptimally in these situations for various reasons.

1. The controls are miniature. While this goes for all dialogs and controls, because the controls are located within an almost screen covering scrollable area, it's harder to do pinch to zoom of the website on the mobile phone. (as opposed to pinch to zoom on the map, the touch actions conflict with eachother).
2. Memory pressure becomes high, leading to potential crashing/closing of the browser tab/window. This happens because
   1. The page can be very large (Wikipedia articles on desktop can easily be in the multiple megabytes)
   2. JS code needs to be loaded to open the map dialog
   3. You are opening a screen with the width of a desktop screen, but due to portrait orientation that can be up to 4 times bigger than a normal desktop in terms of area, and this then needs to be scaled down in memory back to mobile dimensions.
   4. In some conditions, we resize the screen of Vector 2022 to snap it to 1000px after loading it, because viewport specifications of browser are an absolute mess
   5. Lots of older or low end mobile phones only have like 4 to 6 GB of RAM to begin with.

All of this to say... opening Kartographer on the desktop site using a mobile phone is suboptimal. While it could be argued that opening something like this in the desktop site on a mobile device is not supported, it is a very real and common use case of course.

Maybe we can put some logic in, to evaluate by looking at pointer coarse, orientation and screen.availWidth vs window.innerWidth and choose to either not load, or to emit an additional warning dialog or something before opening the map?