Bug 114917
| Summary: | [EFL][WK2] fast/events/touch/frame-hover-update.html is failing | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Chris Dumez <cdumez> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | allan.jensen, kenneth, mcatanzaro, mikhail.pozdnyakov, noam, tonikitoo |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | 114912 | ||
| Bug Blocks: | |||
Chris Dumez
fast/events/touch/frame-hover-update.html is failing on EFL WK2 with the following diff:
--- /home/buildslave-1/webkit-buildslave/efl-linux-64-debug-wk2/build/layout-test-results/fast/events/touch/frame-hover-update-expected.txt
+++ /home/buildslave-1/webkit-buildslave/efl-linux-64-debug-wk2/build/layout-test-results/fast/events/touch/frame-hover-update-actual.txt
@@ -1,21 +1,18 @@
PASS [object HTMLDocument] is non-null.
PASS [object HTMLDocument] is non-null.
-PASS hoveredTop.length is 1
-PASS hoveredIframe1.length is 1
+FAIL hoveredTop.length should be 1. Was 0.
+FAIL hoveredIframe1.length should be 1. Was 0.
PASS hoveredIframe2.length is 0
-PASS hoveredTop.length is 1
+FAIL hoveredTop.length should be 1. Was 0.
PASS hoveredIframe1.length is 0
-PASS hoveredIframe2.length is 1
+FAIL hoveredIframe2.length should be 1. Was 0.
PASS hoveredTop.length is 0
PASS hoveredIframe1.length is 0
PASS hoveredIframe2.length is 0
-PASS hoveredTop.length is 1
+FAIL hoveredTop.length should be 1. Was 0.
PASS hoveredIframe1.length is 0
PASS hoveredIframe2.length is 0
-PASS hoveredTop.length is 1
+FAIL hoveredTop.length should be 1. Was 0.
PASS hoveredIframe1.length is 0
PASS hoveredIframe2.length is 0
-PASS successfullyParsed is true
-
-TEST COMPLETE
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Michael Catanzaro
Closing this bug because the EFL port has been removed from trunk.
If you feel this bug applies to a different upstream WebKit port and was closed in error, please either update the title and reopen the bug, or leave a comment to request this.