[BUG] Unknown call to setInterval #66
Labels
No labels
blocked
bug
duplicate
enhancement
FR accepted
help wanted
invalid
need discussion
next release
not reproduced
PR requested
question
reproduced
WFB
WIP
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Depends on
#67 Don't use jQuerry anymore
deblan/side_menu
Reference
deblan/side_menu#66
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Issue
Environment
The Stuff
Every 50ms this is triggered:
Offending trigger line:
setInterval(updateTopMenu, 50)Offending function line:
var updateTopMenu = function() {I've no clue why this line or function exists.
IMO, there shouldn't be such a call. Unneccessary for a menu and way too often. It essentially makes the app unusable.
Additionally, I was able to kill the interval and everything works fine without it.
My Question: Why does such a call exist without any reference or reason? I'm unable to identify a issue or clear commit for this.
(But apperantly it has smth. to do with #19, but I don't see why a endless running setInterval (every 50ms!!) is neccessary.)
LG,
random user who recommends using a more public repository like gitHub, gitLab or BitBucket. Selfhosted instances aren't very suitable for collaboration nor friendly for reporting issues.
PS: Thanks to this, I now know I can safely have over 100k warnings in one tab :p
Should be fixed in the jquery refactoring branch.
Reporting an issue on Github, gitLab or BitBucket is the same thing than reporting an issue on a forge like Gitnet: you must have an account, login and report.
Doing a pull request on Github, gitLab or BitBucket is the same thing than doing a pull request on a forge like Gitnet: you must have an account, login and do pull request.
...and you can login on Gitnet with a Github or Gitlab account so nothing more complicated or boring :)
👍
You're not wrong. However, I believe it's better to have all modules/additional repos of a project hosted on the same platform as the original one (→ Nextcloud), which is GitHub… (I'm not a fan of it either.)
Or at least having a mirror project for issues only.
Welp, anyway. As you see, I've created an account after all ;)
…mmh, should have tried logging in with GitLab. Wasn't an option on the registration page and hence, I thought, it's only available afterward. (and/or for organization use with auto-acc-creation).
Released in v2.0.0!