Re: Change in the way e10s and multi are enabled on Nightly

2017-10-18 Thread Andrew Swan 
On Wed, Oct 18, 2017 at 3:22 PM, Justin Dolske  wrote:

> On Wed, Oct 18, 2017 at 11:52 AM, Blake Kaplan  wrote:
>
>>
>> One more thing to point out: with the removal of e10srollout, I also
>> removed the code that would disable e10s if we detected a
>> non-multiprocessComptaible extension. We are entirely relying on the addon
>> manager to refuse to install such extensions.
>>
>>
> If someone on a pre-release channel enables legacy addons, will that still
> refuse to load non-E10S compatible addons? (I hope so?)
>

Legacy extensions can only be enabled on nightly and unbranded builds (not
on beta).  On Nightly, a non-MPC extension won't load unless you also flip
the preference extensions.allow-non-mpc-extensions.  If both those prefs
are flipped on Nightly, we will load the extension with shims enabled but
will not disable e10s.

Why don't we rip this all out you ask?  We're still using shims in
automation, see bug 1351512.  If anybody reading this has some spare cycles
(ha) and wants to do a good deed, you should be able to find remaining uses
by running tests with extensions.interposition.enabled set to false and
tracing resulting failures...

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

Re: Change in the way e10s and multi are enabled on Nightly

2017-10-18 Thread Justin Dolske 
On Wed, Oct 18, 2017 at 11:52 AM, Blake Kaplan  wrote:

>
> One more thing to point out: with the removal of e10srollout, I also
> removed the code that would disable e10s if we detected a
> non-multiprocessComptaible extension. We are entirely relying on the addon
> manager to refuse to install such extensions.
>
>
If someone on a pre-release channel enables legacy addons, will that still
refuse to load non-E10S compatible addons? (I hope so?)

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