&gt; In Chrome the code the pages run in themselves can&#x27;t do anything. Not true in Safari. The two are night and day different.<p>By &quot;the code the pages run in themselves can&#x27;t do anything&quot; do you mean that Chrome is sandboxed and Safari isn&#x27;t? That&#x27;s not true. WebKit rendering happens in a &quot;WebProcess&quot; which uses the Mac Seatbelt framework for sandboxing. The sandbox file is WebKit2.framework&#x2F;A&#x2F;Resources&#x2F;com.apple.WebProcess.sb.<p>Sure, Chromium&#x27;s sandbox is more restrictive. It proxies more things out through the broker process. But the difference is a matter of degree, not a fundamental architectural difference.