Issue metadata
Sign in to add a comment
|
Enabling “Allow access to file urls” option disables the extension with error “Not from Chrome Web Store”
Reported by
sury...@gmail.com,
Aug 17 2016
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Steps to reproduce the problem: 1. Dragged and Dropped chrome extension ( .crx file) 2. Enabled "Allow access to file urls" in the Chrome://extensions 3. after step #2, extension getting disabled with message "Not from Chrome Web Store". What is the expected behavior? Non webstore store extension should not get disabled. What went wrong? Extension getting disabled. WebStore page: Did this work before? No Chrome version: 52.0.2743.116 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 22.0 r0 I am developing chrome extension which requires access to file opened with file:// protocol. During the development i installed this extension by dragging and dropping in the Chrome://extensions. Extension is getting disabled as soon as give "Allow access to file urls" permission. Messages that say "Not from Chrome Web Store" . Publishing to webstore is not an option at the moment.
,
Sep 7 2016
any update?
,
Oct 18 2016
Confirm same issue with Chrome 54.0.2840.59 running on OS X Yosemite 10.10.5
,
Oct 19 2016
surya66@ - Could you please provide a sample .crx file to test this issue. Thanks...!!
,
Oct 19 2016
,
Oct 27 2016
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 29 2016
Able to reproduce the issue on Windows 10 and Mac 10.12.2 using chrome reported version #52.0.2743.116 and latest canary #57.0.2965.0. Unable to reproduce this issue on Linux. Bisect Information: ===================== Good build: 49.0.2581.0 Revision(363079) Bad Build : 49.0.2582.0 Revision(363328) Change Log URL: https://chromium.googlesource.com/chromium/src/+log/d8b4998c6d071d1fd0a06004a29d774b2b2c6de6..cfeeea2c8e840dd67af7463088bf02bf200097d0 Unable to find any suspect from the above change log however, suspecting the below change Review url: https://codereview.chromium.org/1492403002 avi@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Thanks...!! Thanks...!!
,
Dec 29 2016
That bisect doesn't make sense to me. This is an extensions issue; sending to an extension peep.
,
Dec 29 2016
This is largely WAI. The reason the extension is being disabled is because we disallow extensions that aren't from the webstore on Windows and Mac, with the exception of policy-installed extensions. Drag-and-dropping extensions allows them to be installed for a very brief time, but we'll disable them when we reload them (which happens on triggering allow in file mode or other options), as well as periodically at other times.* If you are developing an extension, the best approach is to load it as an unpacked extension through the chrome://extensions page - this is the intended way to work with unpublished extensions. *We could also disallow drag-and-drop installation entirely, but it's useful for a few different things, and the risk vector is pretty small since we disable it soon afterwards (as this issue has seen). |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ssamanoori@chromium.org
, Aug 19 2016