We believe that we have addressed the remaining issues and we will turn WebVR
on by default in Windows, shipping in Firefox 55.
After discussions with the other major browser vendors, we believe that we are
all on track to ship a compatible version of the WebVR 1.1 draft specification
and have
Hi all! I'm a spec editor for WebVR and implementer on Chrome. Wanted to chime
in on a few points.
Boris: Thanks for the spec bugs you've filed and the concern about improving
the spec language to ensure consistent implementations between browsers. The
type of issues you have brought up are exa
On Monday, March 6, 2017 at 12:15:25 PM UTC-8, Boris Zbarsky wrote:
> On 3/6/17 3:03 PM, kearw...@kearwood.com wrote:
> > The underlying VR API's expect this process to persist for the browser's
> > lifespan and to have mutually-exclusive access to input from the headsets.
> > It seems that the
On 3/6/17 3:03 PM, kearw...@kearwood.com wrote:
The underlying VR API's expect this process to persist for the browser's
lifespan and to have mutually-exclusive access to input from the headsets. It
seems that the GPU process is the best fit afaict.
In case it matters, the GPU process does n
On Friday, March 3, 2017 at 10:42:43 AM UTC-8, Ehsan Akhgari wrote:
> On Fri, Mar 3, 2017 at 12:36 PM, wrote:
>
> > Hi Ehsan!
> >
> > I believe all IPC messages can be changed to async except GetSensorState
> > and SubmitFrame. We cache the results from GetSensorState and re-use it
> > until the
On Fri, Mar 3, 2017 at 12:36 PM, wrote:
> Hi Ehsan!
>
> I believe all IPC messages can be changed to async except GetSensorState
> and SubmitFrame. We cache the results from GetSensorState and re-use it
> until the next frame.
>
Hmm, not sure if I understand correctly. Did you actually mean "e
Hi Kearwood,
I and a few other engineers have been studying the performance of
Firefox for several weeks now as part of the Quantum Flow project and
one of the serious performance issues that we have been finding in
various parts of the browser have been synchronous IPC messages sent
from the cont
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 Firefo
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
> >
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
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?
>
> https://github.com/w3c
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?
https://github.com/w3c/webvr/issues/197#issuecomment-283492774 and
https://github.com/w3c/webvr/issues/195
Sent from my iPad
> On Mar 1, 2017, at 1:32 PM, Boris Zbarsky wrote:
>
>> On 3/1/17 3:50 PM, kgilb...@mozilla.com wrote:
>> As of March 1, 2017 I intend to turn WebVR on by default on Windows.
>
> So flip the pref on Windows only, right?
Yes, flipping pref on only for Windows. Later, we wil
Last I looked, we didn't have any tests for VRFrameData, FWIW (bug
1317258). I see some now under servo/ but presumably we don't run those.
Maybe I'm missing some.
It would also be good to make sure our internal fuzzers are fuzzing these
APIs to at least catch basic errors.
Andrew
On Wed, Mar 1,
On 3/1/17 3:50 PM, kgilb...@mozilla.com wrote:
As of March 1, 2017 I intend to turn WebVR on by default on Windows.
So flip the pref on Windows only, right?
If there is no VR hardware, is the idea that navigator.getVRDisplays()
returns a promise resolving to an empty array?
Link to standar
As of March 1, 2017 I intend to turn WebVR on by default on Windows. It has
been developed behind the dom.vr.enabled preference and has been enabled by
default on Firefox Nightly and Dev Edition since November 2015. Other UAs
shipping this include Samsung Internet Browser (Gear VR) and Oculus
16 matches
Mail list logo
