This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.
<isindex> was an obsolete HTML element that put a text field in a page for querying the document.
<isindex> provided a single line text input for entering a query string. When sent, the server would return a list of pages matching the query. Its support depended on both the browser and the server to react to the query.
<isindex> is removed HTML Standard. It was deprecated in HTML 4.01. The same behavior can be achieved with an HTML form. All major browsers have now removed
Like all other HTML elements, this element accepted the global attributes.
- This attribute added its value as a prompt for text field.
- This attribute determined the server URL to which the query was sent.
<head> <isindex prompt="Search Document..." action="/search"> </head>
In past browsers, this would generate, at parse time, a DOM tree equivalent to the following HTML:
<form action="/search"> <hr> <label> Search Document... <input name="isindex"> </label> <hr> </form>
On November 1992, indexes as links rather than documents started by Dan Connolly who is pushing the idea that indexes are more links than documents. In this thread, different type of solutions are proposed. The question of forms for making queries is mentioned in reference to Dynatext browser: "The browser displays toggle buttons, text fields etc. The user fills in the fields, clicks OK, and the query results come up in the table of contents window."
A thread about isindex in November 1992, Kevin Hoadley questioned the need for an isindex element and proposed to drop it. He proposed to have instead an input element (idea supported by Steve Putz). Tim Berners-Lee explains the purpose of isindex resulting in aggregated search results. Kevin replies that he doesn't like the boolean nature of isindex and would prefer a system where everything is searchable and proposes to extend the current WWW Framework with a specific httpd configuration and defined that some URIs mapping create search queries.
BCD tables only load in the browser