The installType "normal" should be broken down into more distinct installTypes
Reported by
chrome-a...@ironsrc.com,
Jul 10 2016
|
|||
Issue description
UserAgent: 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:
Suggestion to differentiate between webstore and inline installations of extension, with regards to the "installType" value.
1. Install an extension with management premissions (e.g. bahkljhhdeciiaodlkppoonappfnheoi)
2. On dev tools console window, get the extension install type
example JS code: chrome.management.get(chrome.runtime.id, function(ext){ console.log("installType = " + ext.installType); });
3. Perform steps 1-2 on the following:
1. Extension installed via registry sideload installation
2. Extension installed via Chrome webstore
3. Extension installed via inline installation
What is the expected behavior?
Cases 1-3 have different installType value.
1. Extension installed via registry : "installType = sideload"
2. Extension installed via Chrome webstore : "installType = webstore"
3. Extension installed via inline installation : "installType = inline"
What went wrong?
It would be better to differentiate between inline installation via land page vs. Chrome webstore installation.
1. Extension installed via registry : "installType = sideload"
2. Extension installed via Chrome webstore : "installType = normal" (same as inline)
3. Extension installed via inline installation : "installType = normal" (same as webstore)
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
,
Jul 12 2016
Yes -- the Webstore team is working on a revamped stats UI in the developer dashboard, which should include the ability to breakout installations by source.
,
Jul 12 2016
assigned -> jawag per #2. Feel free to dupe this into an existing bug if there is one.
,
Nov 28 2016
,
Jan 11
You started fixing this bug over two years ago. Are you still working on it? You can update the status to "archived", "wontfix", or "closed". You can remove yourself as owner and change status to "untriaged", but if this is still a real bug, please do not sit on it. |
|||
►
Sign in to add a comment |
|||
Comment 1 by rdevlin....@chromium.org
, Jul 12 2016