Both of which are issues that will pretty much stop @Anywhere from working
and need to be noticed as soon as possible at installation. Hiding them in
console.log will make it more likely that @Anywhere will be installe
improperly and the admins will only find out when users complain.
Abraham
On F
I just came across a coworker's browser that triggered an alert() call
from anywhere.js. While okay for development, the use of alert() is
not friendly for production websites. Could these be converted
console.log() or some other benign mechanism?
Grepping through anywhere.js I found two instances
