Hardening the Firefox Sandbox

Hi all, Security Engineering has started a project to harden Firefox against attack in a post-sandboxed world. It’s early days yet for sandboxing, but conscious of the work required, I wanted to raise sandboxing as a topic for discussion, and request input towards developing a sandbox security

Re: Runnable labeling for Quantum DOM

Double indeed! Very cool to see this happening! On a logistical note, do we have a meta bug that could track all the bugs about labeling etc, so that we can hang individual bugs off of that one to help avoid multiple bugs being filed and worked on for the same thing? Thanks! - jst On Thu, Dec

Re: Runnable labeling for Quantum DOM

On Thu, Dec 1, 2016 at 8:21 PM, Boris Zbarsky wrote: > P.S. This is awesome. ;) Indeed. So glad this is finally happening. - Kyle ___ dev-platform mailing list dev-platform@lists.mozilla.org

Re: Runnable labeling for Quantum DOM

On 12/1/16 10:40 PM, Bill McCloskey wrote: As part of the Quantum DOM project, we're going to be "labeling" all runnables in the browser to say which document they're operating on. Is the intent basically to get rid of NS_DispatchToMain/CurrentThread, or at least get their usage down to a

Runnable labeling for Quantum DOM

Hi everyone, As part of the Quantum DOM project, we're going to be "labeling" all runnables in the browser to say which document they're operating on. Labeling will allow us to prioritize some documents over other documents as well as running different documents concurrently. An API for labeling

Re: Upcoming rename of the marionette-client package to marionette-harness

Note that this kind of changes may lead to weird Python error. We have seen one in bug 1321468. If you recently see any unexpected Python error when running mach commands, try execute "./mach clobber python" first. ("./mach clobber" would *not* work because it only purges things inside the

Re: Intent to implement: Web2Native Bridge

On Thursday, December 1, 2016 at 9:51:36 PM UTC+1, Nicholas Alexander wrote: Hi Nicholas, I want to avoid a long (and for other people boring) debate, but I feel that I must at least *try* to describe what this is all about... I would recommend a peek in this document which describes the

Re: Intent to implement: Web2Native Bridge

On Wed, Nov 30, 2016 at 2:40 AM, Anders Rundgren < anders.rundgren@gmail.com> wrote: > On Tuesday, November 29, 2016 at 10:01:38 PM UTC+1, Nicholas Alexander > wrote: > Hi Nick, > Many thanks for your elaborate comments! > Heh, that message kept growing and probably could be a blog post when

Re: Proposed W3C Charter: Web of Things Working Group

Hi Tantek, On the very serious issues of security and privacy on the Internet of Things, I agree with you. On your proposed solution to those problems of somehow trying to slow down the worldwide deployment of IoT devices (currently forecast to reach tens of billions by 2020) and prevent any

Upcoming rename of the marionette-client package to marionette-harness

Hi, Please note that we will soon rename the marionette-client Python package to marionette-harness. This work is currently happening on bug 1320073. The reason for it is that there is lots of confusion between the package names and the folder names in-tree: > testing/marionette/client ->

ATMOv2 Domain Change Complete

Hello All, This is a followup email to let everyone know that we've completed switching the main ATMO domain (analysis.telemetry.mozilla.org) to point to ATMOv2. If you had previously been using atmo.prod.mozaws.net, this is the same service (there's a redirect in place) and you should use the