Bugzilla

Note: the fuzzy mismatching pixels here are just an indication that antialiasing happens a bit differently for transformed pixels in `preserve-3d` contexts vs. in 2D transforms.

I filed bug 1737904 on that problem.

(Chromium presumably  had that same behavior at some point, which is presumably why this test has a fuzzy annotation baked into it, per comment 0 here.  Though I'm not seeing that behavior in Chrome on my current machine, so they may have improved things in recent months.)

Note: the fuzzy mismatching pixels here are just an indication that antialiasing happens a bit differently for transformed pixels in `preserve-3d` contexts vs. in 2D transforms.

I filed bug 1737904 on that problem. [EDIT: and that bug turned out to be a dupe of bug 1339664]

(Chromium presumably  had that same behavior at some point, which is presumably why this test has a fuzzy annotation baked into it, per comment 0 here.  Though I'm not seeing that behavior in Chrome on my current machine, so they may have improved things in recent months.)

Note: the fuzzy mismatching pixels here are just an indication that antialiasing happens a bit differently for transformed pixels in `preserve-3d` contexts vs. in 2D transforms.

I filed bug 1737904 on that problem.

(Chromium presumably  had that same behavior at some point, which is presumably why this test has a fuzzy annotation baked into it, per comment 0 here.  Though I'm not seeing that behavior in Chrome on my current machine, so they may have improved things in recent months.)

Note: the fuzzy mismatching pixels here are just an indication that antialiasing happens a bit differently for transformed pixels in `preserve-3d` contexts vs. in 2D transforms.

I filed bug 1737904 on that problem.

(Chromium presumably  had that same behavior at some point, which would explain why this test has a fuzzy annotation baked into it, per comment 0 here.  Though I'm not seeing that behavior in Chrome on my current machine, so they may have improved things in recent months.)