Re: Intent to unship: navigator.registerContentHandler()

On Thu, Jan 11, 2018 at 11:43 AM, Daniel Veditz wrote: > On Wed, Jan 10, 2018 at 5:35 PM, Tantek Çelik > wrote: >> >> Also good methodology worth repeating: >>"thinking ... through all the way up to and including the user >> experience, makes for a much more viable approach" > > > Including,

Re: Intent to unship: navigator.registerContentHandler()

On Wed, Jan 10, 2018 at 5:35 PM, Tantek Çelik wrote: > Also good methodology worth repeating: >"thinking ... through all the way up to and including the user > ​​ > experience, makes for a much more viable approach" > ​Including, of course, "how will 4chan trolls abuse this?" and "how will a

Re: Intent to unship: navigator.registerContentHandler()

On Wed, Jan 10, 2018 at 2:19 AM, Anne van Kesteren wrote: > On Wed, Jan 10, 2018 at 2:06 AM, Fabrice Desre wrote: >> WebShare is more a trimmed down version of the WebActivities/WebIntents >> apis. I think it's unfortunate that instead of fixing the issues with WA/WI >> they went with a single pu

Re: Intent to unship: navigator.registerContentHandler()

On Tue, Jan 9, 2018 at 8:51 AM, L. David Baron wrote: > On Wednesday 2018-01-03 15:15 +, Jonathan Kingston wrote: >> I am suggesting the removal of navigator.registerContentHandler >> >> API used to register a

Re: Intent to unship: navigator.registerContentHandler()

I really like this extension mechanism for the web. Unlike, say, registerProtocolHandler, which is relatively widely supported, registerContentHandler allows extensibility for experiencing resources on the web while still remaining on the firm earth of HTTP and the web. If possible, I'd prefer

Re: Intent to unship: navigator.registerContentHandler()

On Wed, Jan 10, 2018 at 2:06 AM, Fabrice Desre wrote: > WebShare is more a trimmed down version of the WebActivities/WebIntents > apis. I think it's unfortunate that instead of fixing the issues with WA/WI > they went with a single purpose API - this doesn't scale at all with uses > case they don'

Re: Intent to unship: navigator.registerContentHandler()

On 01/09/2018 04:59 PM, Jonathan Kingston wrote: I would like to see the expansion of this feature here, especially for handling more types of content. Chrome has been working on Web Share Target API[1] which somewhat overlaps this behaviour and could be expanded to cope with the use cases here.

Re: Intent to unship: navigator.registerContentHandler()

I would like to see the expansion of this feature here, especially for handling more types of content. Chrome has been working on Web Share Target API[1] which somewhat overlaps this behaviour and could be expanded to cope with the use cases here. I actually think web sharing is the answer here, it

Re: Intent to unship: navigator.registerContentHandler()

On Tuesday 2018-01-09 08:51 -0800, L. David Baron wrote: > I'm a little hesitant here -- this is an important feature for > allowing Web apps to fulfil the function that desktop apps do, and > I'd rather push to see it expand. > > For example, if we added support for registering for text/calendar,

Re: Intent to unship: navigator.registerContentHandler()

On Wednesday 2018-01-03 15:15 +, Jonathan Kingston wrote: > I am suggesting the removal of navigator.registerContentHandler > > API used to register a web page to handle content types. > > Firefox has an implem

Re: Intent to unship: navigator.registerContentHandler()

On Tue, Jan 9, 2018 at 5:30 PM, Gervase Markham wrote: > I'm sure unshipping it is the right thing to do, but it's very sad. :-( > Allowing web pages to register for content types and protocols seems > kind of important if you want the web to have the capability of > seamlessly replacing desktop a

Re: Intent to unship: navigator.registerContentHandler()

On 03/01/18 15:15, Jonathan Kingston wrote: > I am suggesting the removal of navigator.registerContentHandler > > API used to register a web page to handle content types. I'm sure unshipping it is the right thing t

Re: Intent to unship: navigator.registerContentHandler()

On 04.01.2018 04:46, Karl Dubost wrote: > Jonathan, > > Le 4 janv. 2018 à 00:15, Jonathan Kingston a écrit : >> Firefox has an implementation that only can be used to allow a web page to >> handle RSS feeds. > > in Firefox 8, the feeds panel was removed from Firefox. It created a bit of > ba

Re: Intent to unship: navigator.registerContentHandler()

Jonathan, Le 4 janv. 2018 à 00:15, Jonathan Kingston a écrit : > Firefox has an implementation that only can be used to allow a web page to > handle RSS feeds. in Firefox 8, the feeds panel was removed from Firefox. It created a bit of bad press. Some people have developed add-ons to cope wit

Re: Intent to unship: navigator.registerContentHandler()

> I like the approach of disabling a feature (behind a pref) in non-Release (Beta and Nightly) for a few releases, to see what surfaces in bug reports. This is reasonable, it is the approach we will be taking with the device sensors. Obviously it takes a little more work however I'm guessing the

Re: Intent to unship: navigator.registerContentHandler()

Hi Jonathan, > On Jan 3, 2018, at 9:15 AM, Jonathan Kingston wrote: > There is a small risk of breakage that we could decide to delay and instead > implement telemetry. However if the site is feature testing rather than > user agent testing there shouldn't be an issue here. As this API throws > e

Intent to unship: navigator.registerContentHandler()

I am suggesting the removal of navigator.registerContentHandler API used to register a web page to handle content types. Firefox has an implementation that only can be used to allow a web page to handle RSS feeds.