Golden file changes have been found for this pull request. Click here to view and triage (e.g. because this is an intentional change).

If you are still iterating on this change and are not ready to resolve the images on the Flutter Gold dashboard, consider marking this PR as a draft pull request above. You will still be able to view image results on the dashboard, commenting will be silenced, and the check will not try to resolve itself until marked ready for review.

For more guidance, visit Writing a golden file test for package:flutter.

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

Changes reported for pull request #106351 at sha 9e848e8

Won't this introduce pixel snapping on mobile?

Can/should this wait until mobile has opted into fractional translation?

It will be extremely minor, we never noticed the issue until we added desktop targets. We can definitely wait, but there is still a chance we won't be able to remove pixel snapping from mobile yet - in which case it would be a shame to lose this.

Supposidly this reduced the new gen gc count on an opacity benchmak, though that is an odd improvement:

https://flutter-flutter-perf.skia.org/e/?begin=1655741047&end=1655846348&keys=X73cbe951e39b585d6bcb21b8912ac1c1&num_commits=50&request_type=1&xbaroffset=29529

Benchmark looks noisy - it usually gets 2 gcs but sometimes gets zero.

Probably an acceptable level of noise though, those benchmarks were really designed to capture going from 10s or 100s of GCs to much fewer.