Unless I'm misreading between the lines, kevs is unable to interface with the window in question because its content is causing Safari to hang. If so, he's stuck with the Wait Cursor (aka spinning beachball) and can neither click the red button nor effect any response from Safari via the Command-W key combo.
I think the real question kevs is asking is this: if the content of a single tab or page is causing Safari to hang, is there a way to rid oneself of that single tab or page, thereby eliminating the hang, while allowing the rest of the application to carry on as usual?
Unfortunately, the answer is "not yet." This functionality, known as sandboxing, is available in Google's Chrome browser, and is currently being incorporated into
WebKit2.
WebKit2 is a new API layer for WebKit designed from the ground up to support a split process model, where the web content (JavaScript, HTML, layout, etc) lives in a separate process from the application UI. This model is very similar to what Google Chrome offers, with the major difference being that we have built the process split model directly into the framework, allowing other clients of WebKit to use it...
...WebKit2 should be considered an early technology demo. It is not yet production quality.
