People who work on WebKit2: should I check in the failing result and/or does someone want to look into the focus issue?
On Wed, Mar 23, 2011 at 4:45 PM, Ojan Vafai <o...@chromium.org> wrote: > Actually, looks like this is a WebKit2-related bug. It just happens that > this is the only non-pixel test that depends on the window having focus. For > example, the following fails on my SnowLeopard machine due to lacking the > focus ring: > run-webkit-tests --debug -2 fast/css/focus-ring-outline-color.html -p > --tolerance 0 > > > On Wed, Mar 23, 2011 at 4:13 PM, Stephanie Lewis <sle...@apple.com> wrote: > >> The machine did have a software update dialog up. However, i dismissed >> the dialog and the test is still failing. >> >> -- Stephanie >> >> On Mar 22, 2011, at 9:29 PM, Ojan Vafai wrote: >> >> > fast/css/pseudo-any.html is failing on SnowLeopard Intel Release >> (WebKit2 Tests), but it's not failing on SnowLeopard Intel Release (Tests). >> The test depends on the window having focus and the failure it's getting is >> the one you get if you load the page in a blurred window. So, I assume some >> dialog or something is up on that bot causing focus issues. What I don't get >> is that there are other tests that depend on the window having focus that >> don't seem to be failing on this bot. Does someone with access to the bot >> mind taking a look? >> > >> > Ojan >> > _______________________________________________ >> > webkit-dev mailing list >> > webkit-dev@lists.webkit.org >> > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev >> >> >
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
