Bugzilla

(In reply to Jonathan Watt [:jwatt] from comment #20)
> (In reply to Daniel Holbert [:dholbert] from comment #16)
> > I have the makings of a test for this, I think, BTW (using mozPrintCallback in a canvas in a WPT-style print test).
> 
> Does that work by scaling up the rendering or something?

Exactly, yeah; I'm just comparing Ahem `X` glyph, drawn-to-a-canvas in mozPrintCallback, vs. `<div>X</div>` essentially, under the influence of `transform: scale(2)` for example.

Interestingly: when the canvas isn't scaled, I do get a column of antialiased gray pixels at the right edge of the Ahem glyph, only on macOS, even with the fix that landed here.  But with `scale(2)` and `scale(4)`, those gray pixels go away.

I agree that a "print reftest" of the flavor that checks-for-strings would be great, too, but I don't have cycles to add one of those right now.

(In reply to Jonathan Watt [:jwatt] from comment #20)
> (In reply to Daniel Holbert [:dholbert] from comment #16)
> > I have the makings of a test for this, I think, BTW (using mozPrintCallback in a canvas in a WPT-style print test).
> 
> Does that work by scaling up the rendering or something?

Exactly, yeah; I'm just comparing Ahem `X` glyph, drawn-to-a-canvas in mozPrintCallback, vs. `<div>X</div>` essentially, under the influence of `transform: scale(2)` for example.

Interestingly: when the canvas isn't scaled, I do get a column of antialiased gray pixels at the right edge of the Ahem glyph (when drawn with mozPrintCallback).  That only happens on macOS, and it happens even with the fix that landed here.  But with `scale(2)` and `scale(4)`, those gray pixels go away.

I agree that a "print reftest" of the flavor that checks-for-strings would be great, too, but I don't have cycles to add one of those right now.

(In reply to Jonathan Watt [:jwatt] from comment #20)
> (In reply to Daniel Holbert [:dholbert] from comment #16)
> > I have the makings of a test for this, I think, BTW (using mozPrintCallback in a canvas in a WPT-style print test).
> 
> Does that work by scaling up the rendering or something?

Exactly, yeah; I'm just comparing Ahem `X` glyph, drawn-to-a-canvas in mozPrintCallback, vs. `<div>X</div>` essentially, under the influence of `transform: scale(2)` for example.

Interestingly: when the canvas isn't scaled, I do get a column of antialiased gray pixels at the right edge of the Ahem glyph (when drawn with mozPrintCallback).  That only happens on macOS, and it happens even with the fix that landed here.  But with `scale(2)` and `scale(4)`, those gray pixels go away (in a build with the fix that landed here).

I agree that a "print reftest" of the flavor that checks-for-strings would be great, too, but I don't have cycles to add one of those right now.