Installing extension via registry, in combination with installing the same extension via inline, causes bad user experience
Reported by
chrome-a...@ironsrc.com,
Jul 10 2016
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.49 Safari/537.36 Steps to reproduce the problem: 1. Install extension via registry (sideload) and restart Chrome. 2. The "registry installation" popup (image attached) appears. 3. At this stage, the extension's installType is "sideload" 4. Choose "Remove from Chrome". 5. Restart Chrome (make sure all Chrome processes were terminated). 6. Install the same extension (same ID) via inline (or webstore). 7. At this stage, the extension's installType is "normal" 8. Remove the extension from Chrome. 9. Restart Chrome (make sure all Chrome processes were terminated). What is the expected behavior? Chrome browser would stop suggesting to install the extension (as the user constantly declined/removed the extension) What went wrong? The "registry installation" popup (image attached) is shown again, even though the user declined previous popup and removed the extension. WebStore page: Did this work before? No Chrome version: 51.0.2704.106 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 22.0 r0 There are a lot of end users that installed a specific extension in the past via registry, declined it, and later installed it via inline installation. If those users later uninstalled the extension, the popup would re-appear. This behavior could be very annoying to users who aren't familiar with Chrome's internal workings. This probably what caused several complaints about such extensions.
,
Jul 12 2016
lazyboy@ has done work in this area.
,
Jul 12 2016
,
Jul 13 2016
This happens b/c we blow away *all* prefs (including Extension::EXTERNAL_EXTENSION_UNINSTALLED) during uninstallation of a regular (webstore installed) extension. https://cs.chromium.org/chromium/src/extensions/browser/extension_prefs.cc?rcl=1468351174&l=1134 The fix wouldn't be too trivial. I'd like to learn a bit more about how frequent this can be in practice, i.e. installing the same extension from webstore that was dropped into the registry before...
,
Jul 13 2016
/cc asargent who is also aware of this issue.
,
May 15 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by robertshield@chromium.org
, Jul 12 2016