@ale-cristofori Thanks for this export of the test data but unfortunately, the services required by these layers are not accessible by me

@tdipisa Is it possible to add this layer to the existing csw?

or @ale-cristofori @tdipisa maybe point me to a map or a layer in MS which can produce many legends on a chart ?

@ale-cristofori Thanks for this export of the test data but unfortunately, the services required by these layers are not accessible by me

@tdipisa Is it possible to add this layer to the existing csw?

or @ale-cristofori @tdipisa maybe point me to a map or a layer in MS which can produce many legends on a chart ?

@dsuren1 use this map which contains the sample dataset you need.

Investigation outcome

As reported in the description, this is an open issue in plotly.js and we do not have a set timeline for its resolution yet.

However, we can handle this case in MS on chart initialization by adding an event listener of the wheel event in capture mode and dispatch a modified event with new deltaY value, such that the sensitivity of the wheel event is exhibited in a controlled manner

Demo with a rudimentary fix applied

Suggestion

Instead of adding a predefined sensitivity value, we can also expose this as a configurable property for the chart. ex: legendMouseWheelSensitivity. Your thoughts @tdipisa ?

Thank you @dsuren1. I would like you to share the above with other core team members (like @allyoucanmap or @offtherailz) since I think it is something probably quick but that we should handle carefully if we have to implement a kind of workaround in MS.

@allyoucanmap
As per our discussion,
I tested with multiple browsers (Chrome, Firefox, Opera), and found that normalizing the deltaY property results in consistent scrolling behavior across all of them. It appears that a fixed value of deltaY: ±0.30 can effectively normalize scrolling behavior, with negative and positive deltaY values corresponding to upward and downward scrolling, respectively.