Re: A nit and an addition for the current draft
Subject: Re: A nit and an addition for the current draft
From: Bert Bos <firstname.lastname@example.org>
Date: Mon, 18 Sep 1995 13:43:56 +0200 (METDST)
From email@example.com Mon Sep 18 07: 44:16 1995
In-Reply-To: <9509180629.AA17989@cadge.hyperion.com> from "Steven Grimm" at Sep 17, 95 11:29:05 pm
X-Mailer: ELM [version 2.4 PL24]
Steve Grimm writes:
|The nit: The text-background attribute has an ambiguous value type.
| body: text-background="bluegreen"
|There's no way for a parser to know if "bluegreen" is a relative URL or a
|color name. Perhaps there should be two attributes for background, with a
|defined order of precedence between them.
The intention is that color names are entered as keywords without
quotes. The reasoning behind this is, that, presumably, the number of
color names is small, so they can be entered in the parser's hash
|The addition: I think it's critical, if we want stylesheets to be adopted
|widely, that they provide a superset of the presentation control that the
|Netscape HTML extensions do. One glaring omission is an equivalent to the
|"border" attribute of the <img> tag. There's no way for a document author
|to specify that a hyperlink on an image be displayed with no decoration.
|Maybe "image-border", whose value is a size in any of the usual units.
For floating images, there is a `border' property (actually a set of
related properties), that can do this and much more. But because of
its generality (and therefore complexity), it was left out of level 1.
For inline images, there is currently only text-line (provisional
name). We forgot to specify that `border' applies to included material
as well. This should be fixed.
But: this is an example of a general problem with level 1: it has to
be both simple and compatible with level 2. Since we don't want to
compromise level 2 because of level 1, this double goal may be
impossible to attain, unless we accept that there are implicit
formatting rules for HTML that are not expressible in CSS level 1.
Maybe we can find a restricted syntax for the margin property that is
simple enough for level 1 and upwardly compatible, but I'm afraid that
won't be very easy.
|On a related note, there should also be a way to specify that two images
|should be displayed immediately adjacent to one another, with no space
|inserted. Some browsers insert extra space even if they don't render a
|link border (notably NCSA Mosaic for Windows.)
This is handled by the same `border' properties. The default is no
Btw. is a line break allowed before/after an image?
Bert Bos Alfa-informatica
<firstname.lastname@example.org> Rijksuniversiteit Groningen
<http://www.let.rug.nl/~bert/> Postbus 716, NL-9700 AS GRONINGEN