Mousetracker click, press, drag, drag-end, scroll events do not fire after upgrading to 3.0
See original GitHub issueClick, press, drag, drag-end, scroll events do not fire when using mouseTracker after upgrading to 3.0.
Example codesandbox: https://codesandbox.io/s/openseadragon-navigator-click-event-forked-ofetb
If you fork the codesandbox and change the openseadragon version to 2.4.0 you will find all of those event handlers are working.
Is this expected behavior?
If so maybe the documentation of mouseTracker should be updated to remove these event handlers as an option.
We were attaching the mousetracker to a navigator. Using the navigator-press
etc event handlers works, except that there is no navigator-drag-end
handler, which is a breaking change for us.
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (9 by maintainers)
Top Results From Across the Web
[WIP] Be able to control when we cancel events. #1537 - GitHub
As part of our event processing in MouseTracker, we cancel events sometimes. ... Mousetracker click, press, drag, drag-end, scroll events do not fire...
Read more >Event that gets fired before (not after!) DOM elements are ...
I am wondering if there is any event that gets fired for every scroll method(eg. mousewheel, dragging the scroll bar, pushing the down...
Read more >Document: scroll event - Web APIs - MDN Web Docs - Mozilla
The scroll event fires when the document view has been scrolled. To detect when scrolling has completed, see the Document: scrollend event.
Read more >DragGesture in SwiftUI ScrollView … | Apple Developer Forums
The gesture's events properly fire when you drag vertically, but when you drag ... I don't want to even begin trying to reimplement...
Read more >.scroll() | jQuery API Documentation
The scroll event is sent to an element when the user scrolls to a ... A mouse click or drag on the scroll...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@msalsbery As far as I know, we’re still canceling the events. In fact, from peoples’ reports, it seems that we are canceling them even more aggressively than before 3.0. #1537 is still open. If you’ve got code that’s meant to fix it, that would be awesome! ❤️
Geez, if that’s still happening then yes I have a huge patch that’s not in…ugh. I’ll need to go through and see what changes since then were addressed by that patch and/or merge in other patches that fixed other stuff since then.
I’ll be back with more answers… 😉