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

Issue 901093 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
User never visited
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Testing extension permission warnings is gone from Permission Warnings extensions doc

Reported by amiag...@gmail.com, Nov 1

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36

Steps to reproduce the problem:
1. Visit https://developer.chrome.com/apps/permission_warnings
2. Look for instructions to testing warnings upon extension upgrade

What is the expected behavior?
The instructions are available.

What went wrong?
The instructions are missing.

Did this work before? Yes 

Does this work in other browsers? N/A

Chrome version: 69.0.3497.100  Channel: n/a
OS Version: 
Flash Version: 

You can view the last version of these instructions here: https://web.archive.org/web/20180114080742/https://developer.chrome.com/apps/permission_warnings#test

Being able to easily test what happens on extension upgrade is important because a new warning auto-disables your extension meaning you will lose a large portion of your users, and as your own documentation points out (https://developer.chrome.com/apps/permission_warnings#permissions_with_warnings), the documentation isn't guaranteed to be complete or accurate (and it's not clear it covers the upgrade case at all):

>Permission tables are updated on a best-effort basis and may contain slight discrepancies with the current warnings.
 
To clarify, the latest version of the page does provide instructions for testing warnings on installation, but this issue is about testing warnings on (extension) upgrade.
Labels: Needs-Milestone
Components: Platform>Extensions>Documentation
Cc: swarnasree.mukkala@chromium.org
Labels: Needs-Feedback Triaged-ET
Tried testing the issue on reported chrome version #69.0.3497.100 using Ubuntu 17.10 by following below steps.

Steps:
=====
1.Launched chrome.
2.Navigated to "https://developer.chrome.com/apps/permission_warnings".
3.Observed at the end of the page there are update permissions.
Note: Same behavior is seen in M-60(60.0.3112.78) also.

Attached screencast for reference.
@reporter: Could you please provide the screenshot of the issue and also request you to confirm if this is the issue you are pointing to.
Thanks.!
901093.webm
10.3 MB View Download
Yes, there is an "Update Permissions" section. But this section gives you no information for how to test permissions warnings on extension update. This documentation used to exist on the page (see https://web.archive.org/web/20180114080742/https://developer.chrome.com/apps/permission_warnings#test) but no longer does.
Project Member

Comment 6 by sheriffbot@chromium.org, Nov 8

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Type-Bug-Regression Target-72 FoundIn-72 M-72 FoundIn-71 FoundIn-70 OS-Mac OS-Windows Type-Bug
As per confirmation from comment#5, able to reproduce the issue on the reported chrome version #69.0.3497.100, latest stable #70.0.3538.110 and latest chrome #72.0.3626.0 using Ubuntu 17.10, Windows 10 and Mac 10.14.1.

The behavior is seen from old M-60builds(60.0.3112.78). This is non-regression issue hence marking it as untriaged and requesting someone from the dev team to look into the issue.
Thanks.!
Status: Untriaged (was: Unconfirmed)
Cc: rdevlin....@chromium.org
Owner: dgash@google.com
Status: Assigned (was: Untriaged)
Yeah, we should add those back.

Sign in to add a comment