On Apr 30, 10:16 pm, Mohamed Mansour <[email protected]> wrote:
> Chromium doesn't support "window.external.AddSearchProvider" , it supports
> the OpenSearch specification.
Except that IS the OpenSearch specification:
"Aside from using autodiscovery links, both IE7 and Firefox 2 can
be pointed to your OpenSearch Description document using a javascript
call: window.external.AddSearchProvider("http://mysite.org/odd.xml";);
"
See http://www.opensearch.org/Documentation/Developer_best_practices_guide
It is also the same function being called on http://mycroft.mozdev.org
where Chrome is working and popping up a window to add an engine:
function addOpenSearch(name,ext,cat,pid,meth)
{
if ((typeof window.external == "object") && ((typeof
window.external.AddSearchProvider == "unknown") || (typeof
window.external.AddSearchProvider == "function"))) {
// See bugs 430058/430067/430070 for Camino
if (((typeof window.external.AddSearchProvider == "unknown") ||
(window.navigator.vendor == 'Camino'))&& meth == "p") {
alert("This plugin uses POST which is not currently supported by
your browser's implementation of OpenSearch.");
} else {
window.external.AddSearchProvider(
"http://mycroft.mozdev.org/installos.php/"; + pid + "/" + name
+ ".xml");
}
} else {
alert("You will need a browser which supports OpenSearch to
install this plugin.");
}
}
(I tested locally on Chrome and it gets to the line with
window.external.AddSearchProvider.)
So what javascript works with Chrome???
Or what is wrong with my xml file on Chrome???
Can someone explicitly spell it out? This isn't Apple; it's not a big
secret is it? ;-)
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: [email protected]
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
