- From: Epperson, Beth <bepperson@websense.com>
- Date: Wed, 14 Jun 2006 14:09:35 -0700
- To: "Steven Pemberton" <steven.pemberton@cwi.nl>, "HTML WG" <w3c-html-wg@w3.org>
- Cc: "public-rdf-in-xhtml-tf.w3.org" <public-rdf-in-xhtml-tf@w3.org>
Hello,
I would suspect that proximity would rule. The title closest to the
content would take precedence. That, I suspect, would be a logical
analytical approach - going from inner most to outer most relative
element.
//beth
-----Original Message-----
From: w3c-html-wg-request@w3.org [mailto:w3c-html-wg-request@w3.org] On
Behalf Of Steven Pemberton
Sent: Wednesday, June 14, 2006 12:34 PM
To: HTML WG
Cc: public-rdf-in-xhtml-tf.w3.org
Subject: [BULK] - Meaning and priority of standard XHTML properties
We have said in XHTML2 that things like
<a title="gezellig" href="gezellig.html">gezellig</a>
is equivalent to
<a href="gezellig.html">
<meta property="title" content="gezellig"/>
gezellig
</a>
The question has arisen, what happens with:
<a title="Peioria" href="gezellig.html">
<meta property="title" content="gezellig"/>
gezellig
</a>
From an RDF point of view, there's no problem (the element has two
titles)
but what should a browser do with respect to, for instance, tool tips?
Steven
Received on Wednesday, 14 June 2006 21:09:43 UTC