If I delete the .ini file and run the test locally, I see the failure: ``` 0:10.37 TEST_END: Test OK. Subtests passed 0/1. Unexpected 1 FAIL overscroll-behavior prevents scroll-propagation in the area and direction as specified - assert_equals: expected 100 but got 0 verify_y_prevented_and_set_boundary_prevents_x/<@http://web-platform.test:8000/css/css-overscroll-behavior/overscroll-behavior.html:105:18 Test.prototype.step@http://web-platform.test:8000/resources/testharness.js:2590:25 verify_y_prevented_and_set_boundary_prevents_x@http://web-platform.test:8000/css/css-overscroll-behavior/overscroll-behavior.html:104:8 @http://web-platform.test:8000/css/css-overscroll-behavior/overscroll-behavior.html:169:42 ``` The logging isn't super-helpful here because the test is passing the assertion description to the wrong function; I filed bug 1790138 on that. But in any case, it looks like this is the check that's failing: https://searchfox.org/mozilla-central/rev/31368c7795f44b7a15531d6c5e52dc97f82cf2d5/testing/web-platform/tests/css/css-overscroll-behavior/overscroll-behavior.html#101,104-105 ```html function verify_y_prevented_and_set_boundary_prevents_x() { ... test.step(function() { assert_equals(root.scrollTop, 100); ``` It looks like we're applying the `dy` from the very first entry in `test_cases` here, but the test is expecting it to get nerfed: ``` const test_cases = [ { x: 200, y: 500, dx: -200, dy: -200 }, ``` If you change `dy` to e.g. -15 there, then the test failure message says "...but got 85"; whereas the test continues to pass in Chrome (where this particular dy value has no effect). So it looks like this is a case where we're scrolling when the test expects us not to. As to why that's happening, I don't know; hiro and botond are probably more familiar with `overscroll-behavior` than I am and might be able to figure out more here.
Bug 1689546 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
If I delete the .ini file and run the test locally, I see the failure: ``` 0:10.37 TEST_END: Test OK. Subtests passed 0/1. Unexpected 1 FAIL overscroll-behavior prevents scroll-propagation in the area and direction as specified - assert_equals: expected 100 but got 0 verify_y_prevented_and_set_boundary_prevents_x/<@http://web-platform.test:8000/css/css-overscroll-behavior/overscroll-behavior.html:105:18 Test.prototype.step@http://web-platform.test:8000/resources/testharness.js:2590:25 verify_y_prevented_and_set_boundary_prevents_x@http://web-platform.test:8000/css/css-overscroll-behavior/overscroll-behavior.html:104:8 @http://web-platform.test:8000/css/css-overscroll-behavior/overscroll-behavior.html:169:42 ``` The logging isn't super-helpful here because the test is passing the assertion description to the wrong function; I filed bug 1790138 on that. But in any case, it looks like this is the check that's failing: https://searchfox.org/mozilla-central/rev/31368c7795f44b7a15531d6c5e52dc97f82cf2d5/testing/web-platform/tests/css/css-overscroll-behavior/overscroll-behavior.html#101,104-105 ```html function verify_y_prevented_and_set_boundary_prevents_x() { ... test.step(function() { assert_equals(root.scrollTop, 100); ``` It looks like we're applying the `dy` from the very first entry in `test_cases` here, but the test is expecting it to get nerfed: ``` const test_cases = [ { x: 200, y: 500, dx: -200, dy: -200 }, ``` If you change `dy` to e.g. -15 there, then the test failure message says "...but got 85"; whereas the test continues to pass in Chrome (where this particular dy value has no effect). So it looks like this is a case where we're scrolling (by that first `test_cases`'s `dy` value) when the test expects us not to. As to why that's happening, I don't know; hiro and botond are probably more familiar with `overscroll-behavior` than I am and might be able to figure out more here.
If I delete the .ini file and run the test locally, I see the failure: ``` 0:10.37 TEST_END: Test OK. Subtests passed 0/1. Unexpected 1 FAIL overscroll-behavior prevents scroll-propagation in the area and direction as specified - assert_equals: expected 100 but got 0 verify_y_prevented_and_set_boundary_prevents_x/<@http://web-platform.test:8000/css/css-overscroll-behavior/overscroll-behavior.html:105:18 Test.prototype.step@http://web-platform.test:8000/resources/testharness.js:2590:25 verify_y_prevented_and_set_boundary_prevents_x@http://web-platform.test:8000/css/css-overscroll-behavior/overscroll-behavior.html:104:8 @http://web-platform.test:8000/css/css-overscroll-behavior/overscroll-behavior.html:169:42 ``` The logging isn't super-helpful here because the test is passing the assertion description to the wrong function; I filed bug 1790138 on that. But in any case, it looks like this is the check that's failing: https://searchfox.org/mozilla-central/rev/31368c7795f44b7a15531d6c5e52dc97f82cf2d5/testing/web-platform/tests/css/css-overscroll-behavior/overscroll-behavior.html#101,104-105 ```html function verify_y_prevented_and_set_boundary_prevents_x() { ... test.step(function() { assert_equals(root.scrollTop, 100); ``` It looks like we're applying the `dy` from the very first entry in `test_cases` here, but the test is expecting it to get nerfed: ``` const test_cases = [ { x: 200, y: 500, dx: -200, dy: -200 }, ``` If you change `dy` to e.g. -15 there, then the test failure message says "...but got 85"; whereas the test continues to pass in Chrome (where this particular dy value has no effect). So it looks like this is a case where we're scrolling (by that first `test_cases` entry's `dy` value) when the test expects us not to. As to why that's happening, I don't know; hiro and botond are probably more familiar with `overscroll-behavior` than I am and might be able to figure out more here.