Welcome to WebHeadStart.org

Web Technologies

Sponsored By

WebHeadStart.org is currently in beta.
Please pardon our appearance as we work to provide you with the most comprehensive reference on today's web technologies.

Interested in advertising on WebHeadStart? Become an advertising partner today!

[WWW-HTML Mailing List Archive Home] [Messages By Thread] [Messages By Date]

name attribute deprecated in XHTML

From: Paolo Candelari <paolo.candelari@fastwebnet.it>
Date: Tue, 12 Jul 2005 16:39:18 +0200
Message-ID: <00d201c586ef$7c12cdc0$3794630a@ict.corp.rai.it>
To: +ACI-html list+ACI +ADw-www-html+AEA-w3.org+AD4

I'm reading (again) XHTML 1.0 Rec.
I wouldn't misunderstand what I'm reading but in paragraph 4.10 (
http://www.w3.org/TR/2002/REC-xhtml1-20020801/#h-4.10  ) I read:

 Note that in XHTML 1.0, the name attribute of these elements (a, applet,
form, frame, iframe, img, and map) is formally deprecated, and will be
removed in a subsequent version of XHTML.

Reading XHTML 1.0 DTD, both strict and transitional, we can find that name
is a permitted attribut of these elements and in HTML 4.01 ( The semantics
of the elements and their attributes are defined in the W3C Recommendation
for HTML 4. http://www.w3.org/TR/2002/REC-xhtml1-20020801/#abstract  ) we
find a suggestion tu use id instead of name for form and img elements.

I haven't problem to use id instead of name as fragment identifier (I think
that now UA are alomost compliant to understand thw usage of id attribut),
as I usally do, but how I have to read what quoted above like a "remainder"
(i.e. informative) or a normative point of XHTML 1.0 Rec?

Regards.

Paolo

**************************************************************************************
Questa e-mail, ed i suoi eventuali allegati, contengono informazioni confidenziali e riservate. 
Se avete ricevuto questa comunicazione per errore non utilizzatene il contenuto e non portatelo a conoscenza di alcuno.
Siete inoltre pregati di eliminarla dalla vostra casella e avvisare il mittente. 
E' da rilevare inoltre che l'attuale infrastruttura tecnologica non pu+API- garantire l'autenticit+AOA- del mittente, n+AOg- tantomeno l'integrit+AOA- dei contenuti.

Opinioni, conclusioni ed altre informazioni contenute nel messaggio possono rappresentare punti di vista personali a meno di diversa esplicita indicazione autorizzata.

**************************************************************************************
Received on Wednesday, 13 July 2005 08:26:01 GMT
Valid XHTML 1.0! Valid CSS! Site Map | Privacy Policy | Terms of Use | WebHeadStart.org © 2005 All Rights Reserved.