PDA

View Full Version : Re: [slim] Fishbone skin issue w/Mozilla?



Victor Brilon
2003-11-24, 22:21
The status frame has this:
<link rev="x-refresh"
href="status_header.html?player=00%3a04%3a20%3a02%3a03%3 a7f&amp;start=&amp;refresh=1">

Is that ok? Sorry my HTML knowledge is near zilch.

In the server settings, the refresh value is set to 30 secs. I am
guessing that what's happening is that it's not actually refreshing. I
just checked the same page w/an IE browser and it works fine, so it's
obviously a Mozilla problem.

Any ideas what it could be?

Victor

Kevin Deane-Freeman wrote:

> The scroll timer shoudl give you a rough measure of the song
duration, and the
> page shoudl refresh at the rate you have set in the server settings.
Is the
> page reloading? Can you look at the source for the status frame and
see that the META refresh
> is valid?
>
> -kdf
>
> Quoting Victor Brilon <victor (AT) victorland (DOT) com>:
>
>
>> I have a weird problem that I am hoping is not user error
>>
>> I am running my slimp3 w/the latest CVS server software w/the
Fishbone skin. I am using Mozilla - and I just updated to the latest
1.6a nightly to test this problem and it still exists.
>>
>> The problem is that even though the player plays fine, the skin is
convinced it's on the same song over and over. The scroll timer at the
top of the page runs down to the end and starts all over again -- with
the skin displaying the same song and never progressing. If I hit
'undock' the new window show the current song playing btw.
>>
>> If I hit the 'forward' or 'back' buttons on the skin, the display
shows the proper song and then gets stuck on it as well.
>>
>> User config error or a problem w/Mozilla?
>>
>> Thanks,
>> Victor
>>

Kevin Deane-Freeman
2003-11-24, 22:30
Sorry, with all your RPM skills, I just assumed HTML was a breeze ;)

This is the line you are looking for from the top of status_header.html is:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta http-equiv="refresh" content="240;
url=status_header.html?player=00%3a04%3a20%3a00%3a 00%3a01&amp;start=&amp;refresh=1">
<link rel="stylesheet" href="slimserver.css">
<script language="JavaScript">

The important part, in this case is content="240;
I have my server set to refresh at 240. If you look at the source from the skin
directory, it will be content="{refresh};

Near the end of a song, if the remaining song time is less than yoru setting,
then it will reduce to match. Minimum should be 2. I'm runing with latest
milestone of Mozilla Firebird, and I can't reproduce the problem. I'll try
downloading Mozilla 1.6 and see if there is any difference.

Do other skins have this same problem? The current song display in the status
should be more or less the same mechanism, unless something in the javascript is
currupting Mozilla's ability to render Fishbone skin.

-kdf



Quoting Victor Brilon <victor (AT) victorland (DOT) com>:

> The status frame has this:
> <link rev="x-refresh"
>
href="status_header.html?player=00%3a04%3a20%3a02%3a03%3 a7f&amp;start=&amp;refresh=1">
>
> Is that ok? Sorry my HTML knowledge is near zilch.
>
> In the server settings, the refresh value is set to 30 secs. I am
> guessing that what's happening is that it's not actually refreshing. I
> just checked the same page w/an IE browser and it works fine, so it's
> obviously a Mozilla problem.
>
> Any ideas what it could be?
>
> Victor
>
> Kevin Deane-Freeman wrote:
>
> > The scroll timer shoudl give you a rough measure of the song
> duration, and the
> > page shoudl refresh at the rate you have set in the server settings.
> Is the
> > page reloading? Can you look at the source for the status frame and
> see that the META refresh
> > is valid?
> >
> > -kdf
> >
> > Quoting Victor Brilon <victor (AT) victorland (DOT) com>:
> >
> >
> >> I have a weird problem that I am hoping is not user error
> >>
> >> I am running my slimp3 w/the latest CVS server software w/the
> Fishbone skin. I am using Mozilla - and I just updated to the latest
> 1.6a nightly to test this problem and it still exists.
> >>
> >> The problem is that even though the player plays fine, the skin is
> convinced it's on the same song over and over. The scroll timer at the
> top of the page runs down to the end and starts all over again -- with
> the skin displaying the same song and never progressing. If I hit
> 'undock' the new window show the current song playing btw.
> >>
> >> If I hit the 'forward' or 'back' buttons on the skin, the display
> shows the proper song and then gets stuck on it as well.
> >>
> >> User config error or a problem w/Mozilla?
> >>
> >> Thanks,
> >> Victor
> >>

Victor Brilon
2003-11-24, 22:57
Kevin Deane-Freeman wrote:
> Sorry, with all your RPM skills, I just assumed HTML was a breeze ;)

Hehe. I was always the guy writing code on the backend server stuff -- I
left the HTML to the guys who knew what they were doing and who had some
sense of aesthetic design. :)

> This is the line you are looking for from the top of status_header.html is:
> <html>
> <head>
> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
> <meta http-equiv="refresh" content="240;
> url=status_header.html?player=00%3a04%3a20%3a00%3a 00%3a01&amp;start=&amp;refresh=1">
> <link rel="stylesheet" href="slimserver.css">
> <script language="JavaScript">
>

Ah! This is quite interesting now.

In Mozilla, the page gives me this source:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1">
<link rev="x-refresh"
href="status_header.html?player=00%3a04%3a20%3a02%3a03%3 a7f&amp;start=&amp;refresh=1">
<link rel="stylesheet" href="slimserver.css">
<script language="JavaScript">

In IE, the page gives me this source:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1">
<meta http-equiv="refresh" content="30;
url=status_header.html?player=0
0%3a04%3a20%3a02%3a03%3a7f&amp;start=&amp;refresh=1">
<link rel="stylesheet" href="slimserver.css">
<script language="JavaScript">


The "content" tag is missing from the Mozilla rendering. So I got
curious why Mozilla would render it different. Winds up my proxy server
(privoxy) which I use for banner ad filtering, also strips out any
Javascript that creates "actions" on the browser -- i.e., a meta-refresh
and that's why it was rendering differently.

After I got rid of the proxy, I still had had problems though with it
working consistently. Some google-ing and a search of Bugzilla came up
with this: http://bugzilla.mozilla.org/show_bug.cgi?id=209020

I think this is what's causing the problem, so the answer is to wait for
the Mozilla bug fix I guess :/

Thanks for the help,
Victor