It depends. What kinds of features were you thinking off? The obvious one is to add search engine choices to the bar, but you can already do this. Maybe a way to choose the engine on the fly would be good. Outside of that, I can't really think of any other uses for Omnibar extension apis. What have you got in mind?
On Jan 8, 3:45 am, Erek Speed <[email protected]> wrote: > I was brainstorming about how different features fit into the chrome > model and one thing I thought about was the custom search bars you get > in many firefox extensions. It seems to me that the best way for > features like that to be integrated into chrome is through the > omnibar. It has a pretty ambitious name after all. > > It seems like direct control over the omnibar would be tricky due to > the browser native features that interact with it already. > > An alternative would be to allow extensions to add a "search feature" > to the omnibar which in most cases would run a script in the > background page (or content script if that makes more sense.) I don't > know specifically, but I feel this could easily fit into the current > API users already have for customizing the omnibar. > > Let me know what you think (or if there are ways to do this already > that I missed.)
-- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
