Update jquery.mousewheel to 3.2.2

[erseco]

What changed upstream

Two releases since 3.1.13, and only 3.2.0 carries functional change:

• .on()/.off() for event binding where available
• no longer clobbers the event's offsetX/offsetY when it has not adjusted them (#165)
• bower/executable-bit/ESLint housekeeping

3.2.1 is a README update; 3.2.2 adds the minified file to the npm package. Neither of the functional changes affects how mindmaps uses the plugin, and both are improvements under jQuery 3.7.1. Most of the diff is a reformat from the project's move to ESLint flat config.

Handler now reads event.deltaY

this.$getContainer().bind("mousewheel", function(e) {
  var vertical = e.deltaY;
  if (!vertical) { return; }
  if (self.mouseWheeled) { self.mouseWheeled(vertical); }
});

The plugin sets the normalised deltaX/deltaY/deltaFactor on the event object; the extra callback arguments remain only for compatibility. Reading the event property is the non-deprecated half of the API.

Behaviour is unchanged — vertical wheel zooms, horizontal-only wheel does not — and the guard that makes that true is untouched. No other wheel handling was refactored.

Provenance

sha256  ca6ed6b8f937a4d5ad42ec2dec05d22031d26dc0b1a741650d98e397ffb5fc2a

Identical in the 3.2.2 git tag and the jquery-mousewheel@3.2.2 npm tarball, fetched independently and compared. MIT header intact, no reformatting on our side.

Validation

npm ci && npm test && npm run build	12 tests pass
Two clean builds	byte-identical (bfe2368c5e8e…)
eXeLearning Playwright suite against a build of this branch	25 passed

The browser suite includes the horizontal-wheel assertion, which asserts after each gesture rather than scrolling one way and back — a paired scroll cancels out and would hide a regression.

The build contract test now pins what the application actually depends on: the special event is registered, event.deltaX/deltaY are set, and the zoom reads deltaY.