Not present in Linux Version 63.0.3239.70 (Official Build) beta (64-bit). Or M-64 on Mac 10.12.6, or 63.0.3239.90 on Mac 10.12.6.

Could you please provide a video demonstrating what you see?

And go to "chrome://GPU" and cut-and-paste the contents here?

Does disabling GPU rasterization make any difference? See the internet for how to do that on your platform.

I see the difference. 
It's extremely subtle here in Windows though (sub-pixel rendering), see the attached gif.
To see it *clearly* you can use the built-in Magnifier app at 400%.

Issue 781566 has a test case with a much more pronounced difference.
Bisection range found there applies to this issue as well.
It'd be nice if someone does a per-revision bisect.

Deleted: glitch.gif 36.3 KB

	glitch.gif 36.3 KB View Download

FWIW chrome://gpu

Deleted: gpu.txt 8.0 KB

gpu.txt 8.0 KB View Download

Disabling hardware acceleration in browser settings has no effect here.

In that case this is very minor changes in appearance due to the text shifting to a composited layer for the transition. For good performance we composite (use the GPU to move content around) when animating transitions, but compositing is incompatible with LCD text rendering because the text is no longer integer aligned. The jump from LCD to anti-aliased text creates the appearance change.

We will not be fixing this. On your end you could add "will-change: transform" to the element with the transition on it, and then the text will always be composited.

schenney@, the workaround with "will-change:transform" works for that other issue's test case too.

It's strange though, that unrelated elements with no transition on them are affected.

Thanks guys, this helps!
Strangely enough however, the fix works like a charm in my live example, but not on the page within my project. Well, at least we now know where to look, so we will solve this.

Thanks again!

The behavior of what we call "layer squashing" is probably why unrelated elements get composited on the transition. In DevTools, there is a "Rendering" tool under "More Tools" in the gear menu. That has an option to see the layers for content and might help in debugging your page. Please don't spread will-change: transform around everywhere. Too much of it will hurt performance by creating too many layers.

The NextAction date has arrived: 2017-12-25