Closed Bug 599984 Opened 14 years ago Closed 14 years ago

"Send tweet" dialog should close automatically after successfully sending a tweet

Categories

(support.mozilla.org :: Army of Awesome, task)

task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: djst, Assigned: abuchanan)

References

Details

After a tweet is sent, 

STR:
1. Go to https://184.106.236.207/en-US/army-of-awesome
2. Click a tweet
3. (If not logged in to Twitter, log in)
4. Send a tweet

Actual results: Dialog remains visible. If closing manually and selecting another tweet, the dialog pops up with the previous state (still saying "Your message was sent!")

Expected results: Dialog should ideally disappear after sending the tweet and the "Your message was sent!" message should appear at the top of the tweet list instead (scrolling back up to the top of that list).
The design intended for the success message to appear on the dialog and then the dialog faded out / disappeared after 2-3 seconds. There wouldn't be a message on top of the tweet list in this case.

Alex, can we do that?
Assignee: nobody → abuchanan
Sure, we can do either workflow.  The flow David suggests sounds like a better experience, but means design changes (e.g. where does the success message show?)

William's is simplest to implement.
Let's definitely go for simplest to implement at this point. Thanks!
Bonus points for disabling the Submit button when clicking it, but I can live without that too if we get this out in Q3...
Agreed. Let's go with the method in comment 1. Play around with the delay before the dialog closes so the user will be able to notice the message but not be waiting for the dialog to close. I'm thinking somewhere between 2-4 seconds.
bug[custcare 1c72c0e] bug 599984, customer care, auto close send tweet dialog after submission
 1 files changed, 4 insertions(+), 0 deletions(-)

2 seconds felt right
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2.2.5
Flags: in-testsuite?
You need to log in before you can comment on or make changes to this bug.