4 ms·

Firefox Developer Edition is not the same as nightly from what I understand. Setting gfx.compositor.glcontext.opaque to true makes firefox unusable as alerts a

Firefox Developer Edition is not the same as nightly from what I understand. Setting gfx.compositor.glcontext.opaque to true makes firefox unusable as alerts aren't readable (might be theme dependent). The only setting that you need to get FF to work on macos with a retina screen is the 'low resolution' mode trick. But then all text, etc isn't as smooth. I am now running some tests with the new nightly, so far it seems like it fixes the issues and I am very excited about this!

Fnoord 7y ago
> Firefox Developer Edition is not the same as nightly from what I understand. It isn't, but this fix has already been around for a while. I've been using it for about a week. Back then, I was advised to run Firefox Developer Edition. I'd rather run that, than Nightlies.
- fernandotakai 7y ago
  according to @whimboo[0], these specific changes will land later this week on the developer edition. [0] https://twitter.com/whimboo/status/1168476885766082561 https://twitter.com/whimboo/status/1168476885766082561
  - Fnoord 7y ago
    Note the wording: "all of these changes". The first part of the change which I've been using for a week now, is already in Developer Edition. It has the largest effect. The most recent change has a small (but noticeable) effect. FWIW, Nightly just managed to crash my MBP. Which, for the record, is normally rock stable.
    - floatingatoll 7y ago
      Caveat emptor: You are likely to be running with altered config settings, as indicated by your advice above to others, and it’s occasionally found that about:config changes are what are causing crashes. Consider unwinding your changes to provide a more accurate outcome. (I’m not part of Firefox, just pointing out an especially common expert user self-inflicted issue.)
      - Fnoord 7y ago
        Thank you for the heads up. It hasn't crashed ever since (the nature of the crash made it appear related to using Nightly). I'll be switching back to Developer Edition ASAP as either b3 or b4 has the same fix.

Fnoord 7y ago

> Firefox Developer Edition is not the same as nightly from what I understand. It isn't, but this fix has already been around for a while. I've been using it for about a week. Back then, I was advised to run Firefox Developer Edition. I'd rather run that, than Nightlies.

fernandotakai 7y ago
according to @whimboo[0], these specific changes will land later this week on the developer edition. [0] https://twitter.com/whimboo/status/1168476885766082561 https://twitter.com/whimboo/status/1168476885766082561
- Fnoord 7y ago
  Note the wording: "all of these changes". The first part of the change which I've been using for a week now, is already in Developer Edition. It has the largest effect. The most recent change has a small (but noticeable) effect. FWIW, Nightly just managed to crash my MBP. Which, for the record, is normally rock stable.
  - floatingatoll 7y ago
    Caveat emptor: You are likely to be running with altered config settings, as indicated by your advice above to others, and it’s occasionally found that about:config changes are what are causing crashes. Consider unwinding your changes to provide a more accurate outcome. (I’m not part of Firefox, just pointing out an especially common expert user self-inflicted issue.)
    - Fnoord 7y ago
      Thank you for the heads up. It hasn't crashed ever since (the nature of the crash made it appear related to using Nightly). I'll be switching back to Developer Edition ASAP as either b3 or b4 has the same fix.