upstreaming a test from Chromium.org - it seems to rely on some Chromium-specific timing issues, so I'm putting it in platform/chromium for now.
Created attachment 45216 [details] Patch
style-queue ran check-webkit-style on attachment 45216 [details] without any errors.
Looks OK. Seems we might want some sort of comment in the test that it need not be chromium specific.
Created attachment 45355 [details] Patch
Actually, it looks like it's not a platform-specific test, so I've revised the patch (which is good, because run_webkit_tests isn't set up to handle platform-specific http tests)
style-queue ran check-webkit-style on attachment 45355 [details] without any errors.
Comment on attachment 45355 [details] Patch 22 // We might want to change it to using postMessage when it 23 // is supported. postMessage is supported. Can we use that instead of polling?
okay, it looks like the key thing is simply to check whether or not window.opener stays null. Unfortunately, there doesn't seem to be a way to do this without using some sort of a timeout or a poll, since by setting window.opener to NULL, we prevent the target window from having a handle to the source. So, the source window has to send a message to the target, giving it a reference. But, if you post a message immediately after window.open(), the message gets dropped on the floor because the target window hasn't initialized yet. Sigh. Anyway, revised patch uploaded.
Created attachment 45361 [details] Patch
Comment on attachment 45361 [details] Patch I actually like the previous version better. Julie will kill me if we land this one.
heh. At least I got to spend some time learning how to use PostMessage() as a result of this ...
Sorry for the wild goose chase. :(
Comment on attachment 45355 [details] Patch Clearing flags on attachment: 45355 Committed r52477: <http://trac.webkit.org/changeset/52477>
All reviewed patches have been landed. Closing bug.