That's not the same. If websites don't implement a cast app themselves, then Chrome will just mirror the tab to the TV. Whereas catt and similar tools will actually direct the chromecast to download the video file directly and play it. This makes a big difference to quality and performance.
While this is true, newer Chrome versions have a feature where if you fullscreen a video in a tab, it will (within a few seconds, if the video is in a directly supported format) attempt to send the video directly to the Chromecast instead of mirroring the tab. It doesn't always work, but it's much smoother when it does.
That's nice; historically when i did that I'd lose the borders but quality would suffer. Admittedly i mostly did it with streaming content that was not CC compatible though.
So what you're saying is that it's probably better to use a browser, because your bandwidth between your PC and your TV is likely to be much better, as well as having the capability to cast not only web content but also anything on your desktop. Plus a mirror is much easier to control, and some cast capable devices may not have the memory to "download" video files.
What am I missing here? You seem to think it's a bad thing.
sending a video stream from a file on your disk on a computer results in higher quality video on the television than playing a video in your browser and encoding a stream of your browser window and sending that to the chromecast to display on the TV.
