Re: Proposed W3C Charter: Immersive Web Working Group

In case others haven't already asked... We have contributed to the content of the new charter and I would advise that Mozilla respond with support. Of course, I would be glad to hear feedback and raise it with the Immersive-Web W3C group if anyone has any concerns. Cheers, - Kip On Tue, Mar

Re: Coding style  : `int` vs `intX_t` vs `unsigned/uintX_t`

Hello! Just wish to chime in with my 2c... Would the proposed shift towards signed types only be for larger values (eg, >= 32 bits)? Audio and rendering code would still require using unsigned types, especially when packed into buffers. (eg, 8-bit unsigned color components, 32-bit packed RGBA

PSA - Planning to enable VR service process on desktop (Linux, macOS, and Windows)

! Cheers, * Kearwood “Kip” Gilbert ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Intent to implement and ship: WebXR Device API in Firefox Nightly

Summary: The successor to WebVR 1.1, the WebXR Device API 1.0, is nearing finalization. The WebXR Device API follows modern Web API patterns, is extensible additively for augmented reality, enables use within Web Workers, and solves many security problems for the VR and AR enabled web. The

Intent to remove: WebVR on insecure contexts

Summary: WebVR on insecure contexts (i.e. web sites served over non-HTTPS) is deprecated and will soon stop working in Firefox. Sites wanting to use WebVR should switch to HTTPS if they have not already. Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1381645 Link to standard:

Intent to ship: WebVR on macOS

As of 2017-10-01, I intend to turn WebVR on by default for macOS. It has been developed behind the dom.vr.enabled preference. We have already shipped WebVR by default for the Windows platform. macOS support has been implemented for several months but disabled by default. Our WebVR

RE: Intent to remove: sensor APIs

Please note that disabling the Device Orientation API will also effectively disable the “WebVR Polyfill”. The “WebVR Polyfill” is a javascript library that allows browser that otherwise don’t support VR (ie, Fennec) to use “Cardboard” VR holders to create simple VR experiences. Usage of these

RE: Profiling nightlies on Mac - what tools are used?

I would add to this Apple’s “OpenGL Profiler”: https://developer.apple.com/library/content/technotes/tn2178 Cheers, - Kip From: Bobby Holley Sent: June 19, 2017 3:08 PM To: Chris Cooper Cc: dev-platform@lists.mozilla.org Subject: Re: Profiling nightlies on Mac - what tools are used?

RE: Running mochitest on packaged builds with the sandbox

. Cheers, - Kearwood “Kip” Gilbert From: Alex Gaynor Sent: May 9, 2017 7:58 AM To: Kearwood Kip Gilbert Cc: dev-platform@lists.mozilla.org Subject: Re: Running mochitest on packaged builds with the sandbox Hi, Hmm, VR appears to be an interesting challenge. To expand a bit more on why mochitest

RE: Running mochitest on packaged builds with the sandbox

the sandboxing rules configurable at runtime? Cheers, - Kearwood “Kip” Gilbert From: Alex Gaynor Sent: May 8, 2017 10:26 AM To: dev-platform@lists.mozilla.org Subject: Running mochitest on packaged builds with the sandbox Hi dev-platform, Top-line question: Do you rely on being able to run

Re: Intent to ship: WebVR on Windows in Release

uot; is > being conceived. > > Windows only support for WebVR would be enabled by default in Firefox 54. > OSX is not yet supported by current VR headsets. Beta Linux support for HTC > Vive has very recently landed, and will be supported by Firefox after the > Firefox 54 upli

Re: Intent to ship: WebVR on Windows in Release

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

Request Feedback - Submitting Canvas Frames, WebVR Compositor

review — I look forward to your feedback! Cheers, - Kearwood “Kip” Gilbert ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: "-Moz-Element" -like API by extending WEBGL_dynamic_texture

On 2016-01-04 3:54 PM, Xidorn Quan wrote: > On Tue, Jan 5, 2016 at 8:46 AM, Kearwood "Kip" Gilbert > <kgilb...@mozilla.com> wrote: >> Hello All, >> >> In WebVR, we often present UI as a Head's Up Display (HUD) that floats >> in front of the user. A

Re: "-Moz-Element" -like API by extending WEBGL_dynamic_texture

On 2016-01-04 4:46 PM, Robert O'Callahan wrote: > On Tue, Jan 5, 2016 at 10:46 AM, Kearwood "Kip" Gilbert < > kgilb...@mozilla.com> wrote: > >> In WebVR, we often present UI as a Head's Up Display (HUD) that floats >> in front of the user. Additionally, we oft

Re: "-Moz-Element" -like API by extending WEBGL_dynamic_texture

On 2016-01-04 4:54 PM, Robert O'Callahan wrote: > On Tue, Jan 5, 2016 at 1:18 PM, Jonas Sicking wrote: > >> A big problem is sticking HTML/CSS content into WebGL is that WebGL >> effectively enables reading pixel data through custom shaders and >> timing attacks. >> > If you

Re: "-Moz-Element" -like API by extending WEBGL_dynamic_texture

; > I think that it would be most efficient just to have a meeting about > these topics, instead of iterating slower via email. Sounds great, if you don't mind joining in. I'll ping you and get something set up. > > -Jeff Thanks again, Jeff! > > On Mon, Jan 4, 2016 at 1:46 PM, K

"-Moz-Element" -like API by extending WEBGL_dynamic_texture

uch easier. If others feel the same, I would also like to follow up with a proposal to make the captured HTML elements interactive through use of an explicit "pick buffer" added to canvases. I look forward to your feedback. Cheers, - Kearwood "Kip" Gilbert _

Re: APZ enabled on Fennec nightly

Excellent, Kats!! Perhaps this will also unblock smooth scrolling and scroll snapping for fennec. Cheers, - Kearwood “Kip” Gilbert > On Nov 30, 2015, at 8:37 AM, Kartikaya Gupta <kgu...@mozilla.com> wrote: > > Hi all, > > Just a heads up that I landed the patch to

Intent to ship: WebVR

As of Oct 29, 2015 I intend to turn WebVR on by default for all platforms. It has been developed behind the dom.vr.enabled preference. A compatible API has been implemented (but not yet shipped) in Chromium and Blink. Bug to turn on by default:

Re: Proposal to remove `aFoo` prescription from the Mozilla style guide for C and C++

I would defer to the expert on the subject: https://imgflip.com/i/o5r8m - Kip On 2015-07-07 6:17 PM, David Anderson wrote: +1 for removing this. Gecko's use is inconsistent, and outside of Gecko code that does use it, I've never seen it used in any other codebase. I've never gone to

Re: Largest chunks of code that are likely to be removable?

Would anyone be opposed to combining the Matrix4x4 class and gfx3DMatrix? Rather than adding support for transforms and projections that involve vertices behind the w=0 plane to gfx3DMatrix, it may be cleaner to refactor affected call-sites to use Matrix4x4 instead. The remaining references

Intent to Ship: DEAA (Antialiasing) for CSS Transformed Layer Edges for the OpenGL Compositor (OSX and Linux)

Kip Gilbert ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Intent to Implement: DEAA (Antialiasing) for CSS Transformed Layer Edges

Summary: Edges of layers with rotations and projections applied through CSS transforms have stair-step, aliased edges. Visiting the attached URL demonstrates the aliasing effect. Applying DEAA (Distance to Edge Anti-aliasing) for transformed layers enables anti-aliasing without requiring

Intent to Ship: CSS Scroll Snapping on Desktop

, deleted, resized), the scroll offset must be modified to maintain this guarantee.. Support for this is tracked in Bug 1124324 (Perform instant and smooth scrolls to maintain guarantees set by scroll snapping CSS attributes when content changes) and will be landed separately. - Kearwood Kip Gilbert

Intent to ship: CSS Scroll Snapping on B2G / Firefox OS

, resized), the scroll offset must be modified to maintain this guarantee.. Support for this is tracked in Bug 1124324 (Perform instant and smooth scrolls to maintain guarantees set by scroll snapping CSS attributes when content changes) and will be landed separately. - Kearwood Kip Gilbert

Re: Detecting 32 or 64-bit Firefox build from privileged JS

be useful to track the number of non-Android ARM users. - Kearwood Kip Gilbert On 2015-02-24 9:52 PM, ishikawa wrote: On 2015年02月24日 20:28, Kyle Huey wrote: I'm also not sure why you care about arcane architectures like Itanium, Alpha, and SPARC, since there are approximately zero users of those

Re: Intent to ship: CSSOM-View Scroll-Behavior CSS Property and CSSOM-View DOM Extensions for Smooth Scrolling

and fling gestures. Cheers, - Kearwood Kip Gilbert On 2014-10-27, 10:11 PM, Jonas Sicking wrote: Last we talked about this, I thought that we concluded that smooth scrolling wasn't so much a property of the element, but rather a property of the callsite. See my two emails to the intent

Intent to ship: CSSOM-View Scroll-Behavior CSS Property and CSSOM-View DOM Extensions for Smooth Scrolling

As of October 28, 2014 I intend to turn on by default CSSOM-View Scroll-Behavior CSS Property and CSSOM-View DOM Extensions related to smooth scrolling. They have been developed behind the layout.css.scroll-behavior.enabled and layout.css.scroll-behavior.property-enabled preferences. Firefox is

Re: Intent to implement: CSSOM-View scroll-behavior property

support, then a new bug will be created to track a non-APZ-dependent implementation. - - Kip On 2014-05-22, 1:50 PM, Kip Gilbert wrote: Summary: CSSOM-View defines a new css property, 'scroll-behavior'. When set to 'smooth', scrolling boxes will be scrolled in a smooth fashion using a user

Re: Intent to implement: CSSOM-View scroll-behavior property

the kind of movement it has to the movement model I proposed for the smooth scroll behavior? - - Kip On 2014-06-10, 12:57 PM, Kip Gilbert wrote: The bug has been split up to track individual parts of the implementation: Bug 1010538 - Implement CSSOM-View scroll-behavior CSS property Bug 1022818

Re: Intent to implement: DOMMatrix

Hello, From a game programmer's perspective, isIdentity would normally be used to cull out work. In these cases, it is expected that isIdentity will return true only when the matrix is exactly equal to the identity matrix. Due to the nature of floating point, the isIdentity will only

Re: Intent to implement: DOMMatrix

On 2014-06-06, 1:23 PM, Rik Cabanier wrote: On Fri, Jun 6, 2014 at 12:18 PM, Kip Gilbert kgilb...@mozilla.com mailto:kgilb...@mozilla.com wrote: Hello, From a game programmer's perspective, isIdentity would normally be used to cull out work. In these cases, it is expected

Intent to implement: CSSOM-View scroll-behavior property

Summary: CSSOM-View defines a new css property, 'scroll-behavior'. When set to 'smooth', scrolling boxes will be scrolled in a smooth fashion using a user-agent-defined function. Implementing this property will enable more fluid scrolling interfaces consistent with modern UI paradigms

Re: Intent to implement and ship: navigator.hardwareConcurrency

into account to effectively optimize for core count. This seems out of place given the level of abstraction web developers expect. I can also imagine a very-short-term future where CPU core count will be an outdated concept. Cheers, - Kearwood Kip Gilbert On 2014-05-13, 10:58 AM