In particular, we should never send referer[sic] headers, nor provide access to window.opener or window.parent.
Can you connect up with tomcat for the qawanted help
Tomcat: Some example tests of handler apps are in test_handlerApps.xhtml and the files it references. This is only somewhat useful to this testing, I think, in that this particular test is calling the launching functions directly, rather than triggering stuff through the UI, which is what I suspect we're going to need. There are several cases worth testing, I think: * link in the content area clicked * URL typed into the URL bar * Send To command chosen from the context menu After giving it more thought, I'm no longer so sure these are all easily testable from Mochitest, but it bears investigation...
Also worth noting is that how the first and third cases are tested depends in part on what we decide to do in bug 402736.
With a few exceptions, I'm mostly focused on MailCo-related hacking now. Reassigning a bunch of bugs to default component owners. I'm happy to help with brainstorming/advice as needed, however. Search for the string MAILMONKEY to delete any bugmail generated by this change.
Connor: need an owner.
Ping on this...
So, this all seems ok. I whipped up some manual tests: http://people.mozilla.com/~dolske/handler/ Visit the "install_mailto.html" pagge to install a test mailto handler, and then select it from Prefs -> Applications -> mailto. Testing consists of looking at the output of a local copy of http://people.mozilla.com/~dolske/handler/linkpage.html (to trigger same-origin checks). * The parent and children are unable to peek across the iframe boundary * No referrer is sent when loading from an iframe or clicking the link I don't see anything interesting happening with these sanity checks, so resolving this bug.
Issue is Resolved - removing QA-Wanted Keywords - QA-Wanted query clean-up task