UniversalViewer
Fix #955
Fixes #955
As noted in the issue, I do not know if this breaks other stuff, i.e. data that is not shown in openseadragon.
![codesandbox[bot] avatar](https://avatars.githubusercontent.com/in/206332?v=4 "Published by a pub.dev verified publisher"){kind=small}
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| universalviewer | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Mar 15, 2024 10:04am |
![vercel[bot] avatar](https://avatars.githubusercontent.com/in/8329?v=4 "Published by a pub.dev verified publisher"){kind=small}
This pull request is automatically built and testable in CodeSandbox.
To see build info of the built libraries, click here or the icon next to each commit SHA.
![codesandbox-ci[bot] avatar](https://avatars.githubusercontent.com/in/38409?v=4 "Published by a pub.dev verified publisher"){kind=small}
Thanks, @nicolasfranck. I see that selectCurrentTreeNode() contains a 4-year-old TODO comment which implies that the eventual plan was to eliminate the need for two separate select methods entirely... so if that refactoring eventually occurs, your proposed change would need to be undone. But if it's fixing problems in the meantime, it seems relatively harmless, given that it's updating the tree node using the appropriate method for the event that caused the tree node to change initially. However, I see that there are several other calls to selectCurrentTreeNode in other parts of the file, and I'm not sure if these might still have bugs related to ranges. If they do, those bugs might be harder to fix.
In any case, bottom line: it seems unlikely to me that this fix makes things worse or causes new breakages, but I'm not sure if it fixes every problem related to the underlying problem. I'd love input from @edsilv if he has any memory of the context of this, but I'd be reasonably comfortable with approving and merging this fix if you need it resolved before Ed has a chance to respond. Feel free to follow up here if you need further action from my end.
