Comment #49 on issue 18857 by [email protected]: Support for GM Functions (Greasemonkey) in Chrome http://code.google.com/p/chromium/issues/detail?id=18857
Security is a tricky business. It's not enough to defend against attacks that are already taking placing in the world. You need to plan ahead and avoid opening up vulnerabilities that attackers can exploit later. We don't want to paint ourselves into a corner where we can't respond to security problems. Providing access to unsafeWindow is something that can't be made safe, and therefore we're not going to implement it. We can make cross-site XMLHttpRequest safe, so we are going to provide it. If you have a proposal for how we can implement unsafeWindow safely, I'd love to hear it. -- 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
