Custom Zoom Buttons – destroy() not fully removing them
See original GitHub issueI’ve got custom elements set for my zoomInButton
and zoomOutButton
:
OpenSeadragon({
...
zoomInButton: "zoomInDiv",
zoomOutButton: "zoomOutDiv",
...
});
After destroying a Viewer and subsequently creating a new one, these zoom buttons still work but also log the following errors to the console:
– Cannot set property 'lastZoomTime' of undefined
– Cannot set property 'zooming' of undefined
Screenshot of the console included as well:
_Originally posted by @mattwolff in https://github.com/openseadragon/openseadragon/issues/1878#issuecomment-731474734_
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Manually leave the meeting in case internet lost - iOS
When the internet is lost, when i destroy my custom UI without calling .leave, my audio and video stream still alive in the...
Read more >javascript - highcharts reset zoom button
destroy() function can be invoked only if resetZoomButton is an object. According to Highsotck source: For Stock charts (...) X axis zooming is ......
Read more >MapView | API Reference | ArcGIS Maps SDK for ...
A MapView may not be immediately ready for display after it has been constructed. ... To prevent these components from being destroyed, remove...
Read more >Using JQuery Zoom and JavaScript Zoom for Product ...
Image zoom is an important product feature for merchants, allowing buyers to enlarge product photos for better viewing.
Read more >The best way of setting up Zoom inside your Angular app
Before opening a meeting, JS and WebAssembly scripts from the SDK have to be loaded, but once you have loaded them you cannot...
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
If you’re in a situation like us where you can’t upgrade to
3.0.0
yet, this is a workaround that worked for us:Yes, just tested it out and this is no longer an issue – amazing overhaul.