New Tab Replacement extensions issues
Extensions are turned off by default when they change the new tab replacement. Especially when users specifically allow the extension to replace the new tab page, this is very confusing and unwanted behavior.
This has originally been reported by 'Jean Nomdes' on https://feedbackportal.microsoft.com/feedback/idea/402b9b7c-cf79-ec11-a81b-0022484f5e0c who mentioned:
I have an extension that is changing the new tab to a page local to the extension. The user can also access this page from a menu when clicking on extension icon. But if user decides to have something else for the new tab, when changing the settings the extension is turned off!
Since an extension can override new tab and do other things, why the new tab is controlling entirely the extension status? I think it should not.
and
Another thing completely crazy you have put in place. On the Edge store Add-on page, a user clicks "Get" then gets a message to accept permission "Change what you see when open a new tab".
- User clicks "Accept" and clearly understands what's going on, since it's written.
- Right after extension is Disabled ?!
- A box telling the user that the extension is disabled for safety, with a link to how to enable an extension page You just told the user the extension is going to change the new tab and the user just accepted. Why don't you just accept the user's decision? You just told them extension may not be safe!
- 50% of people won't go to the page 'how to" because they did not see the box or don't know what to do, or just got scared.
- 50% of people won't understand instructions, be too lazy, or just don't find the extensions page.
- Let's say then 25% users actually went to turn back on the extension. At this stage, when the user opens a new tab, the message says "Is it the new tab you expected" with a revert button ?! 50% of users will be scared or don't even remember what's going on if some time passed since they turned on the extension. So we are left with 12.5% of users who wanted to try the extension actually trying it.
It's frustrating, because us developers spend our time and money making great products, but in the end Edge just kills our chances to have users trying them.
Our engineering team is currently tracking this and will be prioritized in future. Thank you!
Thanks @nagachaitanyalokam for re-opening. We can track this here until closure