I agree with Peter that I don't want have to use someone else's background. If
the person were really clever, they could write an obscene message that only
certain color blind people would see. :/)
There is the *potential* for something meaningful in a background, but I can't
think of any examples. Why not give the option at the client for a usable
background (solving Netscape gray). This should work like display/not display
inline images.
______________________________ Forward Header __________________________________
Eric and Peter wrote:
Subject: Re: textured backgrounds
Author: pflynn@curia.ucc.ie at PMDF
Date: 1/18/95 8:07 AM
Eric writes:
I was more concerned with what people thought of the idea as opposed to
arguments over the syntax of its implementation, but...
The only problem I have with the concept (as opposed to the
implementation) is that I may not _want_ someone else's damnfool
cutesiepie wallpaper in my browser window...which is why I think it
has to be an external option you can turn on or off, rather than
hardwired into the <body>...which is why I liked the idea of using
<link>: that's what it's there for, isn't it?
Heck even with all the different color attributes you can still do one
monster tag. Say lavender text floating above a space backdrop with yellow
anchors (gray when visited, white when activated).
<PAPER BACKGROUND="#000000" HREF="space.gif" FOREGROUND="#CC00FF"
LINK="#FFFF00" VLINK="#CCCCCC" ALINK="FFFFFF">
At this stage, wouldn't it be easier to maintain your files if you
said
<link rel="presentation" href="startrek.style">
where startrek.style said
Paper*Background: http://x.y.z/mypix/ds9.gif
Paper*Foreground: cyan
Paper*ActiveLink: magenta
etc etc.
///Peter
