I see... okay... btw, you can check the map module test on my dev web:
1) Go to
andkit01.com/en/
2) Scroll down to the map module, open StreetView anywhere on the map
Another thing I found, if you right-click and Inspect on the map module (with StreetView opened) on Chrome, and look at the EventListeners, there are these MSPointerDown, MSPointerMove, which both have imagery_viewer.js:843
However, for mousedown and mousemove, they have both imagery_viewer.js:409 and imagery_viewer.js:843
The StreetView mouse pan malfunction will be fixed and working fine if the imagery_viewer.js:843 lines are removed in mousedown and mousemove sections.
It seems that the difference between MSPointer and mouse are mobile/tablet touch vs mouse-click only? I'm wondering whether the issue is related to mouse/mobile map module handling? Any part of the script related to this?