Async Chatter posting in pushdown using Ajax
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KARL3 |
Fix Released
|
Medium
|
JimPGlenn |
Bug Description
When I post via the pushdown, I don't want to reload the page, or even worse, get sent to the Chatter page. I want to stay on the page I was on.
- Clicking "Speak" should submit using xhr
- Perhaps the "Speak" button should change to a spinner to indicate something is happening (and disallow multiple things at once)
- On success, clear the textarea
- Either have the response return the replacement HTML/JSON for the "Posts" column, or issue another request to get that data, then replace that column
Other screens in Chatter will need something similar, but probably just a little different. We will work on those later.
Feel free to do the minimum (e.g. skip JSON+Mustache and just render server side.) But focus on reliability and letting the user know if there was a problem.
Changed in karl3: | |
milestone: | m101 → m102 |
Changed in karl3: | |
status: | New → In Progress |
Changed in karl3: | |
milestone: | m102 → m103 |
Changed in karl3: | |
milestone: | m103 → m104 |
tags: | added: r3.88 |
This looks good on the post side, but we need "New Message" on the Messages side, and it needs to create a message to a particular user.
Actually, let's triage that. Let's remove "New Message" as a link.
--Paul
On May 14, 2012, at 7:21 AM, JimPGlenn wrote:
> ** Changed in: karl3 /bugs.launchpad .net/bugs/ 990120 /bugs.launchpad .net/karl3/ +bug/990120/ +subscriptions
> Milestone: m102 => m103
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Async Chatter posting in pushdown using Ajax
>
> Status in KARL3:
> In Progress
>
> Bug description:
> When I post via the pushdown, I don't want to reload the page, or even
> worse, get sent to the Chatter page. I want to stay on the page I was
> on.
>
> - Clicking "Speak" should submit using xhr
>
> - Perhaps the "Speak" button should change to a spinner to indicate
> something is happening (and disallow multiple things at once)
>
> - On success, clear the textarea
>
> - Either have the response return the replacement HTML/JSON for the
> "Posts" column, or issue another request to get that data, then
> replace that column
>
> Other screens in Chatter will need something similar, but probably
> just a little different. We will work on those later.
>
> Feel free to do the minimum (e.g. skip JSON+Mustache and just render
> server side.) But focus on reliability and letting the user know if
> there was a problem.
>
> To manage notifications about this bug go to:
> https:/