Creating OpenSearch plugins for Firefox

  • Revision slug: Talk:Creating_OpenSearch_plugins_for_Firefox
  • Revision title: Creating OpenSearch plugins for Firefox
  • Revision id: 80718
  • Created:
  • Creator: plotkin
  • Is current revision? No
  • Comment 90 words added, 27 words removed

Revision Content

Correctness of example

Is the example template given correct? Specifically, there's no mention of the method attribute to the Url element, nor the Param element, in the OpenSearch 1.1 current draft. There is a draft specification for parameters, but it uses a Parameter element, not Param. Pimlottc 15:15, 23 April 2008 (PDT)

I moved this section up to the top because would like to bring attention to this question again. The following link does make mention of the Param tag in a sense but they call it "Parameter".  OpenSearch parameter extension 1.0  This of course leads to some parsing confusing for us since we are trying to make an OpenSearch parser (we started with making MozSearch parser). Was it that they called the tag 'Param' in an earlier draft of the OpenSearch spec? There is mention on opensearch.org of moving the <Param> tag to the 'Opensearch parameter extension' but the old copies of the spec do not seem to be available to look back at for comparison.

Plotkin 14:21, 21 July 2009 (EDT)

Newbie questions

I'm a complete newbie here. I've typed the XML code into my text program. Now presumably I have to save it as a file. Any particular name I'm supposed to give it? How do I let FF know to add it to my browser? What about the items I don't know? Should I leave them blank, or delete them entirely?

The page Adding search engines from web pages linked from the third paragraph describes a JavaScript method (this requires access to a web server: either your own website hosted somewhere or install a server on your computer).

Question: is there another way? Can I simply put the xml file somewhere and re-start firefox? Can I access the xml descriptions of the already installed plugins, so I can adapt them to (for example) run over a proxy?  drevicko 01 January 2009

Answer:  Yes, there is another way.  Put the xml file into the searchplugins directory (on Windows systems, this is usually C:\Program Files\Mozilla Firefox\searchplugins).  Then, you have to re-start Firefox so it can see the file.  After the restart, your new search plugin will appear at the bottom of the drop-down list.

Unfortunately, you have to restart Firefox each time you make changes to the XML file.

Once you have tested the XML file you are encouraged to use the JavaScript method to make it easy for others to discover and install.  LandOfDelight 30 May 2009

Link to Mycroft Project in the reference section

The mycroft project would be a good reference to include. drevicko 01 January 2009

MozSearch format

Add link to Creating MozSearch plugin page in Image subsection, and insert note "IE not support data: URIs" there.

Also add in SearchForm subsection: "Trick: May be useful to specify in <SearchForm> URI of extended search page - to allow quick access it by sending empty string as request".

Mozilla-specific elements

Elements <moz:UpdateUrl>, <moz:IconUpdateUrl>, <moz:UpdateInterval> is not described, and even is not documented at developer.mozilla.org at all.

Privacy?

At creating a OpenSearch plugin for Firefox 2.0 , I have to specify the a URL of the type="application/x-suggestions+json" where the search suggestions are stored.

This causes that the search suggestions are stored on the server. If I do not like this, because of privacy:

1) Can I prevent a plugin to store on a server as User of Firefox ?

2) What ULR do I have to use, that these things are stored locally ?

The "application/x-suggestions+json" URL in your plugin file has nothing to do with where suggestions are stored - it's the URL used to obtain the suggestions. These suggestions are displayed once and then discarded. These kinds of "suggestions" are different from the standard "history" results, which are stored in the user's profile, on disk. gavin 05:50, 31 October 2006 (PST)

What to do next with that OpenSearch XML file?

Cut it down to 3 lines 1.what to do with it from the beginners point of view 2.searchengine 3.how to access searchengine

Can I add the search engine by clicking on a link?

I created a few search engine XML files that work fine when I add them directly from the tool bar. That is, I go to the page where I have defined the auto discovery links to the XML files. Immediately the search box on Firefox gets the blue blinking light. I am then able to "add" the new search engine right there. However, I want to have links on this page where I describe the search engine's functionality. Clicking on the link should add the search engine. What should I do to create those links? Now it just opens up the xml file in the browser.

See Adding search engines from web pages, which is linked to in the third paragraph of this article. gavin 10:54, 9 January 2007 (PST)
Thanks Gavin. That worked.--Godzilla2 15:03, 9 January 2007 (PST)

What's wrong here?

I created an OpenSearch XML file, and it works 100% in IE7 (-shudder-) but whenever I try it in FF it says "This Search Engine isn't supported by FF and can't be installed" - Which is wierd because it follows strict OpenSearch 1.1 format. Loading the XML file directly into FF doesn't highlight any errors, there are no special chars to escape, and I don't even use any of the FF-specific tags so don't need to define the MOZ Namespace. (In fact, when I do, it fails in IE as well!)

Code Snippet:


<?xml version="1.0" encoding="UTF-8"?> <OpenSearchDescription xmlns="http://a9.com/-/spec/opensearch/1.1/" > <Url type="text/html" template="http://www.KIWIreviews.co.nz/search/{searchTerms}" /> <ShortName>KIWIreviews</ShortName> <LongName>KIWIreviews Browserbar Search</LongName> <Description>Search through our product and review database for your selected searchterms.</Description> <Tags>New Zealand Product Reviews</Tags> <Developer>KIWIreviews</Developer> <Contact>-valid email address-</Contact> <Attribution>Copyright ©2007 KIWIreviews.co.nz. All rights reserved.</Attribution> <SyndicationRight>limited</SyndicationRight> <AdultContent>false</AdultContent> </OpenSearchDescription>


Is there anything technically wrong with this?

On top of that, I added the autodiscover link to the index page header, yet no autodiscovery. -insert frustrated glare-

Lock?

This page is vandalized very often and doesn't get much useful edits. I suggest we lock it. --Nickolay 15:42, 10 April 2007 (PDT)


I agree. This page gets messed with constantly. I'm going to lock it. If anyone has a legitimate edit to make, let us know and we'll open it up for that. --Sheppy 16:06, 10 April 2007 (PDT)

savely needs to be changed to safely. I'm a new user here and this is my first edit. Nastajus 20:04, 24 July 2007 (PDT)
Fixed the typo, thanks! --Nickolay 10:56, 25 July 2007 (PDT)

Ready2Search moved to new URL;Ready2Search The new guide is Custom Search through Ready2Search. I can't fix by the lock. Delete this message after you finish fixing.

How Search Engines Become "Recommended"?

Is there a need for this page (or some other page) to include some information on how, why and when a search plug-in gets elevated from the full database of plug-ins (http://mycroft.mozdev.org/) to Firefox's primary search plug-in page (https://addons.mozilla.org/en-US/fir.../browse/type:4)? I'm looking for this information myself and was unable to find anything on the topic. --Fold 14:56, 08 June 2007 (GMT)

I suppose, you just need to submit it to AMO as an XPI. Post to dev-apps-firefox, perhaps? --Nickolay 10:56, 25 July 2007 (PDT)
That was wrong:
<gavin|> you need to email the AMO team and ask to have it added, afaik
<gavin|> they dont' accept them as XPIs
<gavin|> I think they have plans to create a more elaborate system for submitting search engines

--Nickolay 14:16, 25 July 2007 (PDT)

Bug 409076 needs to be fixed before users can upload new search engines. -- clouserw 2008-08-06

Automatic Updates?

In the old Firefox-only Plugins, one could specify an URL and Update Interval to be sure, users get updates for their plugins. Is there anything similar available in OpenSearch? --Andreas Kahl 13:21, 8 September 2007 (PDT)

I suppose, you could package the search plugin in an XPI that gets automatic updates. But your question should really be asked in the newsgroups. --Nickolay 13:22, 9 September 2007 (PDT)

Wikipedia Search Coding

I would like to make a search plugin for my company's Wiki-based knowledge base. I imagine that if I could find the coding for the integrated Wikipedia search, most of the parameters would be the same, and I could just change the addresses. The XML file isn't in the \Mozilla Firefox\searchplugins directory though. Can anyone direct me to a wiki search template so that I could create the search plugin? Ninjatek 18:11, 6 November 2007 (PST)

Can I add the search engine from a local file?

I have created a wellformed XML, but how do I add it from a local file? I made a local .html with a <link... in the <head> and specified the path to the local xml under href= but nothing happened. Is it mandatory to upload the file somewhere?! Surely there must be some easy way to locally just import one or more search engines from xml files?

Please, add reference to Portuguese Translation

{{ mediawiki.interwiki('pt', 'Criando_plugins_OpenSearch_para_o_Firefox', 'pt:Criando plugins OpenSearch para o Firefox') }}

Fixing searchterms typo

Just noticed in the documentation that {searchterms} is listed as a smart tag instead of {searchTerms}. Unfortunately, the incorrect case will cause the feature to not work - doh! Could someone please fix this (I would, but the page is locked).

I don't see this, where is it? --Sheppy 10:19, 26 March 2008 (PDT)

xmlns:moz

The URL in xmlns:moz="http://www.mozilla.org/2006/browser/search/" is broken. It is only an identifier, nobody needs to locate the resource, I know the theory, but in practice http is supposed to work.

The documentation doesn't mention that bad things can happen if an opensearch description doesn't offer a Mozilla <SearchForm>. The default is then simply the domain, e.g., Google for a Google CSE (custom search engine). Some users including me are annoyed when google.com redirects them to say google.de.

It would be far better to use the query URL as default, either an empty query or better using the example query in the opensearch description. Of course it is possible to get this effect by adding <moz:SearchForm> for a specified xmlns:moz namespace, broken URI or not, but why should opensearch descriptions be filled up with proprietary Mozilla annotations? --Frank 10:53, 11 April 2008 (PDT)

searchTitle

Firefox treats a leading space in the <ShortName> as significant, noted as -Name.xml instead of Name.xml in the saved search plugin derived from an opensearch description. An autodiscovery title="Name" apparently doesn't match -Name, if that's no bug it's an oddity. . --Frank 12:08, 11 April 2008 (PDT)

 

Please change Firefox 3.1 > Firefox 3.5

{{ user("Jürgen Jeka") }} 2009-05-02

Revision Source

<h3 name="Correctness_of_example">Correctness of example</h3>
<p>Is the example template given correct? Specifically, there's no mention of the method attribute to the Url element, nor the Param element, in the <a class="external" href="http://www.opensearch.org/Specifications/OpenSearch/1.1">OpenSearch 1.1 current draft</a>. There is a <a class="external" href="http://www.opensearch.org/Specifications/OpenSearch/Extensions/Parameter/1.0">draft specification for parameters</a>, but it uses a Parameter element, not Param. <a href="/User:Pimlottc" title="User:Pimlottc">Pimlottc</a> 15:15, 23 April 2008 (PDT)</p>
<div class="note">
<p>I moved this section up to the top because would like to bring attention to this question again. The following link does make mention of the Param tag in a sense but they call it "Parameter".  <a class="external" href="http://www.opensearch.org/Specifications/OpenSearch/Extensions/Parameter#Notice" title="http://www.opensearch.org/Specifications/OpenSearch/Extensions/Parameter#Notice">OpenSearch parameter extension 1.0</a>  This of course leads to some parsing confusing for us since we are trying to make an OpenSearch parser (we started with making MozSearch parser). Was it that they called the tag 'Param' in an earlier draft of the OpenSearch spec? There is mention on opensearch.org of moving the &lt;Param&gt; tag to the 'Opensearch parameter extension' but the old copies of the spec do not seem to be available to look back at for comparison.</p>
<p><a class="internal" href="/User:plotkin" title="User:plotkin">Plotkin</a> 14:21, 21 July 2009 (EDT)</p>
</div>
<h3 name="MozSearch.3F">Newbie questions</h3>
<p>I'm a complete newbie here. I've typed the XML code into my text program. Now presumably I have to save it as a file. Any particular name I'm supposed to give it? How do I let FF know to add it to my browser? What about the items I don't know? Should I leave them blank, or delete them entirely?</p>
<p style="margin-left: 40px;">The page <a href="/en/Adding_search_engines_from_web_pages" title="en/Adding_search_engines_from_web_pages">Adding search engines from web pages</a> linked from the third paragraph describes a JavaScript method (this requires access to a web server: either your own website hosted somewhere or install a server on your computer).</p>
<p style="margin-left: 40px;">Question: is there another way? Can I simply put the xml file somewhere and re-start firefox? Can I access the xml descriptions of the already installed plugins, so I can adapt them to (for example) run over a proxy?  <a href="/User:drevicko" rel="custom">drevicko</a> 01 January 2009</p>
<p style="margin-left: 40px;"><span style="color: rgb(255, 0, 0);">Answer:  Yes, there is another way.  Put the xml file into the <em>searchplugins </em>directory (on Windows systems, this is usually <em>C:\Program Files\Mozilla Firefox\searchplugins</em>).  Then, you have to re-start Firefox so it can see the file.  After the restart, your new search plugin will appear at the bottom of the drop-down list.</span></p>
<p style="margin-left: 40px;"><span style="color: rgb(255, 0, 0);">Unfortunately, you have to restart Firefox each time you make changes to the XML file.</span></p>
<p style="margin-left: 40px;"><span style="color: rgb(255, 0, 0);">Once you have tested the XML file you are encouraged to use the JavaScript method to make it easy for others to discover and install.  <a href="/User:LandOfDelight" rel="custom">LandOfDelight</a> 30 May 2009</span></p>
<h3 name="MozSearch.3F"><span id="1225427128365S" style="display: none;"> </span>Link to Mycroft Project in the reference section</h3>
<p>The mycroft project would be a good reference to include. <a href="/User:drevicko" rel="custom">drevicko</a> 01 January 2009</p>
<h3 name="MozSearch.3F">MozSearch format</h3>
<p>Add link to <a href="/en/Creating_MozSearch_plugins" title="en/Creating_MozSearch_plugins">Creating MozSearch plugin</a> page in <strong>Image</strong> subsection, and insert note "IE not support data: URIs" there.</p>
<p>Also add in <strong>SearchForm</strong> subsection: "<strong>Trick:</strong> May be useful to specify in &lt;SearchForm&gt; URI of extended search page - to allow quick access it by sending empty string as request".</p>
<h3 name="Mozilla-specific.3F">Mozilla-specific elements</h3>
<p>Elements <strong>&lt;moz:UpdateUrl&gt;, &lt;moz:IconUpdateUrl&gt;, &lt;moz:UpdateInterval&gt;</strong> is not described, and even is not documented at developer.mozilla.org at all.</p>
<h3 name="Privacy.3F">Privacy?</h3>
<p>At creating a OpenSearch plugin for Firefox 2.0 , I have to specify the a URL of the type="application/x-suggestions+json" where the search suggestions are stored.</p>
<p>This causes that the search suggestions are stored on the server. If I do not like this, because of privacy:</p>
<p>1) Can I prevent a plugin to store on a server as User of Firefox ?</p>
<p>2) What ULR do I have to use, that these things are stored locally ?</p>
<dl> <dd>The "application/x-suggestions+json" URL in your plugin file has nothing to do with where suggestions are stored - it's the URL used to obtain the suggestions. These suggestions are displayed once and then discarded. These kinds of "suggestions" are different from the standard "history" results, which are stored in the user's profile, on disk. <a href="/User:GavinSharp" title="User:GavinSharp">gavin</a> 05:50, 31 October 2006 (PST) </dd>
</dl>
<h3 name="What_to_do_next_with_that_OpenSearch_XML_file.3F">What to do next with that OpenSearch XML file?</h3>
<p>Cut it down to 3 lines 1.what to do with it from the beginners point of view 2.searchengine 3.how to access searchengine</p>
<h3 name="Can_I_add_the_search_engine_by_clicking_on_a_link.3F">Can I add the search engine by clicking on a link?</h3>
<p>I created a few search engine XML files that work fine when I add them directly from the tool bar. That is, I go to the page where I have defined the auto discovery links to the XML files. Immediately the search box on Firefox gets the blue blinking light. I am then able to "add" the new search engine right there. However, I want to have links on this page where I describe the search engine's functionality. Clicking on the link should add the search engine. What should I do to create those links? Now it just opens up the xml file in the browser.</p>
<dl> <dd> See <a href="/en/Adding_search_engines_from_web_pages" title="en/Adding_search_engines_from_web_pages">Adding search engines from web pages</a>, which is linked to in the third paragraph of this article. <a href="/User:GavinSharp" title="User:GavinSharp">gavin</a> 10:54, 9 January 2007 (PST) </dd>
</dl>
<dl> <dd> <dl> <dd>Thanks Gavin. That worked.--<a href="/User:Godzilla2" title="User:Godzilla2">Godzilla2</a> 15:03, 9 January 2007 (PST) </dd> </dl> </dd>
</dl>
<h3 name="What.27s_wrong_here.3F">What's wrong here?</h3>
<p>I created an OpenSearch XML file, and it works 100% in IE7 (-shudder-) but whenever I try it in FF it says "This Search Engine isn't supported by FF and can't be installed" - Which is wierd because it follows strict OpenSearch 1.1 format. Loading the XML file directly into FF doesn't highlight any errors, there are no special chars to escape, and I don't even use any of the FF-specific tags so don't need to define the MOZ Namespace. (In fact, when I do, it fails in IE as well!)</p>
<p>Code Snippet:</p>
<hr>
<p>&lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;OpenSearchDescription xmlns="<a class=" external" href="http://a9.com/-/spec/opensearch/1.1/" rel="freelink">http://a9.com/-/spec/opensearch/1.1/</a>" &gt; &lt;Url type="text/html" template="<a class=" external" href="http://www.KIWIreviews.co.nz/search/" rel="freelink">http://www.KIWIreviews.co.nz/search/</a>{searchTerms}" /&gt; &lt;ShortName&gt;KIWIreviews&lt;/ShortName&gt; &lt;LongName&gt;KIWIreviews Browserbar Search&lt;/LongName&gt; &lt;Description&gt;Search through our product and review database for your selected searchterms.&lt;/Description&gt; &lt;Tags&gt;New Zealand Product Reviews&lt;/Tags&gt; &lt;Developer&gt;KIWIreviews&lt;/Developer&gt; &lt;Contact&gt;-valid email address-&lt;/Contact&gt; &lt;Attribution&gt;Copyright ©2007 KIWIreviews.co.nz. All rights reserved.&lt;/Attribution&gt; &lt;SyndicationRight&gt;limited&lt;/SyndicationRight&gt; &lt;AdultContent&gt;false&lt;/AdultContent&gt; &lt;/OpenSearchDescription&gt;</p>
<hr>
<p>Is there anything technically wrong with this?</p>
<p>On top of that, I added the autodiscover link to the index page header, yet no autodiscovery. -insert frustrated glare-</p>
<h3 name="Lock.3F">Lock?</h3>
<p>This page is vandalized very often and doesn't get much useful edits. I suggest we lock it. --<a href="/User:Nickolay" title="User:Nickolay">Nickolay</a> 15:42, 10 April 2007 (PDT)</p>
<p><br>
I agree. This page gets messed with constantly. I'm going to lock it. If anyone has a legitimate edit to make, let us know and we'll open it up for that. --<a href="/User:Sheppy" title="User:Sheppy">Sheppy</a> 16:06, 10 April 2007 (PDT)</p>
<dl> <dd> savely needs to be changed to safely. I'm a new user here and this is my first edit. <a href="/User:Nastajus" title="User:Nastajus">Nastajus</a> 20:04, 24 July 2007 (PDT) </dd>
</dl>
<dl> <dd> <dl> <dd> Fixed the typo, thanks! --<a href="/User:Nickolay" title="User:Nickolay">Nickolay</a> 10:56, 25 July 2007 (PDT) </dd> </dl> </dd>
</dl>
<p>Ready2Search moved to new URL;<a class="external" href="http://ready.to/search/en/">Ready2Search</a> The new guide is <a class="external" href="http://ready.to/search/make/en_make_plugin.htm">Custom Search through Ready2Search</a>. I can't fix by the lock. Delete this message after you finish fixing.</p>
<h3 name="How_Search_Engines_Become_.22Recommended.22.3F">How Search Engines Become "Recommended"?</h3>
<p>Is there a need for this page (or some other page) to include some information on how, why and when a search plug-in gets elevated from the full database of plug-ins (<a class=" external" href="http://mycroft.mozdev.org/" rel="freelink">http://mycroft.mozdev.org/</a>) to Firefox's primary search plug-in page (<a class=" link-https" href="https://addons.mozilla.org/en-US/firefox/browse/type:4" rel="freelink">https://addons.mozilla.org/en-US/fir.../browse/type:4</a>)? I'm looking for this information myself and was unable to find anything on the topic. --<a href="/User:Fold" title="User:Fold">Fold</a> 14:56, 08 June 2007 (GMT)</p>
<dl> <dd> I suppose, you just need to submit it to AMO as an XPI. Post to dev-apps-firefox, perhaps? --<a href="/User:Nickolay" title="User:Nickolay">Nickolay</a> 10:56, 25 July 2007 (PDT) </dd> <dd> That was wrong: </dd>
</dl>
<pre class="eval">&lt;gavin|&gt; you need to email the AMO team and ask to have it added, afaik
&lt;gavin|&gt; they dont' accept them as XPIs
&lt;gavin|&gt; I think they have plans to create a more elaborate system for submitting search engines
</pre>
<p>--<a href="/User:Nickolay" title="User:Nickolay">Nickolay</a> 14:16, 25 July 2007 (PDT)</p>
<p><a class="link-https" href="https://bugzilla.mozilla.org/show_bug.cgi?id=409076">Bug 409076</a> needs to be fixed before users can upload new search engines. -- <a href="/User:Clouserw" title="User:Clouserw">clouserw</a> 2008-08-06</p>
<h3 name="Automatic_Updates.3F">Automatic Updates?</h3>
<p>In the old Firefox-only Plugins, one could specify an URL and Update Interval to be sure, users get updates for their plugins. Is there anything similar available in OpenSearch? --<a href="/User:Andreas_Kahl" title="User:Andreas_Kahl">Andreas Kahl</a> 13:21, 8 September 2007 (PDT)</p>
<dl> <dd> I suppose, you could package the search plugin in an XPI that gets automatic updates. But your question should really be asked in the newsgroups. --<a href="/User:Nickolay" title="User:Nickolay">Nickolay</a> 13:22, 9 September 2007 (PDT) </dd>
</dl>
<h3 name="Wikipedia_Search_Coding">Wikipedia Search Coding</h3>
<p>I would like to make a search plugin for my company's Wiki-based knowledge base. I imagine that if I could find the coding for the integrated Wikipedia search, most of the parameters would be the same, and I could just change the addresses. The XML file isn't in the \Mozilla Firefox\searchplugins directory though. Can anyone direct me to a wiki search template so that I could create the search plugin? <a href="/User:Ninjatek" title="User:Ninjatek">Ninjatek</a> 18:11, 6 November 2007 (PST)</p>
<h3 name="Can_I_add_the_search_engine_from_a_local_file.3F">Can I add the search engine from a local file?</h3>
<p>I have created a wellformed XML, but how do I add it from a local file? I made a local .html with a &lt;link... in the &lt;head&gt; and specified the path to the local xml under href= but nothing happened. Is it mandatory to upload the file somewhere?! Surely there must be some easy way to locally just import one or more search engines from xml files?</p>
<h3 name="Please.2C_add_reference_to_Portuguese_Translation">Please, add reference to Portuguese Translation</h3>
<p>{{ mediawiki.interwiki('pt', 'Criando_plugins_OpenSearch_para_o_Firefox', 'pt:Criando plugins OpenSearch para o Firefox') }}</p>
<h3 name="Fixing_searchterms_typo">Fixing searchterms typo</h3>
<p>Just noticed in the documentation that {searchterms} is listed as a smart tag instead of {searchTerms}. Unfortunately, the incorrect case will cause the feature to not work - doh! Could someone please fix this (I would, but the page is locked).</p>
<dl> <dd>I don't see this, where is it? --<a href="/User:Sheppy" title="User:Sheppy">Sheppy</a> 10:19, 26 March 2008 (PDT) </dd>
</dl>
<h3 name="xmlns:moz">xmlns:moz</h3>
<p>The URL in <code><span class="nowiki">xmlns:moz="http://www.mozilla.org/2006/browser/search/"</span></code> is broken. It is only an identifier, nobody needs to locate the resource, I know the theory, but in practice <a class="external" href="http://www.mozilla.org/2006/browser/search/">http</a> is supposed to work.</p>
<p>The documentation doesn't mention that bad things can happen if an opensearch description doesn't offer a Mozilla <code>&lt;SearchForm&gt;</code>. The default is then simply the domain, e.g., Google for a Google CSE (custom search engine). Some users including me are annoyed when google.com redirects them to say google.de.</p>
<p>It would be far better to use the query URL as default, either an empty query or better using the example query in the opensearch description. Of course it is possible to get this effect by adding <code>&lt;moz:SearchForm&gt;</code> for a specified xmlns:moz namespace, broken URI or not, but why should opensearch descriptions be filled up with proprietary Mozilla annotations? --<a href="/User:Xyzzy" title="User:Xyzzy">Frank</a> 10:53, 11 April 2008 (PDT)</p>
<h3 name="searchTitle">searchTitle</h3>
<p>Firefox treats a leading space in the <code>&lt;ShortName&gt;</code> as significant, noted as <strong>-</strong><code>Name.xml</code> instead of <code>Name.xml</code> in the saved search plugin derived from an opensearch description. An autodiscovery <code>title="Name"</code> apparently doesn't match <strong>-</strong><code>Name</code>, if that's no bug it's an oddity. . --<a href="/User:Xyzzy" title="User:Xyzzy">Frank</a> 12:08, 11 April 2008 (PDT)</p>
<p> </p>
<h3>Please change Firefox 3.1 &gt; Firefox 3.5</h3>
<p>{{ user("Jürgen Jeka") }} 2009-05-02</p>
Revert to this revision