I&#x27;m guessing the problem this is trying to solve<p>Originally we had prefixed APIs. webkitAudioContext for example. The idea was the prefix would be removed. Unfortunately the problem was thousands of websites would use the prefixed API. Now you can&#x27;t remove the prefixed version without breaking many many sites. Worse, there&#x27;s even arguably an incentive for other browser to add someone else&#x27;s prefix because they want their browser to run all those same sites.<p>So, a couple of years ago the browser vendors all agreed, no more prefixes. They&#x27;ll put all the new stuff behind flags that developers can opt into. The problem with that is no one uses them. The users aren&#x27;t going to set the flag so no devs have any reason to try out the APIs. There&#x27;s no re-world usage to see that the APIs work, to see what issues come up.<p>So, there&#x27;s this one. Select a few special devs, let them use the features, enable those features for their domain only. Real users get to use the features with no work on their part. It solves the problem to some extent. The devs know the feature might not last. They&#x27;re also signed up to get notification if the feature is going to change or be removed. And, I guess their motivation is to one up their competitors.<p>And that last part is the whole problem with this proposal. Unless any dev can sign up then only special &quot;chosen&quot; devs get the competitive advantage. That feels wrong for some reason. I don&#x27;t have a better solution to suggest though.<p>edit:<p>-- ugh --<p>I suppose I should have clicked the link which said all of this<p><a href="https:&#x2F;&#x2F;infrequently.org&#x2F;2015&#x2F;08&#x2F;doing-science-on-the-web&#x2F;" rel="nofollow">https:&#x2F;&#x2F;infrequently.org&#x2F;2015&#x2F;08&#x2F;doing-science-on-the-web&#x2F;</a>