Bug 106316
| Summary: | [GTK] accessibility/render-counter-text.html is failing | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Zan Dobersek <zan> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | bugs-noreply |
| Priority: | P2 | Keywords: | Gtk, LayoutTestFailure |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 98347 | ||
Zan Dobersek
The accessibility/render-counter-text.html layout test is failing on the GTK port. It was added in r139002.
http://trac.webkit.org/changeset/139002
Here's the diff:
--- /home/slave/webkitgtk/gtk-linux-64-release/build/layout-test-results/accessibility/render-counter-text-expected.txt
+++ /home/slave/webkitgtk/gtk-linux-64-release/build/layout-test-results/accessibility/render-counter-text-actual.txt
@@ -2,12 +2,12 @@
On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
-PASS line1.childAtIndex(0).stringValue is 'AXValue: 1'
-PASS line1.childAtIndex(1).stringValue is 'AXValue: :'
-PASS line1.childAtIndex(2).stringValue is 'AXValue: line1'
-PASS line2.childAtIndex(0).stringValue is 'AXValue: 2'
-PASS line2.childAtIndex(1).stringValue is 'AXValue: :'
-PASS line2.childAtIndex(2).stringValue is 'AXValue: line2'
+FAIL line1.childAtIndex(0).stringValue should be AXValue: 1. Was .
+FAIL line1.childAtIndex(1).stringValue should be AXValue: :. Was .
+FAIL line1.childAtIndex(2).stringValue should be AXValue: line1. Was .
+FAIL line2.childAtIndex(0).stringValue should be AXValue: 2. Was .
+FAIL line2.childAtIndex(1).stringValue should be AXValue: :. Was .
+FAIL line2.childAtIndex(2).stringValue should be AXValue: line2. Was .
PASS successfullyParsed is true
TEST COMPLETE
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Diego Pino
There are no references to this bug in any TestExpectations. It's probable this bug was solved at some point but it wasn't marked as closed. I'm closing this bug now. If you think this bug report is still valid, please reopen it and add an entry to TestExpectations.