3 ms·
It wasn't my idea so, no, that was never my plan :) Though, you do raise a valid point, so let's see how it plays out. setTimeout = function(){...} de
by aidos 12y ago
It wasn't my idea so, no, that was never my plan :)
Though, you do raise a valid point, so let's see how it plays out.
setTimeout = function(){...}
delete setTimeout // true - you've removed the patch
window.setTimeout = function(){...}
delete window.setTimeout // true - you've removed the patch
window.constructor.prototype.setTimeout = function(){...}
delete window.constructor.prototype.setTimeout // false - the patch is still there!
I don't know about the hierarchy of the prototype chain up at this level but it seems to work.
Maybe there's some other way of getting to the built-in setTimeout so you can create your own version to mask the one I added?
EDIT you can embed an iframe and rip the native setTimeout from there.
- zedadex 12y agoreddit stops you from embedding it iirc
- aidos 12y agoI tried that too - you can just use any old page that has CORs headers allowing it.
- towelguy 12y agoThey could listen to the DOMSubtreeModified event in the 10s div.
- aidos 12y agoNice! There are probably clocks all over the place when you start looking around :)