Re: Intent to ship: WebVR on Windows in Release

2017-03-02 Thread Boris Zbarsky
On 3/2/17 1:52 PM, kearw...@kearwood.com wrote: I tend to agree with Brandon on this particular issue That's fine. I agree with you and Brandon too. ;) I'm just worried about possible interop problems more than anything else at the moment. Would this issue block release of WebVR in

CodeCoverage: First Monthly Update

2017-03-02 Thread Kyle Lahnakoski
It is my pleasure to introduce you all to our project to collect code coverage! Motivation Knowing code coverage statistics and code coverage specifics can help evaluate risk in code: It can show what test suites cover what lines, it can show if new code is covered by an existing test. There

Re: Intent to ship: RC4 disabled by default in Firefox 44

2017-03-02 Thread akayla1977
On Tuesday, September 1, 2015 at 9:56:28 AM UTC-7, Richard Barnes wrote: > For a while now, we have been progressively disabling the known-insecure > RC4 cipher [0]. The security team has been discussing with other the > browser vendors when to turn off RC4 entirely, and there seems to be >

Re: Intent to ship: CSS 'transform-box' property

2017-03-02 Thread Jonathan Watt
On 01/03/2017 21:54, Jeff Muizelaar wrote: > What is the status of this property in other browsers? We would be the first to implement. Safari: it's primarily Apple people who edit the spec so I'd hope they'd implement, but who knows. Blink: previously when we've tried to get commitment there's

Re: ANN: Default bug view for BMO changed today!

2017-03-02 Thread Myk Melez
> Mike Hommey > 2017 March 1 at 14:50 > 1. I often wish browsers were helpful here. Seriously. When an anchor is > close enough to the end of the page that the page can't be scrolled for > it to be at the top of the viewport, it's a PITA to find where it is. Indeed. I

Re: Intent to ship: WebVR on Windows in Release

2017-03-02 Thread kearwood
On Thursday, March 2, 2017 at 11:04:07 AM UTC-8, David Baron wrote: > On Wednesday 2017-03-01 12:50 -0800, kgilb...@mozilla.com wrote: > > Since the initial implementation, a W3C working group was formed including > > members from Mozilla, Google, Microsoft, Samsung, and Oculus.  The API has > >

Re: Intent to ship: WebVR on Windows in Release

2017-03-02 Thread L. David Baron
On Wednesday 2017-03-01 12:50 -0800, kgilb...@mozilla.com wrote: > Since the initial implementation, a W3C working group was formed including > members from Mozilla, Google, Microsoft, Samsung, and Oculus.  The API has > stabilized and is frozen at "WebVR 1.1" while its successor "WebVR 2.0" is

Re: Intent to ship: WebVR on Windows in Release

2017-03-02 Thread kearwood
On Wednesday, March 1, 2017 at 2:55:53 PM UTC-8, Boris Zbarsky wrote: > On 3/1/17 5:03 PM, Kip Gilbert wrote: > > We have worked directly with the other WebVR platform implementers to > > ensure compatibility. > > OK, but what is the actual state of that compatibility? > >

Re: ANN: Default bug view for BMO changed today!

2017-03-02 Thread Byron Jones
Jörg Knobloch wrote: Some more feedback: While "3 years ago" is nice for the date display, I'd also like to see the full date and hour in a copyable form. Another bug for that? Or is there a setting that will do it already? set "Use absolute format instead of relative time when viewing a bug"

Re: ANN: Default bug view for BMO changed today!

2017-03-02 Thread Jörg Knobloch
On 02/03/2017 16:06, David Lawrence wrote: Thanks for the feedback. Please file this as a bug if you haven't already, outlining the proposed workflow change. I could see how automatically exposing the milestone form field when resolving a bug could be useful for a lot of people. Yes, maybe

Re: ANN: Default bug view for BMO changed today!

2017-03-02 Thread Benjamin Smedberg
One other tip which really helped me: you can hit Control-E to go to bug editing mode. I bet there are other cool keyboard shortcuts, but I don't know if there's a guide or not. --BDS On Wed, Mar 1, 2017 at 3:47 PM, David Lawrence wrote: >Today, the BMO Team changed

Re: ANN: Default bug view for BMO changed today!

2017-03-02 Thread David Lawrence
Thanks for the feedback. Please file this as a bug if you haven't already, outlining the proposed workflow change. I could see how automatically exposing the milestone form field when resolving a bug could be useful for a lot of people. Thanks dkl On 3/2/17 3:13 AM, Jörg Knobloch wrote: > On

Re: ANN: Default bug view for BMO changed today!

2017-03-02 Thread Jörg Knobloch
On 01/03/2017 21:47, David Lawrence wrote: Today, the BMO Team changed the default bug view to the new modal view that has been in development for a while. I like the fact that you can now change the Product in one step. Sadly when resolving a bug, there's now an additional click