YUKI "Piro" Hiroshi Reporter
	Description • 8 years ago

My addon "Second Search" https://addons.mozilla.org/firefox/addon/second-search/ extends the web search bar (and the location bar, if the search bar is removed from the toolbar) totally: 

 * Provides ability to treat bookmark keywords just same as regular search engines.
 * Provides a rich drop target to select the search engine for a dropped text,
 * Provides ability to search with recently used search engines.

Actually I add many bookmark keywords for each MXR repository and heavily use them from "recent search engines" popup. After XUL is ended, the addon will die completely, so I need something to alter current methods to extend the search bar. Handling of events around the search bar is the basis. Moreover, I need more new APIs: custom popup panels, accessing to the search engines database, and others.

On the other hand, I've found two existing bugs to improve the search bar itself like as my addon:

 * bug 236587 – Allow bookmark keyword searches from the search bar / integrate toolbar and bookmark keyword searches
 * bug 261124 – Textbox context menu should have "Add to Search Bar..."

I don't know which is the better way: improving Firefox's search bar itself or just adding extensibility, but anyway I still need something alternative, thus I open this bug here.

	YUKI "Piro" Hiroshi Reporter
	Comment 1 • 8 years ago

Another topic, the addon Second Search provides custom drop target for the search bar. It appears when you are dragging some text onto the search bar, a list of search engines is shown as a popup. After you drop the text onto one of listed search engine, it will be searched by the engine. To migrate the feature to WebExtensions, I need ability to handle drag events on the search bar.

The bug 274432 is about implementing this behavior by Firefox itself. If it is fixed, the demand of this proposal will decrease for me.

	Caitlin Neiman [:caitmuenster]
	Comment 2 • 7 years ago

Hi Piro! We are going to discuss this at the April 4 WebExtensions API meeting. Would you be able to join the meeting? Time and call-in info is here: https://wiki.mozilla.org/Add-ons/Contribute/Triage#Details_.26_How_to_Join

Meeting agenda is here: https://docs.google.com/document/d/1V4NP4tWnjHigS2lAosCLfkU2FTcrQnoQzzXZmmB1uzk/edit#

	YUKI "Piro" Hiroshi Reporter
	Comment 3 • 7 years ago

(In reply to Caitlin Neiman (http://pronoun.is/she) from comment #2)
> Hi Piro! We are going to discuss this at the April 4 WebExtensions API
> meeting. Would you be able to join the meeting? Time and call-in info is
> here:
> https://wiki.mozilla.org/Add-ons/Contribute/Triage#Details_.26_How_to_Join

While the meeting I join to the IRC channel #Addons. If you have any question about this bug, please mention to me ("Piro").

	Amy Tsay [:amyt]
	Comment 4 • 7 years ago

Per triage discussion, please break these use cases into separate API methods, or separate the use cases into different bugs so we can discuss implementation methods for each.

	YUKI "Piro" Hiroshi Reporter
	Comment 5 • 7 years ago

Now I agree to close this as WONTFIX. Instead I should contribute to bug 236587, bug 261124, bug 274432 and more.

	Andy McKay
	Comment 6 • 7 years ago

Based on comment 5.