W3C home > Mailing lists > Public > public-html-comments@w3.org > September 2009

Allow list attribute to contain a URI pointing to an innerHTML-like fragment

From: Ric Hardacre <ricster@cyclomedia.co.uk>
Date: Wed, 2 Sep 2009 12:50:42 +0100 (BST)
Message-ID: <1180.81.145.159.82.1251892242.squirrel@omelette.dyndns.org>
To: public-html-comments@w3.org
Allow the ability to directly embed or set via javascript a URI that when
polled with a HTTP GET request will return the HTML fragment that would
make up the list of OPTION elements as if it were a physical DATALIST that
had its contents set via innerHTML.

<input type="text" id="fruit"
list="http://example.com/fragments/fruit-suggestions.htm" >


This could be a full GET including a search string, allowing search engine
style suggest-as-you-type (performance considerations aside for this
example!):

<input type="text" id="fruit" onkeyup="fruit_list(this)" >
<script>
function fruit_list( elem )
{
  elem.list = "http://example.com/fragments/fruit-suggestions.php?value="
+ elem.value;
}
</script>


Standard GET rules would apply, specifically allowing the returned
fragment to be cached locally.



The fragment returned by the server would look like the following:

"<option>Apples</option><option>Bananas</option><option>Oranges</option>"



This could feasibly be used to solve the long standing SELECT that fills
another SELECT dilemma

<select id="make" onchange="select_make(this)">...</select>
<select id="model">...</select>
<script>
  function select_make( elem )
  {
    document.getElementById("model").options =
"http://example.com/fragments/models.php?make=" + elem.value;
  }
</script>




Ric Hardacre
cyclomedia.co.uk
Received on Wednesday, 2 September 2009 14:11:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 1 June 2011 00:14:00 GMT