Does this sandbox userChrome.js? User tustamido seems to say AutoConfig and userChrome.js are equivalent, in which case I'm glad I never bothered testing the CSS or add-on icon code from the pages we discussed, because I'm not sure I'd want to use ESR just to maintain that functionality (but I'm not sure why I would not want to. Security's a concern, though; while the ESR version might be as fully patched as that version of Firefox can be, that doesn't resolve security holes only fixed in later versions that also affect ESR but don't get patched for ESR).
Tustamido also campaigned for AutoConfig to remain unsandboxed in Nightly, Betas and so on, but no one ever said if it would be or not. I'd continue to pursue workarounds for Nightly or Betas but I just don't see myself jumping backward for an ESR (I'm already using Waterfox just to edit CSS because tools I'm comfortable using/that do what I want literally don't exist outside of it, and Waterfox is slow/insecure/backwards enough as it is. It's actually really awful).
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
chiming
Re: Mozilla/Firefox did it again
Date: 2018-09-16 08:46 am (UTC)From:Tustamido also campaigned for AutoConfig to remain unsandboxed in Nightly, Betas and so on, but no one ever said if it would be or not. I'd continue to pursue workarounds for Nightly or Betas but I just don't see myself jumping backward for an ESR (I'm already using Waterfox just to edit CSS because tools I'm comfortable using/that do what I want literally don't exist outside of it, and Waterfox is slow/insecure/backwards enough as it is. It's actually really awful).