New issue
Advanced search Search tips

Issue 850463 link

Starred by 1 user
Status: WontFix
Owner:
hcarmona@chromium.org
Closed: Jun 2018
Cc:
pnangunoori@chromium.org
nyerramilli@chromium.org
rbasuvula@chromium.org
jawag@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

User is unable to redirected to the "Errors" details page of the respective extension.

Reported by dchau...@etouch.net, Jun 7 2018 
Chrome Version: 68.0.3440.17 (Official Build) Revision	3f4388bf791dc0987401140638818b80d5a81616-refs/branch-heads/3440@{#225} 32/64-bit.
OS: Win(7,8,8.1,10), Mac(10.12.6, 10.13.1, 10.13.6).

What steps will reproduce the problem?
1. Launch Chrome, navigate to chrome://extensions page and enable "Developer mode" toggle button.
2. Click on ‘Load unpacked’ button and Install an extension for which errors can be found.
3. Now click on the "Errors" button and observe.

Actual: User is unable to redirected to the "Errors" details page of the respective extension.
Expected: User should be redirected to the "Errors" details page of the respective extension.

This is a non-regression issue, seen from M-68 series.

NOTE:
1. It is working fine on Market Canary builds (i.e. build # 69.0.3451.0) and issue is observed on equivalent signed build (i.e. build # 69.0.3451.0).
2. This issue is also reproducible on Canary signed build #69.0.3452.0
3. This issue is not reproducible on Linux (14.04 LTS) OS.

Kindly review the attached screen-cast for reference.

Thank you.
Market_Canary_behavior.mov
3.2 MB View Download
Equivalent_Signed_build.mov
4.6 MB View Download

Comment 1 by pnangunoori@chromium.org, Jun 7 2018 

In the equivalent signed builds, we are seeing Warnings as below:

Eg.: There were warnings when trying to install this extension:

> Unrecognized manifest key 'not_a_real_key'.
> Permission 'not_a_real_permission' is unknown or URL pattern is malformed.

Comment 2 by hcarmona@chromium.org, Jun 7 2018

Status: WontFix (was: Assigned)
Working as intended. The subpage contains the same errors, but with additional context showing the code in the manifest file.

Notice the same two warnings can be seen in the screenshot taken from the video
Screenshot from 2018-06-07 10-20-24.png
111 KB View Download

Comment 3 by pnangunoori@chromium.org, Jun 8 2018 

hcarmona@ -- Thanks for looking into this issue. 

As per our daily tasks, we generally perform BAT/FP testing on the equivalent signed builds which will be released into the market. As we are executing the test cases on equivalent signed builds, we are seeing warnings as seen in the screen cast 'Equivalent_Signed_build.mov' from the original comment.

But, as per the test instructions provided for the Feature Issue 812491 we have wrote test cases and it satisfies the functionality which we are seeing in the Chrome market builds.

As the functionality in the equivalent signed builds is contradicting the expected behavior mentioned in test cases, do we need to modify the test cases according to the functionality in equivalent signed builds?

Please guide us going further.

Thanks!
►

Sign in to add a comment