Finally. I remember roughly two years ago I was working as a typographical consultant, and this was by far the most irritating issue I came across. It surprised me that despite being aware of the issue, the Chrome team still hadn't fixed it.
I agree! As a front end dev, this has frustrated me and clients for yeaaaaars. Can't believe they're finally like 'oh, I guess we better fix it'... but it's not even turned on by default for another two versions :/