The tile layer is just a few elements that are standard HTML elements, the element behind the shapes is a single div, while a shape layer consists of a lot of SVG elements, and attaching events to all of them like that is likely to deteriorate performance and may also break other scenarios developers rely on.

We haven't had other people raise this as a problem in the several years since this has been available, which leads me to believe that the current behavior is acceptable for the majority of the users of this widget. Thus, considering that a workaround can be made if this is unwanted, we would rather avoid the risk of breaking existing scenarios and causing worsened performance.

In this scenario, a click was actually executed on the shape. If you click and hold the left button on an element, move the mouse around that element, and release the button, the click event of the element will fire. This is what happens here, the difference is that the element moves around with the mouse because of the dragging feature. Here's a basic example that illustrates this browser behavior: https://dojo.telerik.com/@bratanov/ONiDIRoC. Since such behavior is the normal browser behavior, I believe it is expected of the map to fire the click event on a shape in such a scenario.

If you don't want logic tied to shape click to execute after panning, using a simple throttling technique on the panEnd event can let you check for a flag to know whether there was a pan that happened, or only a click. A basic example of throttling an event is available here: https://stackoverflow.com/questions/667426/javascript-resize-event-firing-multiple-times-while-dragging-the-resize-handle/668185#668185.