Now that bug 985252 is about to land and the Windows sandboxing code will be compiled unconditionally, it makes sense to allow the content sandbox to be turned on via a pref. This will make it easier for people to test the sandbox and for when we want to start running tests on tinderbox with e10s and the sandbox enabled. I think it makes sense to only have this pref in nightly.
So far we've been using environment variables for enabling/disabling sandboxing at runtime. Is there a preference (no confusion intended) one way or the other for environment variables vs a nightly-only pref?
(In reply to Tim Abraldes [:TimAbraldes] [:tabraldes] from comment #1) > So far we've been using environment variables for enabling/disabling > sandboxing at runtime. Is there a preference (no confusion intended) one way > or the other for environment variables vs a nightly-only pref? Well, I think one of the factors here is that we want addon developers to be able to test their code with the sandbox enabled. That was the original reason I started looking at a warn only sandbox (I'm not sure where the original request came from). I would imagine that flipping a pref would be fairly familiar to most addon developers, but I have no solid evidence to back that up. :) I'm happy to go with any solution that makes things straight forward and doesn't involve actually building firefox.
Done as part of bug 1018966.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.