Hello,

Thanks for the very detailed bug report. I have a clarifying question:

In the steps to reproduce, you mention navigating to an extension's store page. Should I be installing the extension from the store? Or was the extension already installed on the system?

Thanks!

With respect to comment#1 
Sorry for the confusion 
I installed the extension from web store 
And in step 3 I am giving you the explaination what error message it is giving .
I installed it from web store 
The extension was not already installed .
Thank you 

Adding RB Label as this is a recent Regression. Please remove if not required.
Thank You.

Hi Shruti. I was able to reproduce the issue and am investigating.

++jamhuan@microsoft.com who recently offered to help debug the issue on https://chrome.google.com/webstore/detail/office-online/ndjpnladcallmjemlbaebfadecfhkepb/reviews?hl=en

It looks like the extension tries to open an empty file when the button is pressed (line 9 of app.js?). The content verifier tries to match that empty file against a known file in the extension and fails. Since the file is thought to exist by base::PathExists, the content verifier marks the extension as corrupted.

@jamhuan if you see user feedback about the extension being corrupted, it's likely coming from users on Chrome Dev or Beta. I'll fix it and try to merge it so it doesn't impact any of your users on the Stable channel.

This should block M64.

Note: this was merge into M63 in https://chromium-review.googlesource.com/c/chromium/src/+/736079. We should either revert the merge or merge the fix into M63.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6521b2fc34425253732ee0e02e78fbf1ce5d0c13

commit 6521b2fc34425253732ee0e02e78fbf1ce5d0c13
Author: proberge <proberge@chromium.org>
Date: Tue Dec 05 19:19:26 2017

Extension content verifier: ignore empty relative paths

Some extensions make a request to "/" which confuses the extension
content verifier and causes it to mark the extension as corrupted.

Bug:  791929 
Change-Id: Id594bd714048d33ddcf88fa86b26ce0a7696503c
Reviewed-on: https://chromium-review.googlesource.com/809225
Commit-Queue: proberge <proberge@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521777}
[modify] https://crrev.com/6521b2fc34425253732ee0e02e78fbf1ce5d0c13/extensions/browser/content_hash_reader.cc
[modify] https://crrev.com/6521b2fc34425253732ee0e02e78fbf1ce5d0c13/extensions/browser/content_verify_job_unittest.cc

After discussion with the Chrome TPMs, we decided to revert https://chromium-review.googlesource.com/c/chromium/src/+/736079 from M63. This was done in https://chromium-review.googlesource.com/c/chromium/src/+/809564, hence I'm removing the M-63 release block from this issue.

Requesting a merge into M64 for the fix-forwards submitted in #8. 

As @veranika pointed out, a better long term solution would likely involve ignoring subfolders as well. 

An extension shouldn't corrupt itself just for making a request to one of its existing folders. 

Able to reproduce the issue on Chrome64.0.3282.7/CrOS 10176.4.0 - Peppy

Approving merge to M64 Chrome OS.

Note: Retested the above issue on Beta# 63.0.3239.84 on Win(7,8,10),Mac OS X(10.12.6,10.13.1),Linux(14.04 LTS) and fix is working as intended.
Kindly refer the attached screen cast.

Kindly refer the attached screen cast
Thank you.

Deleted: Verified.mp4 842 KB

	Verified.mp4 842 KB View Download

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/76ed74ef6940586490cd6e68d975235a005c3016

commit 76ed74ef6940586490cd6e68d975235a005c3016
Author: proberge <proberge@chromium.org>
Date: Wed Dec 06 18:08:59 2017

Extension content verifier: ignore empty relative paths

Some extensions make a request to "/" which confuses the extension
content verifier and causes it to mark the extension as corrupted.

(Merging into M64)

Bug:  791929 
Change-Id: Id594bd714048d33ddcf88fa86b26ce0a7696503c
Reviewed-on: https://chromium-review.googlesource.com/809225
Commit-Queue: proberge <proberge@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#521777}(cherry picked from commit 6521b2fc34425253732ee0e02e78fbf1ce5d0c13)
Reviewed-on: https://chromium-review.googlesource.com/811544
Reviewed-by: proberge <proberge@chromium.org>
Cr-Commit-Position: refs/branch-heads/3282@{#59}
Cr-Branched-From: 5fdc0fab22ce7efd32532ee989b223fa12f8171e-refs/heads/master@{#520840}
[modify] https://crrev.com/76ed74ef6940586490cd6e68d975235a005c3016/extensions/browser/content_hash_reader.cc
[modify] https://crrev.com/76ed74ef6940586490cd6e68d975235a005c3016/extensions/browser/content_verify_job_unittest.cc

Marking as fixed now that the issues is reverted in M63 and that the fix is merged into M64. Created a follow-up bug for cleanup: https://bugs.chromium.org/p/chromium/issues/detail?id=792538