Bug 11016 - Search has no user feed back during search
: Search has no user feed back during search
Status: CLOSED FIXED
Product: SqueezePlay
Classification: Unclassified
Component: Browser
: unspecified
: PC Windows XP
: P5 minor (vote)
: 7.5.x
Assigned To: Ben Klaas
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-02-09 14:24 UTC by James Richardson
Modified: 2011-05-12 14:26 UTC (History)
4 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Richardson 2009-02-09 14:24:51 UTC
Using the SBC to do a search (any service) there is no user feed back during the search procedure.

IP3K has a spiny, Jive does not

Music Service > Rhapsody > Search > enter term > Button
Notice there is no indication to a customer that the search is working.  On really slow services, this looks as though the button press did nothing, or the SBC has locked up.
Comment 1 Andy Grundman 2009-02-10 10:40:39 UTC
This is an SBC issue, also test against SC.
Comment 2 James Richardson 2009-02-10 11:06:33 UTC
Yes, this also happens on production when the search service takes a long time to return results.
Comment 3 James Richardson 2009-02-23 14:23:23 UTC
Easy to reproduce by selecting Music Service > Napster > Search > ABBA >

Notice on the SBC there is no spiny '>' although the search does work
Comment 4 Blackketter Dean 2009-07-22 09:01:50 UTC
Moving to the product SqueezePlay because this bug appears to apply to any player based on that application code.  Feel free to move it back if it's specific to the original product.
Comment 5 Ben Klaas 2009-07-22 14:21:37 UTC
actually I don't believe this requires a string, but a spinny and at most a "Searching..." string, which can be poached from the string used for the local music search waiting screen.
Comment 6 Ben Klaas 2009-08-26 07:52:56 UTC
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
Comment 7 Chris Owens 2009-10-21 09:47:34 UTC
Moving these bugs to P4 to make room for moving P1.5 bugs to P2
Comment 8 Pat Ransil 2009-10-23 05:09:32 UTC
Administrative move of 7.5 bugs. All P2, P3, P4 being downgraded one level. Will then split P1s.
Comment 9 Chris Owens 2010-03-08 11:32:59 UTC
Moving lower-priority bugs to next target
Comment 10 Ben Klaas 2011-01-13 17:34:34 UTC
this is fixed
Comment 11 Paul Chandler 2011-05-12 14:26:44 UTC
Search gives a brief spinning icon and prompts for 'where to search'  7.6. r32407