[whatwg] Safari-compatible <input type="search">

[João Eiras]

> How can the Web designer know how many recent search terms the user would like to keep handy at the search box?

He/she can't know, and providing that info would be a privacy issue.
input with type search would simply tell the UA to keep entries typed
in memory for later reuse, which is a bonus for usability, and spared
the page uathro of javascript kungfudeathgrips and bloated js
libraries to provide trivial functionality.



On Tue, Sep 30, 2008 at 3:18 PM, Kristof Zelechovski
<giecrilj at stegny.2a.pl> wrote:
> How can the Web designer know how many recent search terms the user would
> like to keep handy at the search box?
> What if autosave strings clash, or get deliberately stepped upon?
> I think it is a user preference + browser QoI and Web sites should not try
> to outsmart it.  Marking a box as a search box is already there (ISINDEX,
> deprecated).
> Chris
>
> -----Original Message-----
> From: whatwg-bounces at lists.whatwg.org
> [mailto:whatwg-bounces at lists.whatwg.org] On Behalf Of Andy Lyttle
> Sent: Tuesday, September 30, 2008 1:40 PM
> To: whatwg at lists.whatwg.org
> Subject: [whatwg] Safari-compatible <input type="search">
>
> I would like Apple's <input type="search"> adopted as an official
> standard, maintaining Safari compatibility.  Attributes are:
>
> onsearch="foo();" - JavaScript function called when the user
> initiates a search
>
> incremental - if present, onsearch fires on every keypress, and on
> clicking the cancel button; otherwise onsearch fires when pressing Enter
>
> results - if present, shows a little magnifying glass icon, which
> helps to visually identify the field as a search box
>
> results=10 - the magnifying glass functions as a drop-down menu
> containing a history of the last (whatever number) search terms
>
> autosave="foo" - define a unique name to identify the search history
> (so the same history may be shared across multiple search boxes, even
> across different domains)
>
>
>
>