W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2010

[whatwg] SearchBox API

From: Robert O'Callahan <robert@ocallahan.org>
Date: Thu, 14 Oct 2010 23:28:46 +1300
Message-ID: <AANLkTi=eAJx1ODZCyCLkgHmmiL3DKJnFrwn60V6v4OSZ@mail.gmail.com>
On Thu, Oct 14, 2010 at 11:59 AM, Tony Gentilcore <tonyg at chromium.org>wrote:

> // Dimensions of the portion of the search box (e.g. a dropdown)
>  // that overlaps the window.
>  readonly attribute unsigned long x;
>  readonly attribute unsigned long y;
>  readonly attribute unsigned long width;
>  readonly attribute unsigned long height;

How is this information expected to be used?

Is there expected to be some kind of policy that controls which pages are
allowed to access the searchBox API? I assume that if I'm currently visiting
evil.com and I start typing in a search, evil.com should not be able to see
that. How should the searchBox API behave in that case?

Is the intent that the browser load a normal search page for some partial
query and then expose the rest of the search query through this searchBox
API? If so, it seems we'll need a way to detect ahead of time that a search
service expects/supports such behavior.

"Now the Bereans were of more noble character than the Thessalonians, for
they received the message with great eagerness and examined the Scriptures
every day to see if what Paul said was true." [Acts 17:11]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20101014/b35606b3/attachment.htm>
Received on Thursday, 14 October 2010 03:28:46 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:27 UTC