Since we published the Keeping Browsing Experience in Users’ Hands blog in December 2015, we’ve received feedback from the ecosystem and engaged in discussions with the industry. Based on those discussions and feedback, we are making a couple of updates.
We are broadening the scope of the evaluation criteria we blogged about to state:
Programs that change the user browsing experience must only use the browsers’ supported extensibility model for installation, execution, disabling and removal. Browsers without supported extensibility models will be considered non-extensible.
This addition addresses software that modifies the browsing experience, not just those that insert ads into the browsing experience.
Accordingly, we are moving the criterion from the Advertising criteria to become an expansion of our BrowserModifier criteria.
By doing so we are closing additional gaps that impact the browsing experience from outside the browser, not just ad injection software, and are pointing developers to comply with the browser’s respective extensibility models.
Internet Explorer and Microsoft Edge’s policy, for example, can be found at aka.ms/browserpolicy.
In addition, and due to the broadening of the policy, we are further extending the notification up until May 2, 2016.
We continue to encourage developers who may be affected by this policy to work with us during the notification time, and fix their software to become compliant with the new criteria and follow the respective browser policies.
Enforcement starts on May 2, 2016.
Barak Shein and Michael Johnson