Closed Bug 542098 Opened 16 years ago Closed 15 years ago

Test Pilot UI: Use persistent notifications only for test-ready-to-submit

Categories

(Mozilla Labs Graveyard :: Test Pilot, defect, P1)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jono, Assigned: jono)

References

Details

(Whiteboard: extension-core, ui)

Use pop-up notifications only in one case, which is case of a study being ready to submit, but leave it up until user clicks on it - don't have it go away if they click anywhere else. Put an X in the corner that they can click to close it if they don't want to see it, but a click anywhere else in the notification takes you to the study results page. Other state changes, like a new study becoming available, can be shown on the All Tests page, and the user can be notified there's something there by lighting up the test pilot icon (which is grey otherwise). It's OK if people don't notice new studies and only find out about the study when it's done.
This is because user studies show that the current notifications go away so easily that most people don't even notice them. The only one we REALLY need people to see is the ready-to-submit status, so I think it's a fair trade-off to have a less fragile notification in exchange for using it less often.
Priority: -- → P1
Target Milestone: 0.1 → 1.0
Whiteboard: extension-core, ui
In the UI redesign, we'll have 'fragile' notifications for new tests and new results (i.e. click anywhere outside to close) and 'solid' notifications for when a test is ready to submit; these notifications need a close button, a link, and a submit button within them.
Blocks: 551289
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Verified with 1.0a2 on Win7 and Mac 10.6 with Firefox 3.6.3 This also answers questions about a couple notification test cases I was having trouble with. I'll update those based on info here.
Status: RESOLVED → VERIFIED
Product: Mozilla Labs → Mozilla Labs Graveyard
You need to log in before you can comment on or make changes to this bug.