Sorry that should read 
'When printing on a Terminal Services setup additional spacing is produced in the print.'

Sidenote... if you change 8.2pt for 10.9px the issue does not appear to present itself - so I think it might be only applicable to points.

Specifically, you are referring to the "Your laptop ... one of our's" line in the bottom right box, which has odd spacing in Terminal Services JSFiddle.pdf, right?

I see this with Remote Desktop. Will bisect.

halcanary: Does this look familiar?

Bisected to https://chromium.googlesource.com/chromium/src/+log/e55d9d3bf..e58743c43

So probably r406860? Not sure if we want to file this under Blink>Fonts?

r406860 was committed in - 54.0.2804.0. Does any one think that this is going to be a stable blocker?

We are planning a Stable re-spin today/tomorrow. 

While annoying for affected users, I don't think this should be a Stable Release Blocker because severity of the bug is not that bad, and the number of affected users is probably not that high.

This seems to have something to do with text layout/glyph measurement differences between the remote and the local systems.

chrisnevill28@, could you produce smaller PDFs by just highlighting the interesting text and hitting `Ctrl-p`?  That'll make it easier to compare just the important differences between the two.

Thanks for the bug report.

I had no idea you could selectively print like that - learn something every day.  Excuse the different account it's the same Chris.

Deleted: local - JSFiddle selected.pdf 62.7 KB

local - JSFiddle selected.pdf 62.7 KB Download

Deleted: Terminal Services JSFiddle selected.pdf 52.6 KB

Terminal Services JSFiddle selected.pdf 52.6 KB Download

Basically for what ever reason it seems to create odd additional spacing on the TS version.  In our original reports the spacing appeared in the middle of words, and such like spread across multiple paragraphs.

halcanary: Since I can also reproduce it, if there's anything you need, like making a SKP or trying out a patch, let me know.

I suspect that  SkGlyphCache::getGlyphIDAdvance(gid)::fAdvanceX are different values for the client and the server.

thestig@, can you apply https://skia-review.googlesource.com/c/4202/ and see if that fixes anything?

May be we should get this fixed before M55 hits stable,tagging accordingly.

if it is a release blocker and if https://skia-review.googlesource.com/c/4202/  fixes it, then let's land that for now.  It's inefficient, but at least it works.

But first, let's hear from Lei.

Adding Lei (thestig@), could you ptal comment #13 and #15?

halcanary: Yes, the patch fixes it for me via RDP.

Mind if I assign this to you? I think I can't help here.

Okay.

I'm going to land this fix, but it doesn't really address the underlying problem, which seems to be that somewhere someone is getting incorrect typeface metrics.

M54 Stable is already deployed today,we should target to M55.

Well, we should definitely try merging to M55 first, but we may still want to consider M54 for Terminal Services (i.e. enterprise) users.

Please request a merge to M55 ASAP if cl is ready to be merged to M55. Thank you.

Approving merge to M55 branch 2883 based on comment #17 and #21. Please merge ASAP. Thank you.

[Automated comment] Request affecting a post-stable build (M54), manual review required.

(regarding m54, this cherry-pick - https://skia-review.googlesource.com/c/4343/ - exists, but I don't know how important it is.)

https://skia-review.googlesource.com/c/4342/