Chrome for Windows is one of the most common setups for browsing the internet, so this isn't an edge case situation. That post originated in 2009, over 4.5 years ago.

It's good to hear it might be finally addressed, but I wouldn't say they've been actively working on it, when all the other popular browsers had this sorted years ago.