New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 740913 link

Starred by 3 users

Issue metadata

Status: Archived
Owner: ----
Closed: Jul 20
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Confusing UI on after mandatory move to Settings Overrides API

Reported by partn...@traffisco.com, Jul 11 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.50 Safari/537.36

Steps to reproduce the problem:
1.  Use tabs API to open a new tab from extension
2. Update the extension to use the new mandatory Settings Overrides API (starting from August 1 2017)
3. User get a "Is this is what you expected to see" notification 

What is the expected behavior?
User should not get this notification if the extension used to open a new tab and no new functionality is added in the update. 

What went wrong?
Users are unaware that the update took place and not expecting to see the "new tab is changed notification" and just blindly click the "Restore settings" button loosing the new tab override functionality without knowing it.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 60.0.3112.50  Channel: stable
OS Version: OS X 10.12.5
Flash Version: 

After the notification from the chrome store to update extensions to use the proper API the updated extension have a 70%-90% drop in active users.
I understand that users should be aware about the changes that the extension makes to their browser and have the ability to restore those changes. With this new change, long time extension users(that know what the extension does) disable the extension without even knowing.
 
Cc: krajshree@chromium.org
Components: Platform>Extensions
Labels: Needs-Feedback
partners@ - Thanks for filing the issue...!!

Could you please provide a sample test file or URL to triage the issue from TE end.
This will help us in triaging the issue further.

Thanks...!!
Steps to reproduce:
1. Upload old_API.zip to the chrome store.
2. Install the extension.
3. Upload the extension with the new API with update_to_the_new_version.zip

At some point the extension will update in the browser. Upon opening a new tab(at some random time from the user prospective) a VERY INTIMIDATING popup will appear that says that some extension changed the browser settings. Users don't really can associate the popup with they beloved extension and blindly click "Restore Settings". This is a very bad UI. The popup shout at very least have the extension icon and name in that popup so users can really know what happening. 
In the end March developers lost up to 90% of their user base after updating to the new API. 
Attached the extension files, screenshot of the popup, screen shoot of a random extension stats that shows the users drop the day they updated the extension.

Also, the impressions(searches from the chrome store) also dropped in the same date. I don't understand how's that related but it happened. 

Loosing 75% of users on average is very bad.   
old_API.zip
9.6 KB Download
update_to_the_new_version.zip
9.4 KB Download
Screen Shot 2017-07-16 at 1.47.58 PM.png
40.6 KB View Download
stats.jpg
151 KB View Download
Project Member

Comment 3 by sheriffbot@chromium.org, Jul 17 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: kkaluri@chromium.org
Components: Webstore
Labels: TE-NeedsTriageHelp
As per comment #2, We need to upload extension to Webstore since we can't do it from TE-End adding Webstore component and "TE-NeedsTriageHelp" label for further triage from dev team.
Project Member

Comment 5 by sheriffbot@chromium.org, Jul 20

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment