http://trac.webkit.org/changeset/85795 http://build.webkit.org/results/Windows%207%20Release%20(WebKit2%20Tests)/r85794%20(6495)/results.html http://build.webkit.org/results/Windows%207%20Release%20(WebKit2%20Tests)/r85795%20(6496)/results.html
I am going to commit the expected failing results in order to get the bots green.
Committed the expected failing results in http://trac.webkit.org/changeset/86019
<rdar://problem/9403200>
Big ol' fail on my part. Thanks for cleaning up the mess, Jessie. I'll look into these failures today.
I think we can relax these tests such that they still pass in WebKit2 and would start failing if either of the bugs they are tests for were reintroduced. At this point I see no evidence that they are indicative of real-world bugs in WebKit2.
platform/win/plugins/window-geometry-initialized-before-set-window.html is easy to fix. We should just check the window's size and stop caring about its position. platform/win/plugins/window-region-is-set-to-clip-rect.html is harder. In WebKit2, the plugin window's region won't be set until the UI process paints. But we don't have a good way to wait for that to happen, or to ensure that it happens in a certain order.
(In reply to comment #6) > platform/win/plugins/window-region-is-set-to-clip-rect.html is harder. In WebKit2, the plugin window's region won't be set until the UI process paints. But we don't have a good way to wait for that to happen, or to ensure that it happens in a certain order. A timer seems to work around the issue. (Lame!)
Created attachment 92959 [details] Update some plugin tests to work with WebKit2's asynchronous windowed plugin positioning on Windows
Committed r86157: <http://trac.webkit.org/changeset/86157>
http://trac.webkit.org/changeset/86157 might have broken SnowLeopard Intel Release (WebKit2 Tests) The following tests are not passing: fast/frames/flattening/frameset-flattening-subframesets.html