<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><span style="font-family:arial,sans-serif">On Tue, Mar 27, 2018 at 1:09 PM, Boris Zbarsky </span><span dir="ltr" style="font-family:arial,sans-serif"><<a href="mailto:bzbarsky@mit.edu" target="_blank">bzbarsky@mit.edu</a>></span><span style="font-family:arial,sans-serif"> wrote:</span><br></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 3/27/18 1:02 PM, Eric Shepherd wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Yes, that's true. My thinking is that a first step could be to change it so it had to be enabled using Policy Engine, and have an ESR release with that<br>
</blockquote>
<br></span>
So presumably targeting 60? The timing is a bit tight...<br></blockquote><div><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Yeah, I suppose. Otherwise you have to wait quite a while. But I think if you were going to make it deprecated for ESR 60, it should be doable, if the decision were made quickly enough.</div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Note that as things stand the only way to enable remote XUL for a hostname is by adding permission manager entries. This needs to either be done by a non-webextension extension, or by running code in a privileged context (e.g. browser console) or by directly munging the sqlite database involved. This last is what we do in our automation.<span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
with a notice to users of ESR that that will be the last ESR release to support remote XUL.<br>
</blockquote>
<br></span>
We can do that anyway, for 60, without changing how it's enabled, right?</blockquote><div><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">In that case, yeah, I would think that if you have to add a permission for it, you're probably okay -- unless there's a desire to have it together with the other Policy Engine stuff just for consistency purposes when customizing Firefox for enterprise use.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div></div><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><br>Eric Shepherd<br>Senior Technical Writer<br>Mozilla<br>Blog: <a href="http://www.bitstampede.com/" target="_blank">http://www.bitstampede.com/</a><br>Twitter: <a href="http://twitter.com/sheppy" target="_blank">http://twitter.com/sheppy</a><br>
<a style="font-style:italic" href="https://freebusy.io/eshepherd@mozilla.com" target="_blank">Check my Availability</a><br></div></div></div>
</div></div>