The problem is that the Chrome team shouldn't be selectively implementing parts of the html5 standard [1]. It shouldn't matter how many users desire the functionality after it's accepted by the w3c.
Of course, Chrome could implement whatever it likes if it drops any claim to be standards compliant, but until that happens...