No one said it can’t go anywhere ever. There are privacy concerns that should be vetted and discussed before it moves forward in my opinion. You however seem to be entirely against the notion that it is an issue. From that you’re refusing to try and actively work towards a solution that respects users. The only person currently that is holding this request back, is yourself.
An important part of the specification process is having push-back in various areas. It helps make the idea more concrete even if the original proposal is unchanged. People making requests need to be accepting of this and attempt to be productive within it. If you’re not willing to even consider that even one part of your suggestion is wrong in the slightest; then the process as a whole becomes much more frustrating and laborious than it otherwise would be for everyone involved.
If this push-back doesn’t happen, things like AppCache happen. You throw a bunch of brilliant people into a room to solve a problem in mostly isolation. That spec then ends up being so narrow in applicable uses it is nearly unusable for the majority of people. That’s just one example of how things can go wrong if parts of proposals aren’t questioned.
If you’re going to propose web features, you need to be prepared for this. It involves understanding that you’ll need to defend various points. Provide data to support your claims. Have processes and examples ready to show developers on their own hardware what you mean if it is something that can run in some form today. That way, you can construct a strong case for your request as it was made. It also means being prepared that maybe you aren’t considering the whole situation. In those cases, you may need to compromise in some fashion with browser vendors or developers from the community contributing to these discussions.