Bugzilla – Full Text Bug Listing
| Summary: | [client] progress service OK status could be improved | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion (Archived) | Reporter: | Susan McCourt <susan> | ||||
| Component: | Client | Assignee: | Susan McCourt <susan> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | john.arthorne, malgorzata.tomczyk, simon_kaegi | ||||
| Version: | 0.2 | Keywords: | polish | ||||
| Target Milestone: | 0.5 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 371261 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
We have many implementation-oriented status messages, and I don't see that OK warrants at special case at this time. I'd rather add the "taskName" notion in a later release, do some animation, etc. and then consider the OK special case. Things have changed with progress (we have animation now, etc.) but the basic point is still relevant: When something is "OK" do we need more context, like saying what was OK? This is especially relevant if we decide to keep a history. A bunch of "OK"s are kind of useless. moving out of 0.5M2 to 0.5 milestone until we have more specific buckets for future I haven't seen "OK" in a long time. |
Created attachment 194214 [details] screenshot after a successful merge in git, the progress message says "OK" It would be cool if the progress service could special case the "OK" message and say something a little better. I think a good solution might be to add a parameter to showWhile showWhile: function(deferred, message, taskName) And we could post info like taskName + " is complete." In fact, this would be even more useful for the case where a showWhile doesn't provide a final message or status. Having the progress message disappear may not be enough for the user, it would be nicer to have a completion message. The taskName could also then be used for cases where more than one thing is going on, for showing progress from multiple tasks, etc.