Updates:
Cc: [email protected]
Comment #2 on issue 17523 by [email protected]: Content scripts don't see
their own functions in setTimeout
http://code.google.com/p/chromium/issues/detail?id=17523
It will work if you pass foo as a reference, eg:
window.setTimeout(foo, 100);
+abarth
Adam, do we want to consider this one a bug or feature? I vaguely lean
toward bug:
window.setTimeout(<string>), should execute in content script world. But if
it is
hard, I could easily go the other way.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
