Bug 114917 - [EFL][WK2] fast/events/touch/frame-hover-update.html is failing
Summary: [EFL][WK2] fast/events/touch/frame-hover-update.html is failing
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 114912
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-21 10:24 PDT by Chris Dumez
Modified: 2017-03-11 10:32 PST (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Dumez 2013-04-21 10:24:15 PDT
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
Comment 1 Michael Catanzaro 2017-03-11 10:32:57 PST
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.