Bugzilla

Nowadays we only fail one subtest:
```
@position-try rule does not win over transitions

FAIL message: assert_equals: expected 30 but got 5
```

It looks like the testcase is expecting that element to start at its `--pf {`-granted `top: 50px;` value and snap halfway to the target `top: 10px` function (using the "steps" easing function in the transition styling).

But for whatever reason, we're instead starting that element at its `top: 0` value that's granted by the `.abs {` class, and we're transitioning it from *there* to `top:10` (and correctly pausing halfway).

So the issue here isn't with the transition, but rather it's with figuring out that we should be triggering the position fallback.

Nowadays we only fail one subtest (of six):
```
@position-try rule does not win over transitions

FAIL message: assert_equals: expected 30 but got 5
```

It looks like the testcase is expecting that element to start at its `--pf {`-granted `top: 50px;` value and snap halfway to the target `top: 10px` function (using the "steps" easing function in the transition styling).

But for whatever reason, we're instead starting that element at its `top: 0` value that's granted by the `.abs {` class, and we're transitioning it from *there* to `top:10` (and correctly pausing halfway).

So the issue here isn't with the transition, but rather it's with figuring out that we should be triggering the position fallback.