Re: QA Firefox 60 feature testing pi-requests deadline is January 10

2018-01-09 Thread Tom Grabowski
Hi, Just a reminder that the deadline for submitting your PI-requests for Fx60 feature testing is today. Thanks, Tom On Mon, Jan 8, 2018 at 12:30 PM, Tom Grabowski wrote: > > Hi, > > Similar to what QA did for Fx59 feature testing prioritization >

Re: Device Orientation API future

2018-01-09 Thread cwiemeersch
Exciting to hear, Kyle! As mentioned earlier, Chrome for Android M63+ has shipped an implementation (disabled by default, with an Origin Trial) of the Generic Sensor API, but TAG review (https://github.com/w3ctag/design-reviews/issues/207) feedback needs to be addressed. For our WebVR use

Re: Intent to unship: navigator.registerContentHandler()

2018-01-09 Thread Fabrice Desre
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()

2018-01-09 Thread Jonathan Kingston
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,

stockwell (intermittent failures) policy change - recommend disabling tests when 150 failures are seen in 21 days

2018-01-09 Thread jmaher
Happy new year from the stockwell team! We have been busy triaging bugs and getting the test-verify job to be fine tuned for all platforms and test suites. If you want to read about what we plan to do in the near future, you can follow along in this tracking bug:

Re: Password autofilling

2018-01-09 Thread Eric Rescorla
On Tue, Jan 9, 2018 at 8:43 AM, Gervase Markham wrote: > On 01/01/18 20:08, Jonathan Kingston wrote: > > A recent research post[1] have highlighted the need for Firefox to > disable > > autofilling of credentials. The research post suggests web trackers are > > using

Re: Intent to unship: navigator.registerContentHandler()

2018-01-09 Thread L. David Baron
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

Re: Intent to unship: navigator.registerContentHandler()

2018-01-09 Thread L. David Baron
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

Re: Password autofilling

2018-01-09 Thread Gervase Markham
On 01/01/18 20:08, Jonathan Kingston wrote: > A recent research post[1] have highlighted the need for Firefox to disable > autofilling of credentials. The research post suggests web trackers are > using autofilling to track users around the web. Autofill is restricted to same-domain (roughly) so

Re: Intent to unship: navigator.registerContentHandler()

2018-01-09 Thread Anne van Kesteren
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

Re: Intent to unship: navigator.registerContentHandler()

2018-01-09 Thread Gervase Markham
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