Microsoft Edge Origin Trials

Getting Started

Register for an Experiment

Our registration process is consistent with Chrome Origin Trials, simply click the Register button for any of the available experiments listed above. Follow the prompts in the registration form and we'll send you a valid token to use on your site.

Using an Origin Trial Token

There are two ways to use the tokens provide in your page:

Add an origin-trial tag to the head of any page.

                    <meta http-equiv="origin-trial" content="your-token-goes-here">
                

Alternatively, you can add an `Origin-Trial` header to your HTTP server response.

                    Origin-Trial: your-token-goes-here
                

When a token is found in a document, Microsoft Edge will automatically turn on the Edge Feature Flag corresponding to the trial for which the token is valid. This will allow visitors of the application to use the feature despite it's off-by-default state in their local browser.

Developer Guidelines

Allowed Origins

Edge origin trials only support SSL-enabled domains. For localhost testing of a feature, please use the appropriate Edge Feature Flag located in about://flags. In the future, we may publish public tokens that are valid for localhost testing.

Subdomains, URL Paths and Query Params

Origin trial tokens can be configured to support a single domain or subdomain, but they can also be configured to support wild card subdomains for a specific domain. For example, a developer can register https://beta.example.com without subdomain support or a developer can register https://example.com with the subdomain support checkbox selected at registration time to enable all subdomains of that origin.

Paths and query parameters are not supported by the origin trial system. URIs that are submitted with trailing paths or query parameters, such as https://example.com/path/new-feature will be registered as the root domain.

Origin Trial Duration

Once you have registered for a trial, your token will be valid until the expiration date listed on the trial informational card. After this date, the token will no longer function and the feature associated with the trial will be considered ready to ship or be brought back for further development based on developer feedback.

A browser feature team may decide to early-end an experiment in case of any major security incidents caused by the feature, or they have collected enough feedback and concluded the currently proposed API does not meet the web developer needs, and a major redesign need to happen. We will be sending out emails to all developers enrolled in an experiment in the case of early-end.

Providing Feedback on an Origin Trial

If you would like to provide public feedback for a particular trial, please click the issues button located next to the registration button for that trial. We track all feedback as GitHub issues in order to allow for public discourse on ergonomics and stability of a feature.

Opting out of an experiment

To opt out of an experiment, you can simply remove the token we have provided from the <meta> tag or from the server response headers.

Experimental feature implementation best practices

MDN has a great resource on best practices for feature detection, you can view it here. We encourage all developers to treat origin trials as experimental and provide graceful fallback mechanisms should the token expire or the browser team choose to discontinue an active trial.