On Tue, 20 Feb 2007, Anne van Kesteren wrote:
I think the parsing algorithm should take the prompt= attribute of
isindex in account. It replaces the string of characters placed before
the input element with its contents. (In that case there will be no
characters after the isindex element.)
On Tue, 20 Feb 2007 10:56:05 +0100, Anne van Kesteren wrote:
On Tue, 20 Feb 2007 10:52:12 +0100, Alexey Feldgendler
Are there any real-world uses of isindex remaining? Is this
element worth the trouble?
Yes. And it's not much trouble...
I never understood what isindex is done for. Is it
2007/2/21, David Latapie [EMAIL PROTECTED]:
I never understood what isindex is done for. Is it some kind of
precursor of Google Sitemaps?
http://en.wikipedia.org/wiki/HTML_element
isindex…/isindex (deprecated)
The :isindex element requires server side support for indexing
documents.
On Wed, 21 Feb 2007 14:19:43 +0100, Martijn wrote:
2007/2/21, David Latapie [EMAIL PROTECTED]:
I never understood what isindex is done for. Is it some kind of
precursor of Google Sitemaps?
http://en.wikipedia.org/wiki/HTML_element
isindex…/isindex (deprecated)
The :isindex element
I think the parsing algorithm should take the prompt= attribute of
isindex in account. It replaces the string of characters placed before
the input element with its contents. (In that case there will be no
characters after the isindex element.)
--
Anne van Kesteren
On Tue, 20 Feb 2007 09:53:31 +0100, Anne van Kesteren [EMAIL PROTECTED]
wrote:
I think the parsing algorithm should take the prompt= attribute of
isindex in account. It replaces the string of characters placed before
the input element with its contents. (In that case there will be no
