Update status page UI to match mocks

RESOLVED WONTFIX

Status

Marketplace
Developer Pages
P3
normal
RESOLVED WONTFIX
3 years ago
2 years ago

People

(Reporter: robhudson, Unassigned)

Tracking

Avenir
x86
Mac OS X
Points:
---

Details

(Whiteboard: [marketplace-transition])

(Reporter)

Description

3 years ago
In bug 1006816 the mocks created updated the UI around status and versions. This bug is to go over the mocks and implement the UI changes.
can you link to the mocks or detail the changes?
(Reporter)

Comment 2

3 years ago
Mocks:
http://people.mozilla.org/~ehunt/bug_1006816_unlisted_apps/unlisted_apps_ui.pdf

Updated

3 years ago
Priority: -- → P5
Depends on: 1018950
Blocks: 1018950
No longer depends on: 1018950
Priority: P5 → P3
https://www.dropbox.com/s/1ej97fqa1c2p0p3/Screenshot%202014-09-17%2016.40.28.png?dl=0

At a quick glance, it seems odd to me that the "Currently Active" text is deemphasised, wheres the "Make Active" text is both prominent a button.
And what happens if the first version is the current version? Where does the "Make Active" button go?

Is the button something that is supposed to magically appear on :hover?

What about using a radio button? Like this:

https://www.dropbox.com/s/7ohfnp5zxnq13vj/versions-list-bug-1055148.png?dl=0
(Reporter)

Comment 5

3 years ago
(In reply to Christopher Van Wiemeersch [:cvan] from comment #4)
> And what happens if the first version is the current version? Where does the
> "Make Active" button go?
> 
> Is the button something that is supposed to magically appear on :hover?
> 
> What about using a radio button? Like this:
> 
> https://www.dropbox.com/s/7ohfnp5zxnq13vj/versions-list-bug-1055148.png?dl=0

The problem with the radio button was that you can only go forward, not backward since we only allow the "Make Active" button on approved versions later than the currently active version. In that sense a radio doesn't make sense b/c there'd only be one radio and we'd also need a form submit button somewhere.
"Make Active" is the primary action one can take. Therefore it is larger.

"Make Active" only becomes available when a dev uploads a new version of an app. Then the new version shows the "Make Active" button, while the previous version is "Currently Active." 

We don't want radio buttons b/c not all versions can be made active, ie, rejected/blocked/etc can't be made active and you can't "go backwards" to make a prior version active.

Updated

2 years ago
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
Whiteboard: [marketplace-transition]
You need to log in before you can comment on or make changes to this bug.