Install of packaged apps is not supported on desktop. However, we need a way for editors to download and look at the contents of the packaged app. So, we should switch "install" button to "download" on Reviewer Details page and allow editors to download packaged apps.

Andrew: what do you want to do here?

possibly crazy idea: Could the install <button> on the review page be change to be <a> that looks like a button and installs the same as before when left clicked but acts like a link otherwise (so right click; save as, or middle click would work for a download)? Otherwise two buttons is acceptable. For viewing via Mkt I was expecting a 'View Contents' link like addons have. Bug 784200 mentions the Compare diff viewer and its essentially the same thing.

(In reply to Andrew Williamson [:eviljeff] from comment #2) > possibly crazy idea: > Could the install <button> on the review page be change to be <a> that looks > like a button and installs the same as before when left clicked but acts > like a link otherwise (so right click; save as, or middle click would work > for a download)? I'm confused

Now that we have a "mini manifest" some of this doesn't make sense... I've made the manifest "View" link show the mini manifest. That's now what gets sent to the install API. In that JSON is a path to the zip file you can click on to download the zip file. So via those tools you have both install and download package ability.

(In reply to Chris Van Wiemeersch [:cvan] from comment #3) > (In reply to Andrew Williamson [:eviljeff] from comment #2) > > possibly crazy idea: > > Could the install <button> on the review page be change to be <a> that looks > > like a button and installs the same as before when left clicked but acts > > like a link otherwise (so right click; save as, or middle click would work > > for a download)? > > I'm confused the install button would have been a link to the download package styled as a button but with a left-click onclick handler that did the installing. But as Rob mentions, I think the mini-manifest makes this partially irrelevant (it unlikely we'd want to download the mini-manifest) so the link in the 'View' link will do.

Does that mean this bug is done? It's a bit roundabout (having to click the manifest, then the URL inside it) and the package listed in the mini manifest is (will be) the signed package for reviewers. Would it be better to have a download button which links directly to the uploaded package?

The current implementation (download via the mini-manifest) is acceptable to stop this blocking. An extra download button that links directly to the uploaded package would be great though if its not a lot of additional work!

Sure thing.

The title of this bug is confusing. Based on comment 7 and that we have a file viewer implemented now, I'm going to wontfix.