Aha, two other interesting things: (1) The reference case has extremely magical/"tuned" fractional values in its reference case: `<polygon points="0,0 150,54.595535 236.602540,204.595535 86.602540,150" style="fill:lime"></polygon>` It's not surprising that there's a little bit of fuzz from matching a transformed div against that. (2) The testcase already has a fuzzy annotation that's nearly sufficient (presumably because this is similarly-fuzzy in other browsers): ``` <meta name="fuzzy" content="maxDifference=17-233;totalPixels=90-858"> ``` So: quite reasonable to bump the upper edge of both ranges a little to accomodate our observed fuzziness.
Bug 1841349 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Aha, two other interesting things: (1) The reference case has extremely magical/"tuned" fractional values in its polygon: `<polygon points="0,0 150,54.595535 236.602540,204.595535 86.602540,150" style="fill:lime"></polygon>` It's not surprising that there's a little bit of fuzz from matching a transformed div against that. (2) The testcase already has a fuzzy annotation that's nearly sufficient (presumably because this is similarly-fuzzy in other browsers): ``` <meta name="fuzzy" content="maxDifference=17-233;totalPixels=90-858"> ``` So: quite reasonable to bump the upper edge of both ranges a little to accomodate our observed fuzziness.