Re: Intent to ship: Autodiscovery of WebExtension search engines

2020-03-05 Thread Dale Harvey
OpenSearch is not a standard and as far as I understand it almost no wrote: > I would also like to mirror the previous comments: Why do we need to > expose this new non-standard feature to the web? Can't we just > transform OpenSearch XML internally to the new WebExtension format? > > On Wed,

Re: Intent to ship: Autodiscovery of WebExtension search engines

2020-03-05 Thread Tom Schuster
I would also like to mirror the previous comments: Why do we need to expose this new non-standard feature to the web? Can't we just transform OpenSearch XML internally to the new WebExtension format? On Wed, Feb 26, 2020 at 1:17 PM Henri Sivonen wrote: > > On Tue, Feb 25, 2020 at 10:04 PM Dale

Re: Intent to ship: Autodiscovery of WebExtension search engines

2020-02-26 Thread Henri Sivonen
On Tue, Feb 25, 2020 at 10:04 PM Dale Harvey wrote: > Yes, extensions that only define a new search engine will be permitted, > the extension will not be able to do anything else. What capabilities do search engine-only WebExtensions have that OpenSearch doesn't provide? -- Henri Sivonen

Re: Intent to ship: Autodiscovery of WebExtension search engines

2020-02-25 Thread Dale Harvey
Sorry I had replied but only just realised the discussion had been taken off list > Does this code enforce that the .xpi we download and attempt to install is actually a search type and not an arbitrary WebExtension Yes, extensions that only define a new search engine will be permitted, the

Re: Intent to ship: Autodiscovery of WebExtension search engines

2020-02-25 Thread Dale Harvey
On Thu, 20 Feb 2020 at 00:17, Daniel Veditz wrote: > On Wed, Feb 19, 2020 at 2:10 PM Dale Harvey wrote: > >> > If you _do_ invent a new one shared with other browser vendors, please >> > don't use an "x-" prefix in anything new. >> >> Thanks, I got notice of others concerns about this as well

Re: Intent to ship: Autodiscovery of WebExtension search engines

2020-02-19 Thread Daniel Veditz
On Wed, Feb 19, 2020 at 2:10 PM Dale Harvey wrote: > > If you _do_ invent a new one shared with other browser vendors, please > > don't use an "x-" prefix in anything new. > > Thanks, I got notice of others concerns about this as well and have been > looped in to discuss this more with standards

Re: Intent to ship: Autodiscovery of WebExtension search engines

2020-02-19 Thread Adam Roach
On 2/14/2020 5:05 PM, Daniel Veditz wrote: On Fri, Feb 14, 2020 at 11:50 AM Dale Harvey wrote: We’re proposing a new mime-type [...]: “x-xpinstall” for WebExtension search engines. Example: This is confusingly similar to "application/x-xpinstall" which we use to trigger extension installs

Re: Intent to ship: Autodiscovery of WebExtension search engines

2020-02-19 Thread Ehsan Akhgari
Hi Dale, It seems that this feature is not being developed with the hope of it turning into a cross-browser autodiscovery of search extensions in the future. With that in mind, I'd like to ask if it is really necessary to expose a new meta tag to the web platform, given the unclear path to the

Re: Intent to ship: Autodiscovery of WebExtension search engines

2020-02-14 Thread Daniel Veditz
On Fri, Feb 14, 2020 at 11:50 AM Dale Harvey wrote: > We’re proposing a new mime-type [...]: “x-xpinstall” for WebExtension > search > engines. Example: /" some authors will tend to fill in the "missing" bit and get it wrong, and others will complain that the syntax is non-standard and broken.

Intent to ship: Autodiscovery of WebExtension search engines

2020-02-14 Thread Dale Harvey
Summary: Since Firefox 57, users have been able to install additional search engines in the shape of a WebExtension[1] from addons.mozilla.org (AMO), whereas this used to only be possible using the OpenSearch XML format[2]. Since Firefox 68, all the search engines we distribute are