Actually Chrome does slow down tabs in the background. On my computer whenever I put a CPU heavy tab in the background, it crawls to a snail's pace. And if you don't touch it in a long time, it is suspended and saved to the hard drive.
Which is why this story is weird. This shouldn't even be an issue.
That is a naive view on it. Javascript can be doing a LOT of things. It could be rotating a product carousel; or it could be running a browser game. In both cases that's something that can use a LOT of CPU, but in the latter case the user might want it to continue processing in the background. How is the browser supposed to differentiate this on its own?
Doing it manually would be great, but then you run into Chrome's obsession with remaining simple and "slim", regardless of whether this happens to the detriment of users.