[Webkit-unassigned] [Bug 128172] New: [Tests] some tests in fast/events/touch test non-replicable platform-specific behavior

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Feb 4 03:47:08 PST 2014


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

           Summary: [Tests] some tests in fast/events/touch test
                    non-replicable platform-specific behavior
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Tools / Tests
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: carlosg at gnome.org


In the workings of a patch for bug #98931 to add touch support for GTK+, multiple tests had to be skipped because they tested platform-specific behavior in several ways:
- The EventSenderProxy object is expected to coalesce multiple operations under one single event. Under X11/GTK+, each touch update will emit an independent event that can't be coalesced, as there is nothing that groups touch IDs at that layer, so that brings 1) a different number of events than many tests expect and 2) different expectations if the effect of two touch updates are expected to happen at once.
- On some other tests, touch IDs were directly tested, even though platforms may generate those differently, as it happens with X11

So in order to be useful more generally I'd propose to change those tests to test the coherence of the events gotten, rather than a fixed stream of those. The events currently tested would be rather considered "milestones", and intermediate events that still maintain coherence would be safely skipped, that way those tests would also be useful to test GTK+ behavior. As for touch IDs, comparing those from previous events is fine, checking fixed numbers is not...

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list