The modifications includes:
1) skip focus-within-shadow-*.html tests due to test method changed and causing test timeout
2) sync the failures.list with reftest.list
3) add new failures to the list
MozReview-Commit-ID: HjynNYDuiv4
--HG--
extra : rebase_source : 6b2f087709015882929b2cf533160eb1695067e6
The marker, a red triangle, is clipped during "overflow" property
animation.
MozReview-Commit-ID: CAZ6adTXiQw
--HG--
extra : rebase_source : 888dc520aecba61cd129145ab015780dd8cbc943
Activate WebRender output for filters that introduce only one pixel
differences in tests. Since the filters spec does not seem to specify
how color values are rounded, this output should be spec compliant.
We use gpu for yuv color conversion now. There are some precision problems in gpu path. Mark them fails-if and update the fuzzy-test value.
MozReview-Commit-ID: 6tunOCj3OHB
Disable 461917-1.xhtml under dom/xul/crashtests/ because I cannot reproduce
it locally.
Annotate assert-if on some crashtests (bug 1370830). Other modifications are
all removal of fails-if.
MozReview-Commit-ID: 6Q2A5M5rOry
--HG--
extra : rebase_source : b282a919fcda6287fe2eaa6b139a11f2663ad578
In the an+b syntax, this continues to allow comments and spaces like so:
` an + b `. It does not allow `a n+b`, or `- an+b` or `+ an+b` (and the
same for the `an-b` form). Similarly, it does not allow `- b` or `+ b`.
Additionally, it *does* allow `+/*comment*/n+b` or `-/*comment*/n+b`,
but not `+ n+b` or `-n+b`. This is specced; in this one case we
parse two tokens but do not allow whitespace in between.
MozReview-Commit-ID: INzFGeMPeK7
--HG--
extra : rebase_source : ca5bcf4034759823f79b9a925dc72998d8f0218b
This is because in original gecko, canvas background color will merge to
painted layer with other display items. When advanced canvas background
color is enabled, the "other display items" won't be merged with canvas
background color. Which means the layers that are generated by those
display items may not be opaque. So set fails-if to those tests.
MozReview-Commit-ID: 1WbMU8pGtTC
--HG--
extra : rebase_source : c7bc417cde65ece8589d733a63d4a6e1a161d1fe
This catches a common problem where somebody adds a fuzzy annotation on
a test to work around some minor differences. Later the differences go
away, but since the test harness doesn't catch that, nobody is the
wiser. Subsequently a "real" regression can reintroduce differences
which are hidden by the stale fuzzy annotations.
With this patch, if the annotations are set up properly, the test
harness will flag tests as "UNEXPECTED-PASS" when the differences go
away. This will require the patch author to reduce the allowed fuzziness
parameters, and will make it easier to catch subsequent regressions.
MozReview-Commit-ID: B3rGPFLXkCu