Bug 115659 - [EFL] accessibility/meter-element.html is failing
Summary: [EFL] accessibility/meter-element.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:
Blocks:
 
Reported: 2013-05-06 10:10 PDT by Chris Dumez
Modified: 2017-03-11 10:37 PST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Dumez 2013-05-06 10:10:25 PDT 
accessibility/meter-element.html was introduced in r149155 but is failing on EFL port:
--- /home/buildslave-1/webkit-buildslave/efl-linux-64-debug-wk2/build/layout-test-results/accessibility/meter-element-expected.txt
+++ /home/buildslave-1/webkit-buildslave/efl-linux-64-debug-wk2/build/layout-test-results/accessibility/meter-element-actual.txt
@@ -1,51 +1,12 @@
+CONSOLE MESSAGE: line 25: TypeError: 'null' is not an object (evaluating 'meter.role')
+      
 This tests that the 
 
 On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
 
 
 Meter1
-AXRole: AXProgressIndicator
-AXTitle: 6 blocks used (out of 8 total)
-AXDescription: 
-
-
-Meter2
-AXRole: AXProgressIndicator
-AXTitle: 75%
-AXDescription: 
-
-
-Meter3
-AXRole: AXProgressIndicator
-AXTitle: 
-AXDescription: 
-
-
-Meter4
-AXRole: AXProgressIndicator
-AXTitle: 12cm
-AXDescription: 
-
-
-Meter5
-AXRole: AXProgressIndicator
-AXTitle: 2cm
-AXDescription: 
-
-
-Meter6
-AXRole: AXProgressIndicator
-AXTitle: 12cm
-AXDescription: 
-
-
-Meter7
-AXRole: AXProgressIndicator
-AXTitle: 2cm
-AXDescription: 
-
-
-PASS successfullyParsed is true
+FAIL successfullyParsed should be true (of type boolean). Was undefined (of type undefined).
 
 TEST COMPLETE
Comment 1 Michael Catanzaro 2017-03-11 10:37:59 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.