Michael Winter <M.Winter@blueyonder.co.uk.invalid> writes:
[color=blue]
> Lasse Reichstein Nielsen wrote on 21 Nov 2003:[/color]
[color=blue]
> Withdrawn. It just seemed a sensible association: name attributes of
> NAME type.[/color]
Most of the people in this grouped had thought the same thing. We were
quite surpriced :)
[color=blue][color=green]
>> We had that discussion a while ago, and the conclusion was that
>> there are not restrictions on the names of controls.[/color]
>
> No leading and trailing spaces is probably one.[/color]
True. It is only a recommendation, but since browsers are free to
choose whether to strip the whitespace, writing it is asking for
trouble.
[color=blue]
> It would appear that the NAME type is only used for language codes,
> and the name and http-equiv attributes in META elements.[/color]
Yes, that was my reading too.
For all other tags with name attributes, i.e., a, applet, form, frame,
iframe, img, and not control names, the specifiaction has this note:
---
Note. This attribute has been included for backwards
compatibility. Applications should use the id attribute to identify
elements.
---
Also, if you have both "id" and "name" attributes in the same
non-form-control tag, they must have identical values.
<URL:http://www.w3.org/TR/html4/struct/links.html#anchors-with-id>
Still, if you omit the "id" attribute, you can still give your images
"name" attributes that are not valid NAMEs.
/L
--
Lasse Reichstein Nielsen -
lrn@hotpop.com
DHTML Death Colors: <URL:http://www.infimum.dk/HTML/rasterTriangleDOM.html>
'Faith without judgement merely degrades the spirit divine.'
