OriginTrials

Early on in the article you might see that you have to sign up for a token to use it while it's in the trial stage. If you're wondering what this is about, see https://github.com/GoogleChrome/OriginTrials/blob/gh-pages/d... > The TL;DR is that we strongly value the feedback of real web developers (that means you!) during the process of designing and standardizing new features. We believe origin trials provide a good way of encouraging that feedback, while being extremely careful that the experiments aren’t used by sites in production-critical roles or as if they’re finalized features.

Chrome team member here, and one of the people working on the portals spec. This isn't accurate. This feature is being developed behind a flag, as it's still highly experimental and undergoing a lot of change. There is an origin trial [1] for mobile-only same-origin-only portals [2] which people can use to test how well this works in the wild, but it's nowhere near shipping. You can learn more about the intention of the element in [3]. [1]: https://github.com/GoogleChrome/OriginTrials/blob/gh-pages/d... [2]: https://developers.chrome.com/origintrials/#/view_trial/-768... [3]: https://github.com/WICG/portals/blob/master/README.md

Also related: Chrome Origin Trials: https://github.com/GoogleChrome/OriginTrials

> waterfall concept is considered bad taste in the web world Typically the result is a terrible feature like AppCache. Today, I think origin trials are the best alternative to waterfall. https://github.com/jpchase/OriginTrials It allows browsers to experiment with features, even breaking them and deleting them, while working with real web developers and users on actual web sites. > So why can’t they do these breaking changes, too? When browser vendors break web sites, their users complain and switch browsers to another vendor that "works."