I noticed the same thing in Chrome after upgrading to Chrome 52. I'm fairly sure this is a Chrome bug, and it isn't currently present in Chrome Canary (54) so we probably just need to keep an eye on this for now.
This is very much a Chrome bug. There was a similar bug that could be triggered in RTL and it had to do with it determining the text box width as 1 pixel less than what the text actually laid out as -- I'm guessing because of subpixel rendering differences. We've only seen this on Mac, which would point to a similar thing. This would almost certainly have to be handled within Chrome's rendering engine.