> There is nothing IPython can do about it. It's a Safari-specific security policy and not due in WebKit, correct? It seems like we'd have more luck appealing to WebKit devs than those working on Safari (though there's overlap for sure). --Scott