Bug 224064
| Summary: | [GTK] Layout test media/video-orientation-canvas.html fails | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Carlos Alberto Lopez Perez <clopez> |
| Component: | Media | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | bugs-noreply, jer.noble, peng.liu6, pnormand |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: |
https://bugs.webkit.org/show_bug.cgi?id=221820 https://bugs.webkit.org/show_bug.cgi?id=223850 |
||
Carlos Alberto Lopez Perez
The layout test fails on GTK (and likely on WPE as well, but we are currently skipping media tests on WPE) with this:
--- /home/igalia/clopez/webkit/webkit-flatpak/layout-test-results/media/video-orientation-canvas-expected.txt
+++ /home/igalia/clopez/webkit/webkit-flatpak/layout-test-results/media/video-orientation-canvas-actual.txt
@@ -1,6 +1,6 @@
-EXPECTED (context.getImageData(88, 115, 1, 1).data == [208,0,0,255] with tolerance 5 OK
+EXPECTED (context.getImageData(88, 115, 1, 1).data == [208,0,0,255] with tolerance 5, OBSERVED '[0,0,0,255]' FAIL
EXPECTED (context.getImageData(237, 88, 1, 1).data == [208,0,0,255] with tolerance 5 OK
-EXPECTED (context.getImageData(200, 237, 1, 1).data == [208,0,0,255] with tolerance 5 OK
+EXPECTED (context.getImageData(200, 237, 1, 1).data == [208,0,0,255] with tolerance 5, OBSERVED '[0,0,0,255]' FAIL
END OF TEST
The failure happens since r274076
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Carlos Alberto Lopez Perez
Ok.. the failure just happens because r274076 removed the expected failure from media/video-orientation-canvas.html LayoutTests/platform/wk2/TestExpectations
So this is not a regression
Philippe Normand
Maybe review https://bugs.webkit.org/show_bug.cgi?id=223850 ? :)
Carlos Alberto Lopez Perez
(In reply to Philippe Normand from comment #2)
> Maybe review https://bugs.webkit.org/show_bug.cgi?id=223850 ? :)
Ups.. i missed that
*** This bug has been marked as a duplicate of bug 223850 ***