Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 334471
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 12, 20262026-05-12T10:03:26+00:00 2026-05-12T10:03:26+00:00

I think the title explains it all but I am going deeper into my

  • 0

I think the title explains it all but I am going deeper into my question anyway:

How can I make use of the Chrome’s Omnibox [TAB] feature for my website?

As many users requested me to implement that feature on the site, I did research on the OpenSearchDescription and was very successful in implementation with the FireFox and IE7/IE8 Searchbar.

Yet the implementation didn’t quite work for the Chrome Omnibox [TAB] feature..

Can you help me with that?

My OSD.xml code:

<OpenSearchDescription xmlns="http://a9.com/-/spec/opensearch/1.1/"
                       xmlns:moz="http://www.mozilla.org/2006/browser/search/">
<ShortName>MySite</ShortName>
<Description>My Site</Description>
<InputEncoding>UTF-8</InputEncoding>
<Image width="16" height="16" type="image/x-icon">http://MySite.com/favicon.ico</Image>
<Url type="application/x-suggestions+json" method="GET"
     template="http://ff.search.yahoo.com/gossip?output=fxjson&amp;command={searchTerms}" />
<Url type="text/html" method="POST" template="http://MySite.com/query.php">
  <Param name="sString" value="{searchTerms}"/>
</Url>
<Url type="application/x-suggestions+json" template="suggestionURL"/>
<moz:SearchForm>http://www.MySite.com</moz:SearchForm>
</OpenSearchDescription>

And this is the link to the osd file on my page:

<link rel="search" type="application/opensearchdescription+xml" title="MySite" href="/opensearch.xml" />
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-12T10:03:26+00:00Added an answer on May 12, 2026 at 10:03 am

    Getting OSD (OpenSearchDescription) work under Google Chrome or IE7 / IE8 isn’t as difficult as mentioned or that these browsers don’t support POST requests.

    With a little bit of tweaking, I found a workaround to the entire problem.

    My initial code:

    <Url type="text/html" method="POST" template="http://MySite.com/query.php">
      <Param name="sString" value="{searchTerms}"/>
    </Url>
    

    This code points directly to the query page and passes the value for the sString attribute on my POST request.

    That works perfectly on FireFox but doesn’t quite work well on IE7/IE8 or Google Chrome (I didn’t test with Opera or Safari yet..).


    Altering the code to the following piece:

    <Url type="text/html" template="http://MySite.com/query.php?sString={searchTerms}"></Url>
    
    • Removing method=”POST” from the element
    • Replacing /query.php with the actual page call: /query.php?sString={searchTerms}
    • Removing the now unnecessary “<Param name="sString" value="{searchTerms}"/>“

    Resolved my problem of incompatibility with those browsers.

    All calls are directly headed to the query page and even it initially was a POST request, it now work on both IE7/IE8 and Google Chrome.

    Thanks again adrianbanks for providing me with your xml file which led to the solution!

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

The original question is below, but I changed the title because I think it
I think the title explains it all. I want to be notified when a
I think the title pretty much says it all... I'm looking to implement an
OK so that title sucks a little but I could not think of anything
Sorry for the bad title, but I couldn't think of a better one. I'm
The title explains all... I have this snippet of code in my application: String
i think my whole questions is inside title bar =] but i'll explain little
I think title should be good enough.
I'm sorry I could not think of a better title. The problem is the
Sorry for the slightly rubbish title. I could not think how to describe this

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.