Missing redo-solid.svg file when using the "Reset Map View Leaflet Plugin" functionality

Core maintainer @catch has written a comment about this issue:
https://www.drupal.org/project/drupal/issues/3393274#comment-16165561 🐛 The theme must be passed as a query argument Closed: duplicate

thanks @gillesbailleux for reporting this ...
BUT indeed I couldn't reproduce this issue that you report
in my playground in Drupal 11.2.0 with Leaflet 10.3.3,
and both css and sj aggregation enabled.

Screenshot attached ...

Worth to mention that Leaflet 10.3.3 (that you explicitly mention "after upgrading to" ...) didn't touch any code related to "Reset Map View Leaflet Plugin" functionality.

Please run your further inspections/debugging and provide clear evidence of what changed changed in Leaflet 10.3.3. that is now potentially causing this issue of you ...

Greetings @itamair,

The live website which displays the client error in this issue has been updated to leaflet_module v10.3.4 with a composer update -W command followed by drush updb command and even a drush cr command. In /admin/config/development/performance, disabling bandwidth optimization displays the icon [see live-site-bandwidth-optimization-disabled.png]. When enabling bandwidth optimization, the icon disappears [see live-site-bandwidth-optimization-disabled.png].

Because the live website uses the minifyjs_module v3.0.3 and the minifyhtml_module v2.0.5, which could be the origin of the issue, I upgraded a dev website which does not use these modules to leaflet_module v10.3.4 with the same commands mentioned above. Disabling bandwidth optimization displays the icon [see dev-site-bandwidth-optimization-disabled.png] and enabling bandwidth optimization hides the icon [see dev-site-bandwidth-optimization-enabled.png].

The websites both use D11.2.2 but they have nothing in common as they have a different hosting, modules, PHP version, etc.

I marked this issue as minor, considering that the leaflet_module v10.3.4 is not at the origin of this client error.

Awaiting to have some time to test the GeoJSON overlays features of the 10.3 branch you recently implemented and which represent a major qualitative leap for the module.