Something To Enjoy....

[drhayden1]

http://www.members.shaw.ca/grandmafaiths2/boogie.htm

I know you will enjoy this page as much as I did.
turn volume up....and scroll down

[roro]

I went to this site using Firefox and couldn't hear the music, so I opened it up in IE tab.  Then I could hear the music.  Why I wonder?
Ro Ro

[FreewheelinFrank]

I went to this site using Firefox and couldn't hear the music, so I opened it up in IE tab.  Then I could hear the music.  Why I wonder?
Ro Ro

Crappily written web page:

http://validator.w3.org/check?uri=http%3A%2F%2Fwww.members.shaw.ca%2Fgrandmafaiths2%2Fboogie.htm&charset=%28detect+automatically%29&doctype=Inline&group=0

[drhayden1]

Crappily written web page

might of been FWF my friend-but the presentation was nice
i just started this thread something to enjoy if anyone found something we would or must  of us would enjoy put it in this thread like the interesting thread but different of sorts.

I went to this site using Firefox and couldn't hear the music

and RoRo didn't have any trouble with my firefox-that's what i was using when i saw the site and listened to the music.

[FreewheelinFrank]

Crappily written web page

might of been FWF my friend-but the presentation was nice
i just started this thread something to enjoy if anyone found something we would or must  of us would enjoy put it in this thread like the interesting thread but different of sorts.

I was referring to the coding. The presentation of the page is fine, but the coding has major errors.

The page is silent for me in Firefox, but boogies in Opera.

The fox is a fussy beast and turns his nose up at a dog's breakfast of code. IE happily tucks in, and Opera chugs down the mess, but it is really an unappetising meal.

[drhayden1]

I was referring to the coding. The presentation of the page is fine, but the coding has major errors.

ok-at least it worked
doing the boogie

[FreewheelinFrank]

The main body of the page is doubly obfuscated in two layers of JavaScript.

Unravelling this code into HTML reveals (along with a whole load more validation errors) the real problem:

<BGSOUND balance=0 src="boogie/boogie.mid"
volume=0><bgsound balance="0" src="boogie/boogie.mid" volume="0" loop=infinite>

BGSOUND is supported by IE but not Netscape.

Now, assuming you've thought through the consequences of your actions, let's talk about how to put a background sound on your page. Unfortunately the browser industry and standards committees have not settled on a standard way of accomplishing this. Netscape allows background sounds through use of the <EMBED ...> tag. MSIE, Mosaic, and several other browsers use the <BGSOUND ...> tag. You might at this point ask why you can't just use both and let each interpret its preferred tag. The problem is that MSIE sometimes interprets the <EMBED ...> tag in addition to <BGSOUND ...> (depending on the particular installation) resulting in conflict and ugly error messages. This is the sort of thing that happens when there isn't a standard to follow.

With this lack-of-standards problem, the best to hope for is a situation that plays the sound in most situations, and in the other situations doesn't play the sound and doesn't give error messages. This can be accomplished using scripting, as in this example.

<SCRIPT TYPE="text/javascript">
<!--
var filename="hazy_shade_of_winter.mid";
if (navigator.appName == "Microsoft Internet Explorer")
    document.writeln ('<BGSOUND SRC="' + filename + '">');
else if (navigator.appName == "Netscape")
    document.writeln ('<EMBED SRC="' + filename + '" AUTOSTART=TRUE WIDTH=144 HEIGHT=60><P>');
// -->
</SCRIPT>
<NOSCRIPT>
<BGSOUND SRC="hazy_shade_of_winter.mid">
</NOSCRIPT>

The code says this:

   1. If the current browser is MSIE then write out a <BGSOUND ...> tag.
   2. Else, if the current browser is Netscape then write out an <EMBED ...> tag.
   3. Then in the <NOSCRIPT> section, browsers that don't understand scripting will see the <BGSOUND ...> tag. Several browsers that don't understand scripting do understand <BGSOUND ...>. Also, browsers that have scripting turned off but do understand <BGSOUND ...> will also see this tag. Of course, browsers that have scripting turned off but don't understand <BGSOUND ...> will have no sound at all. Again, that's the price being paid for lack of standards. At least they won't fail with an ugly error message.

That's kind of complicated, isn't it? Well, that's the problem with this sort of kludge: you have to try to anticipate all the situations and avoid the nasty ones. Hopefully in the foreseeable future the browser makers will correct this problem. 

http://www.htmlcodetutorial.com/sounds/sounds_famsupp_18.html

Generally the coding does not make any effort to be cross-browser compatible or standards-compliant.

[drhayden1]

thanks for the in-depth analysis of the link and etc. FWF 
what have i started now posting this thread
where's the super malware fighter polonus on this one

[Kilia]

Leave it to the avast! team to dissect a website.  Thanks for the chuckle, guys.   

[DavidR]

Leave it to the avast! team to dissect a website.  Thanks for the chuckle, guys.   

No avast (Alwil) team members in this topic, just avast users like yourself looking out for other avast users.

The main body of the page is doubly obfuscated in two layers of JavaScript.
Unravelling this code into HTML reveals (along with a whole load more validation errors) the real problem:

<BGSOUND balance=0 src="boogie/boogie.mid"
volume=0><bgsound balance="0" src="boogie/boogie.mid" volume="0" loop=infinite>

BGSOUND is supported by IE but not Netscape.

Interesting that, when the favicon is a Netscape one really clever.

[gdiloren]

My only issue over the new update of FF v. 2.0.0.6 is that when you mouse over an emoticon, you no longer have the explanation text like IE 7.0 or the previous version. I use the latest "NoScript" extension, but I don't think that's the problem.

[Kilia]

Leave it to the avast! team to dissect a website.  Thanks for the chuckle, guys.   

No avast (Alwil) team members in this topic, just avast users like yourself looking out for other avast users.

Ahhh..I sit corrected then.

[drhayden1]

No avast (Alwil) team members in this topic, just avast users like yourself looking out for other avast users

how true davidr my friend

Ahhh..I sit corrected then.

no problem
let's get back to the meaning of this thread i started....anybody have anything us Avast! Users have to enjoy

[polonus]

Hello FwF and drhayden1,

Cross browser compatible code is abound on the Internet, and it should be. But it also needs be secure. Sometimes browser coders freeze certain applications because of persistent bugs.
But code like this should be coded with the major browsers in mind.

polonus

[drhayden1]

let's get back to the meaning of this thread i started

i know after i pm'ed you-you would reply to this off-topic on my thread