OLD | NEW |
1 // This file consists of lines with specifications of what | 1 // This file consists of lines with specifications of what |
2 // to expect from layout test cases. The test cases can be directories | 2 // to expect from layout test cases. The test cases can be directories |
3 // in which case the expectations apply to all test cases in that | 3 // in which case the expectations apply to all test cases in that |
4 // directory and any subdirectory. The format of the file is along the | 4 // directory and any subdirectory. The format of the file is along the |
5 // lines of: | 5 // lines of: |
6 // | 6 // |
7 // fast/js/fixme.js = FAIL | 7 // fast/js/fixme.js = FAIL |
8 // fast/js/flaky.js = FAIL PASS | 8 // fast/js/flaky.js = FAIL PASS |
9 // fast/js/crash.js = CRASH TIMEOUT FAIL PASS | 9 // fast/js/crash.js = CRASH TIMEOUT FAIL PASS |
10 // | 10 // |
(...skipping 957 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
968 // No anti-aliasing on the text. | 968 // No anti-aliasing on the text. |
969 BUG10298 LINUX : svg/custom/use-on-disallowed-foreign-object-3.svg = FAIL | 969 BUG10298 LINUX : svg/custom/use-on-disallowed-foreign-object-3.svg = FAIL |
970 | 970 |
971 // The failures listed below have never passed in Chromium and need to be | 971 // The failures listed below have never passed in Chromium and need to be |
972 // investigated, categorized, and (one hopes) fixed. | 972 // investigated, categorized, and (one hopes) fixed. |
973 | 973 |
974 // These test fail full text diff (but not simplified diff) most likely due | 974 // These test fail full text diff (but not simplified diff) most likely due |
975 // to differing implementations of SVG fonts. They may or may not represent | 975 // to differing implementations of SVG fonts. They may or may not represent |
976 // real bugs which need fixin' | 976 // real bugs which need fixin' |
977 | 977 |
978 // pixeltest failure: font baseline should be on the path, not the centerline | |
979 // There's no baseline at all for this! | 978 // There's no baseline at all for this! |
980 BUG24198 SKIP : svg/batik/text/smallFonts.svg = FAIL | 979 BUG32392 SKIP : svg/batik/text/smallFonts.svg = FAIL |
981 | 980 |
982 // pixeltest failure: font baseline should be on the path, not the centerline | 981 // pixeltest failure: font baseline should be on the path, not the centerline |
983 BUG24198 LINUX WIN : svg/custom/path-textPath-simulation.svg = FAIL | 982 BUG24198 LINUX WIN : svg/custom/path-textPath-simulation.svg = FAIL |
984 | 983 |
985 // This test fails because of an oddity in stroke width calculation. A | 984 // This test fails because of an oddity in stroke width calculation. A |
986 // line is stroked horizontally from Y=100 with stroke width 100, we consider | 985 // line is stroked horizontally from Y=100 with stroke width 100, we consider |
987 // it to be occupying the scan lines from Y=50 to Y=149 inclusive, which | 986 // it to be occupying the scan lines from Y=50 to Y=149 inclusive, which |
988 // is a total of 100 lines. Apple expects it to be occupying Y=150 as | 987 // is a total of 100 lines. Apple expects it to be occupying Y=150 as |
989 // well. The specification isn't very specific on which behavior is correct, | 988 // well. The specification isn't very specific on which behavior is correct, |
990 // but I feel like ours makes more sense. | 989 // but I feel like ours makes more sense. |
991 // The crash started occuring after the WebKit merge 43242:43321 | 990 // The crash started occuring after the WebKit merge 43242:43321 |
992 BUG24198 RELEASE : svg/custom/stroke-width-click.svg = TEXT | 991 BUG24198 RELEASE : svg/custom/stroke-width-click.svg = TEXT |
993 BUG24198 DEBUG : svg/custom/stroke-width-click.svg = CRASH | 992 BUG24198 DEBUG : svg/custom/stroke-width-click.svg = CRASH |
994 | 993 |
995 // The red marker is not drawing the same way as the mac. | 994 // The red marker is not drawing the same way as the mac. |
996 BUG24198 LINUX WIN : svg/custom/marker-changes.svg = FAIL | 995 BUG24198 LINUX WIN : svg/custom/marker-changes.svg = FAIL |
997 | 996 |
998 BUG24198 LINUX WIN : svg/hixie/text/003.html = FAIL | 997 BUG24198 LINUX WIN : svg/hixie/text/003.html = FAIL |
999 | 998 |
1000 // SVG combined with font metrics. | 999 // SVG combined with font metrics. |
1001 BUG24198 LINUX : svg/hixie/text/001-broken.xml = FAIL | 1000 BUG24198 LINUX : svg/hixie/text/001-broken.xml = FAIL |
1002 | 1001 |
1003 // This is an interesting one. | |
1004 // The test has an error which causes it to output a message to the console. | |
1005 // Apple's expected results include this error. Actually, Apple's expected | |
1006 // results include the error twice, because (apparently unique among console | |
1007 // debugging messages) it's generated during rendering. The problem is that | |
1008 // we end up invoking the renderer twice when we're doing pixel tests, once | |
1009 // otherwise, so we get different results depending on whether pixel tests are | |
1010 // enabled. (Neither matches Apple's exactly... when we have pixel tests on, | |
1011 // the duplicate error message ends up at the end of the file, while Apple's | |
1012 // results have them both at the top.) But this test doesn't represent a real | |
1013 // failure in any way and nothing needs to be done to fix it. I'm leaving it | |
1014 // in tests_fixable in case we change the test shell's webview delegate to | |
1015 // ignore console messages while doing a pixel dump | |
1016 BUG24198 : svg/custom/clip-path-referencing-use2.svg = FAIL | |
1017 | |
1018 // These two tests have a highlight color that is different from the Mac, | 1002 // These two tests have a highlight color that is different from the Mac, |
1019 // which is normal because selection color is different between Mac and | 1003 // which is normal because selection color is different between Mac and |
1020 // Windows, but even so it still doesn't look identical because there is still | 1004 // Windows, but even so it still doesn't look identical because there is still |
1021 // some problem with the fill color for the text. | 1005 // some problem with the fill color for the text. |
1022 BUG10300 WIN LINUX : svg/text/text-deco-01-b.svg = FAIL | 1006 BUG10300 WIN LINUX : svg/text/text-deco-01-b.svg = FAIL |
1023 BUG10300 LINUX : svg/text/text-text-08-b.svg = FAIL | 1007 BUG10300 LINUX : svg/text/text-text-08-b.svg = FAIL |
1024 | 1008 |
1025 // SVG masks aren't quite working yet. | 1009 // SVG masks aren't quite working yet. |
1026 // Might also be related to https://bugs.webkit.org/show_bug.cgi?id=21910 | 1010 // Might also be related to https://bugs.webkit.org/show_bug.cgi?id=21910 |
1027 // New tests. We should fix these, but they don't need to block the current rele
ase | 1011 // New tests. We should fix these, but they don't need to block the current rele
ase |
(...skipping 2042 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
3070 BUG32308 DEBUG : fast/frames/cached-frame-counter.html = TIMEOUT | 3054 BUG32308 DEBUG : fast/frames/cached-frame-counter.html = TIMEOUT |
3071 | 3055 |
3072 // WebKit roll: 53290:53313 | 3056 // WebKit roll: 53290:53313 |
3073 BUG32339 LINUX : fast/dom/Window/window-lookup-precedence.html = TEXT PASS | 3057 BUG32339 LINUX : fast/dom/Window/window-lookup-precedence.html = TEXT PASS |
3074 BUG32305 : fast/loader/onload-willSendRequest-null-for-script.html = TEXT | 3058 BUG32305 : fast/loader/onload-willSendRequest-null-for-script.html = TEXT |
3075 BUG_ATWILSON MAC : svg/css/css-box-min-width.html = IMAGE | 3059 BUG_ATWILSON MAC : svg/css/css-box-min-width.html = IMAGE |
3076 BUG_ATWILSON MAC : svg/custom/js-update-bounce.svg = IMAGE | 3060 BUG_ATWILSON MAC : svg/custom/js-update-bounce.svg = IMAGE |
3077 | 3061 |
3078 // New flakyness ? | 3062 // New flakyness ? |
3079 BUG32306 MAC DEBUG: svg/hixie/error/004.xml = CRASH PASS | 3063 BUG32306 MAC DEBUG: svg/hixie/error/004.xml = CRASH PASS |
OLD | NEW |