Skip to content
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

setTimeout is complete broken #1554

Closed
Spamme1 opened this issue May 14, 2012 · 1 comment
Closed

setTimeout is complete broken #1554

Spamme1 opened this issue May 14, 2012 · 1 comment

Comments

@Spamme1
Copy link

Spamme1 commented May 14, 2012

Ah ah ah, sorry I can't say it differently, but you suck! You have complete broken the setTimeout, almost all my scripts work with setTimeout and you have broken them all, thanks! I just rolled back to the previous version, it took me one hour to understand why my scripts stopped to work, until I found out that the setTimeout wasn't working any more and this because GM updated itself automatically to a broken version!
First setTimeout doesn't return any more a clear id, nice work! If you make a wrapper it should work as before!
Second with intervals over 1000 ms it doesn't trigger it anymore, with intervals under 1000 ms after a few calls it stops to work!
No errors in console, just lost the timed call to the function!
Why you had to make a wrapper on the setTimeout function? It's a DOM function and logically if javascript is turned off also the setTimeout mustn't work! If you want to add a method to have a retarded call to a function, add a new function to the GM API and not a useless broken wrapper to a DOM function.

@arantius
Copy link
Collaborator

Well, this is a dupe. Of #1550, #1552 and #1553. And it severely lacks tact.

Human beings make mistakes. Take a chill pill dude.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants