RESOLVED FIXED 100248
[EFL][WK2] select-multiple-elements-with-mouse-drag.html fails 
https://bugs.webkit.org/show_bug.cgi?id=100248
Summary [EFL][WK2] select-multiple-elements-with-mouse-drag.html fails
Dominik Röttsches (drott)
Reported 2012-10-24 07:25:56 PDT
Some change in this range caused this test to fail on Wk2: http://trac.webkit.org/log/?action=stop_on_copy&mode=stop_on_copy&rev=132343&stop_rev=132333&limit=100
Attachments
Add attachment proposed patch, testcase, etc.
Raphael Kubo da Costa (:rakuco)
Comment 1 2012-10-24 08:17:10 PDT
It's working fine in my tests here if I only run this specific test. Perhaps some flakyness related to my focus commit?
Raphael Kubo da Costa (:rakuco)
Comment 2 2012-10-29 08:25:33 PDT
I've finally reproduce it here. Let the fun begin.
Raphael Kubo da Costa (:rakuco)
Comment 3 2012-10-30 01:36:33 PDT
Going back to r132332 did not help, and the test still failed most of the time. My guess is that it is somewhat flaky right, and has been so for a while.
Raphael Kubo da Costa (:rakuco)
Comment 4 2012-10-30 07:44:06 PDT
This is turning out to be interesting. I can only reproduce it here if I set the focus model in my window manager to a variation of "focus follows mouse" plus "automatically move the mouse pointer to newly created windows" and run WebKitTestRunner with the pointer outside of the region the window is going to occupy when it is created...
Raphael Kubo da Costa (:rakuco)
Comment 5 2012-10-31 04:30:52 PDT
I don't think there is an easy fix for this -- the test fails if you manage to move the mouse pointer in the window while it is in the process of selecting the elements in the box (which is made easier when the window manager automatically moves the mouse pointer for you as I described in comment #4). Since the test seems to be consistently passing in the bot again these days, I'll just unskip it again and hope for the best.
Raphael Kubo da Costa (:rakuco)
Comment 6 2012-10-31 04:34:02 PDT
Committed r133010: <http://trac.webkit.org/changeset/133010>
Note You need to log in before you can comment on or make changes to this bug.