On Thu, Oct 14, 2010 at 11:59 AM, Tony Gentilcore <to...@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. Rob -- "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]
