But unlike the proposal by the blog author, it's already been implemented by at least one browser vendor and received positive responses from another. Sure, we

But unlike the proposal by the blog author, it's already been implemented by at least one browser vendor and received positive responses from another. Sure, we could throw in another spec and maybe Mozilla will implement this one and maybe Safari won't be neutral to the new one, but why go through that effort when there's already a working solution to this problem?