[Webkit-unassigned] [Bug 169126] New: [GTK] Two file reset tests are failing in the bots since they were added in r213042

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=169126

            Bug ID: 169126
           Summary: [GTK] Two file reset tests are failing in the bots
                    since they were added in r213042
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Local Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Keywords: Gtk, LayoutTestFailure
          Severity: Normal
          Priority: P2
         Component: Tools / Tests
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: cgarcia at igalia.com
                CC: aestes at apple.com, bugs-noreply at webkitgtk.org,
                    lforschler at apple.com, thorton at apple.com

They are failing because the GTK+ event sender is not firing the second UIHelper.activateAt() after the change event. In onse case this causes that the reset button is not locked, and in the other one the file input is not unfocused.

https://build.webkit.org/results/GTK%20Linux%2064-bit%20Release%20(Tests)/r213357%20(21247)/fast/forms/file/file-input-reset-using-open-panel-diffs.html
https://build.webkit.org/results/GTK%20Linux%2064-bit%20Release%20(Tests)/r213357%20(21247)/fast/forms/file/file-reset-in-change-using-open-panel-diffs.html

This is because the change event is emitted before the mouse up, and the GTK+ event sender ignores mouse down events when the button is already down to not confuse Xvfb. So, we can easily fix theses tests by using a timeout to ensure the next UIHelper.activateAt() happens in a different run loop iteration, after the mouse up.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170303/4035a8f9/attachment.html>