Community
Participate
Working Groups
we've just added support for links in the progress messages. The M7 support was done quickly (during the status call)..some improvements - need to document what HTML can really go in there - need a special CSS class assigned by the progress support so that the links always appear (vs. just on hover) - probably need some space between the status icon and html (we insert some for the text)
I would add there a spinning wheel (or any other kind of spinning widget) so the user knows there is something going on in the background. Dots are not that intuitive. Moreover, if we're getting statuses from more then one task they should be displayed in a drop down list or something similar. This sounds like a separate bug, though.
(In reply to comment #1) > I would add there a spinning wheel (or any other kind of spinning widget) so > the user knows there is something going on in the background. Dots are not that > intuitive. this bug is for minor cleanup for the 0.2 release, so it's just going to be tweaking what's there. I had thought about elapsed time, just so there was at least some movement. > Moreover, if we're getting statuses from more then one task they > should be displayed in a drop down list or something similar. This sounds like > a separate bug, though. yep, that's bug 344012
*** Bug 349131 has been marked as a duplicate of this bug. ***
Szymon, now that the header layout has been changed and the progress messages appear on a light color vs. dark, there is no longer a need to use the CSS class "pageActions" on your progress message that has links. That was the hack I gave you back when we first added this feature. I removed the class in the live CSS and indeed, you get the nice, blue link that you would expect if no class is specified. So the progress links look just like other links in the header (good). So I think this bug is over to you to remove "pageActions" from your progress HTML.
*** Bug 349232 has been marked as a duplicate of this bug. ***
looks OK
Fixed with cc9f454e2fa76e7327668eb317323c3ce7503b2b. The link is nice and blue, but I think it should be more visible. I raised Bug 349296 for it.