Bug 7147 - Default Skin: The message about upgrade should not have white background.
: Default Skin: The message about upgrade should not have white background.
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Web Interface
: 7.0
: PC Windows (legacy)
: P5 normal (vote)
: ---
Assigned To: Michael Herger
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-02-14 14:16 UTC by Wallace Lai
Modified: 2009-09-08 09:12 UTC (History)
0 users

See Also:
Category: ---


Attachments
ScreenShot (308.80 KB, image/bmp)
2008-02-14 14:17 UTC, Wallace Lai
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wallace Lai 2008-02-14 14:16:09 UTC
System Info:  Gateway, P4, 2.00 GHz, Win 2K SP4 ENU, IE 6
SC Version:  Nightly from 2008-02-14

Steps to Reproduce:
1.  Down grade the Ray to MP FW.
2.  During down grade, look at the default skin of SC Web UI.
3.  There should be a message about holding the brightness button.
4.  Notice the background for that message is white.
5.  Grey is better looking than white in this case.
Comment 1 Wallace Lai 2008-02-14 14:17:03 UTC
Created attachment 2888 [details]
ScreenShot
Comment 2 Wallace Lai 2008-02-14 14:21:24 UTC
This bug is a bit related to 7128.  However, this is a cosmetic issue.  Not a functional one.
Comment 3 Michael Herger 2008-02-14 14:39:18 UTC
Oh,sure it should. But it should fill the full panel with that bg colour ;-)
Comment 4 Blackketter Dean 2008-02-14 19:45:12 UTC
Heh.  It should be the standard background color for that area.
Comment 5 Chris Owens 2008-02-15 09:15:27 UTC
Dean notes it's 'Jammed up in the corner' as well
Comment 6 Michael Herger 2008-02-15 10:02:54 UTC
change 17585 - please test. Thanks!
Comment 7 Chris Owens 2008-03-07 09:04:39 UTC
This bug is being closed since it was resolved for a version which is now released!  Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html

If you are still seeing this bug, please re-open it and we will consider it for a future release.