On Thu, Oct 14, 2010 at 11:59 AM, Tony Gentilcore to...@chromium.orgwrote:
// 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;
Hi,
Are you covering such a use case: user enters a website, goes to the
search box (of the browser, not the page), and it is able to search
based on suggestions given by the page?
I think this would be great and would be a good way to normalize the way
people search inside a given page/app.
--
Thanks Anne,
On Wed, Oct 13, 2010 at 10:00 AM, Anne van Kesteren ann...@opera.com wrote:
On Tue, 12 Oct 2010 06:41:59 +0200, ATSUSHI TAKAYAMA
taka.atsu...@googlemail.com wrote:
It's a minor error in the spec in the Server-Sent Events spec.
Hi,
may I wonder why on earth any new API, like
link.sizes uses PutForwards?
IMHO, PutForwards should be limited to the
awkward DOM0 APIs like window.location.
br,
-Olli
On Wed, Oct 13, 2010 at 3:59 PM, Tony Gentilcore to...@chromium.org wrote:
Hi All,
We're adding instant search integration [1] to Google Chrome, allowing
the search provider to communicate suggestions to the user agent.
If there is interest, we'd like to make sure that we do this in such a
On Thu, Oct 14, 2010 at 8:43 AM, Jonas Sicking jo...@sicking.cc wrote:
On Wed, Oct 13, 2010 at 3:59 PM, Tony Gentilcore to...@chromium.org wrote:
Hi All,
We're adding instant search integration [1] to Google Chrome, allowing
the search provider to communicate suggestions to the user agent.
On Thu, Oct 14, 2010 at 12:12 AM, Peter Kasting pkast...@google.com wrote:
The API is completely orthogonal to OpenSearch AFAICT. OSDDs tell a UA
about a search engine and how to search with it. The proposed DOM additions
provide a search engine with information about what the user is doing
On Thu, Oct 14, 2010 at 11:09 AM, Aryeh Gregor
simetrical+...@gmail.comsimetrical%2b...@gmail.com
wrote:
If this is meant to be vendor-neutral, there needs to be some way for
arbitrary search engines to advertise support for this feature to
supporting browsers.
That depends on whether the
If this is meant to be vendor-neutral, there needs to be some way for
arbitrary search engines to advertise support for this feature to
supporting browsers. In the experimental Chrome implementation, does
it just not work if the search engine isn't Google? If Bing wanted to
make use of this
On Fri, Oct 15, 2010 at 12:53 PM, Tony Gentilcore to...@chromium.orgwrote:
The simplest way to address this is probably to advertise support via
an agreed upon meta tag. e.g.
meta name=NavigatorSearchBoxSupport content=true
The UA populates the API only if the page advertises support via the
10 matches
Mail list logo
