Bug 5739 - Additional vertical spacing after the currently playing track
: Additional vertical spacing after the currently playing track
Status: RESOLVED DUPLICATE of bug 5737
Product: Logitech Media Server
Classification: Unclassified
Component: Web Interface
: 7.0
: PC Windows XP
: P2 minor (vote)
: ---
Assigned To: Squeezebox QA Team email alias
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-10-09 06:00 UTC by Philip Meyer
Modified: 2007-10-09 13:40 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments
See the whitespace between track 4 (playing), and the next selected track (35.49 KB, image/pjpeg)
2007-10-09 06:02 UTC, Philip Meyer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Philip Meyer 2007-10-09 06:00:18 UTC
In the new default skin, there is additional spacing only after the currently playing track.

This is only noticeable if the artwork is turned off.
Comment 1 Philip Meyer 2007-10-09 06:02:59 UTC
Created attachment 2238 [details]
See the whitespace between track 4 (playing), and the next selected track
Comment 2 KDF 2007-10-09 08:15:16 UTC
I'm not seeing this on FF.  Is this with IE6? 7?
Comment 3 KDF 2007-10-09 11:04:13 UTC
ok, seems to be IE6 (can't check IE7) and it involves the currentSong div, namely the "height: 34px;" in ie.css.  However, the problem then is that the selectorMarker divs all overlap, leaving currentSong showing extra highlighting.
Comment 4 Philip Meyer 2007-10-09 12:30:25 UTC
Yes, I discovered the problem on IE6.  IE7 and FF are okay.
Comment 5 KDF 2007-10-09 12:51:30 UTC
ah ok. There has been some discussion on whether continued support for IE6 is reasonable given it's plethora of unresolved issues with CSS, Ajax and basically anything that isn't specifically tailored to IE6.  Now that IE7 has apparently been opened up as a high priority update (no longer requiring WGA validation) I expect IE6 will soon be gone aside from the corporate world unwilling to risk an update.  This will probably fall into the "learn to live with it" bucket as it does take up a lot of resource time to make IE6 work exactly like everything else.
Comment 6 KDF 2007-10-09 13:26:56 UTC
actually, since this is IE6 only, I'm going to merge with 5737 as it is a good bucket for evaluating the effort required to get IE6 fully supported.

*** This bug has been marked as a duplicate of 5737 ***
Comment 7 Philip Meyer 2007-10-09 13:28:48 UTC
I am stuck, for now, with IE6 from my work PC.  I guess many users accessing their server from work will be in a similar boat.

However, your comment is not an unreasonable stance to take.  Most home users I guess would upgrade to IE7, or use some other browser.  As long as SC in IE6 is functional, superficial problems with styles are probably acceptable.

Other skins can be used instead if it becomes a bigger issue.
Comment 8 KDF 2007-10-09 13:40:23 UTC
yes, it also may be that most issues are trivial.  Major problems might still be worth fixing so that IE6 still works in principle. vertical space and a few errant lines is something that can be lived with. Blank panes or failing JS responses, maybe not so much :)