Why? It seems like new API's should be tested with real users before becoming a web standard, and origin trials were a big improvement over what happened before with webkit specific CSS, etc.

▲

maxloh 2 days ago | parent | next [-]

This is actually the case for ECMAScript (JavaScript).

All proposals must first be implemented by some browser vendors at Stage 3:

> The proposal has been recommended for implementation.

Then, the proposal shall be included in the standard at Stage 4:

> Two compatible implementations which pass the Test262 acceptance tests

https://tc39.es/process-document/

▲

anthem2025 2 days ago | parent | prev [-]

Because they have a history of abusing their monopoly on browsers to push new standards that only help them.

▲

skybrian 2 days ago | parent [-]

What are some examples of that for web standards?

▲

LikesPwsh 2 days ago | parent [-]

FLOC/Cohorts API, AMP, Manifest V3, Widevine, WEI.

▲

bitpush 2 days ago | parent [-]

None of those are web standards. They are web technologies, but they arent standards unless other browsers agree to it.

So pray tell, what should the browser do? Just sit on their hands, like Firefox? That's a classic example of how a browser could be mismanaged.

	▲	lightedman 2 days ago \| parent [-]
		Widevine is absolutely a web DRM standard. Literally every major streaming service uses it.