Bug 177447
| Summary: | [GTK] Layout test imported/w3c/web-platform-tests/dom/events/Event-timestamp-high-resolution.html is failing | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Michael Catanzaro <mcatanzaro> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | bugs-noreply, cdumez, mcatanzaro |
| Priority: | P2 | ||
| Version: | Other | ||
| Hardware: | PC | ||
| OS: | Linux | ||
Michael Catanzaro
Layout test imported/w3c/web-platform-tests/dom/events/Event-timestamp-high-resolution.html has been unexpectedly failing for GTK since r222392 "Use high resolution timestamp for event time" when it was changed from an expected failure to an expected pass. The diff:
--- /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/imported/w3c/web-platform-tests/dom/events/Event-timestamp-high-resolution-expected.txt
+++ /home/slave/webkitgtk/gtk-linux-64-release-tests/build/layout-test-results/imported/w3c/web-platform-tests/dom/events/Event-timestamp-high-resolution-actual.txt
@@ -1,7 +1,4 @@
+CONSOLE MESSAGE: line 7: ReferenceError: Can't find variable: GamepadEvent
-PASS Constructed MouseEvent timestamp should be high resolution and have the same time origin as performance.now()
-PASS Constructed KeyboardEvent timestamp should be high resolution and have the same time origin as performance.now()
-PASS Constructed WheelEvent timestamp should be high resolution and have the same time origin as performance.now()
-PASS Constructed GamepadEvent timestamp should be high resolution and have the same time origin as performance.now()
-PASS Constructed FocusEvent timestamp should be high resolution and have the same time origin as performance.now()
+FAIL Untitled ReferenceError: Can't find variable: GamepadEvent
GTK does not support the gamepad API so there won't be any gamepad events. Shame. Updating expectations accordingly.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Chris Dumez
This test was skipped and I unskipped it in r222392. It looks like it still fails in GTK due to lack of Gamepad API support.
The right thing to do here is to skip again for GTK port only, until Gamepad API is supported.
Michael Catanzaro
(Mostly) agreed, I marked it as an expected failure for now. I don't think we have any plans to implement the gamepad API unfortunately.