Beauregard T. Shagnasty said:
Quoth the raven named Revd. Norle Enturbulata:
End of problem (perhaps) for those visitors who have JavaScript,
present and enabled.
Why don't you investigate using server-side technologies for
repetitive content, such as headers, menus, footers and make your
pages much simpler to maintain at the same time? It's quite easy. You
will probably have to give up FrontPage, though.
<meta name="ProgId" content="FrontPage.Editor.Document">
Actually I don't just rely upon FP, having a deep-seated suspicion of
code-generators on their own. I've grown used to the interface and it
doesn't mess with my hand-coding - previous versions were awful about that.
BTW, why do you open Halloween.html in a new window? The embedded
media on that page also crashes my browser (Firefox and Mozilla 1.6).
That page is actually the first done back in 1996. I've been wanting to get
to it for a while, and the only answer at this point is a complete revamp of
the system. It was originally intended to be a more interactive process as
well.
If you look at the code you can see the main reason for the browser error
you're getting. It WAS RealAudio, but the Real player doesn't support their
own original format any more. I hated Real after they pimped those of us
who produce music on the Internet, when they silently stopped supporting
their own format, I stopped producing work in Real 100%. They left
thousands of web people out in the cold, and it was either figure out where
the original media file encoded to RM was, or reverse-engineer/record the
work so it could be reencoded, or junk everything and start anew with
another format not Real. Combine this with their desceptive links to the
"free player" that linked to the Pay-for player, making it an act of
detective work just finding the "free player"; the unannounced and unwelcome
additions of AOL crapola to user machines; the constant changing of the
links to the "free player" in order to defeat webmasters' efforts to help
people find it... and it all shows a mercenary attitude towards their
userbase that I consider unacceptable in any kind of environment. End of
rant.
Ahenh! Thus my thoughts on the frames level, and my questions here. One of
the items on the agenda, by the way, is the code to allow WM to be
implemented as startup sounds for all browsers. Simple, yes, but in
combination with a load of other items, just one more thing to fix.
Thanks for responding.