marek123x

Great job. Exactly this! ??
Works great!

temporarily fixed by adding:

i.getAttribute("data-mousewheel") == "true" &&

to the

i.hasAttribute("data-releaseonedges") && ((t.options.mousewheel = {}), (t.options.mousewheel.releaseOnEdges = i.getAttribute("data-releaseonedges"))),

so it looks like:
i.getAttribute("data-mousewheel") == "true" && (i.hasAttribute("data-releaseonedges") && ((t.options.mousewheel = {}), (t.options.mousewheel.releaseOnEdges = i.getAttribute("data-releaseonedges")))),

mousewheel and releaseOnEdges even works when enabled.

feel free to use it or to find a more elegant solution. For now, it works fine for me! ??

I debugged and unminified the JS file frontend_blocks.js and found out that this is triggering the slide:

mousewheel: {
    releaseOnEdges: false,
  },

even if “releaseOnEdges == false” (in the gutenberg blog settings) the init method fires mousewheel = true.

deleting
i.hasAttribute("data-releaseonedges") && ((t.options.mousewheel = {}), (t.options.mousewheel.releaseOnEdges = i.getAttribute("data-releaseonedges"))),

from the JS, disables the mousewheel.

Need to check if mousewheel is enabled, if so, releaseOnEdges should be available in the init… if disabled, releaseOnEdges shouldn’t be loaded into the init method.