-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OneZoom site hangs with in a JavaScript infinite loop if tree_startpoints table is empty #851
Comments
Wrapping the lot in |
Right, that should do it. I just reported it minimally to uikit as uikit/uikit#5004. Hopefully, if it gets fixed there, we don't need to change our code, other than upgrading uikit. Getting from the full hang to the minimal repro was ... a fun time! |
The workaround is to simply add a bogus entry to |
Good news: the issue was just fixed in uikit. Keeping this open until we update to a uikit with the fix, which will need to be 3.20.9 or later. |
FWIW switching versions is a case of tweaking here and running Line 9 in fa65779
But I wouldn't roll it out without testing the UI, particularly the search / advanced search. |
Thanks @lentinj. Agreed, we'll need to do a good round of testing on the UI. Upgrading is not urgent, as I'm unblocked by adding a dummy |
It wouldn't be a bad idea, IMO, to have |
When just going to http://127.0.0.1:8000/OZtree/, the browser hangs with high CPU if the
tree_startpoints
table is empty. This appears to be caused by a bug inuikit
, but we could potentially work around on our side.More specifically, in index.html, we have
{{for key in carousel:}}
. Ifcarousel
is an empty list, we end up with no<li>
tags, which makes theuk-slider
blow up.The text was updated successfully, but these errors were encountered: