Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 OS-All Area-Misc
New issue 17523 by dawagner: Content scripts don't see their own functions
in setTimeout
http://code.google.com/p/chromium/issues/detail?id=17523
Chrome Version : 3.0.195.1 (Official Build 21222)
What steps will reproduce the problem?
1. Create an extension with a content script which a function foo(), and
contains a call to setTimeout("foo()", 100);
2. Go to a page which matches that content script
What is the expected result?
foo is called 100ms later
What happens instead?
Uncaught ReferenceError: foo is not defined
Please provide any additional information below. Attach a screenshot if
possible.
If the page itself contains foo(), this is called. May be intentional (to
not clobber page functions)... Perhaps some kind of namespace (i.e.
contentScript.foo() always calls the content script's function) would be
useful?
--
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
-~----------~----~----~----~------~----~------~--~---
