Comment by Robdel12 2 days ago
I really dislike when this happens. Completely side steps the standards process and puts forth an API that will have to be now considered since it’s in use. Chrome has done this before, too, I’m pretty sure with web components. Leading to the mess that they are.
This is part of the standards process. Incubation happened here https://github.com/WICG/PEPC now on to Origin Trials before Standardization
I think that’s kinda misleading, isn’t it? You make it sound like it’s making good progress towards standardisation. They asked for feedback from other browser vendors, everybody said no, and they are shipping it anyway. Is “incubation happened, now on to origin trials before standardisation” really a suitable summary of that?
It cannot be a standard until two browsers ship the API.
Yes, when people complain about what they're doing, they can say "this is just the way the standards process works".
It's not. There are now probably dozens (if not more) "standards" that are shipped in Chrome because "it's part of standards process".
Google creates an excuse of a standard proposal. Other browser vendors find major issues, or outright say "no", Google still ships the "standard".
Well, It's on an Origin Trial, so it's only "in use" for people that have explicitly turned it on. There's not much to dislike.