Continue calling onDrag events even after the pointerout event

[brian-byassee]

I updated the draggable.ts file here to support drag events even after the cursor has left the wave surfer. I think this makes the seekToDrag function more intuitive and inline with what users might expect when seeking through a video or audio file.

The thing is this could be a breaking change for applications that are expecting the pointerout event to fire onPointerUp.

Thoughts on if this changes feels safe enough or if this just isnt the sort of functionality wanted in wavesurfer.js

Here is the PR preview:
https://github.com/katspaugh/wavesurfer.js/compare/main...brian-byassee:wavesurfer.js:waversurfer-draggable-update?expand=1

[brian-byassee]

Closing as I have found issues with this current update with envelope

[katspaugh]

That event is assigned to the document object, so unless your waveworm is close to the edge of the page, it's supposed to continue dragging even outside of the waveform. Perhaps the listener isn't added correctly though. We should check that it fires only on the document object and not on a child element. It might need { capture: true }.

[brian-byassee]

Steps to reproduce the issue would be.

1. https://wavesurfer.xyz/examples/?basic.js
2. Add dragToSeek: true
3. Start dragging and then with the mouse still down drag below the waveform. The drag event gets canceled.

That event is assigned to the document object

I think this is because 'document' is the wavesurfer shadow root, not document.body of the page.

Additionally pointerout calls onPointerUp

[katspaugh]

I've just fixed this in #3477.

[brian-byassee]

Ah brilliant. Much better than the approach I had started down. Thank you 🙏

And sorry I thought I might save you time and yet it seems I probably took more of your time.

[katspaugh]

Thanks! I appreciate your pointing out this problem, I think it’s good we fixed it.