This could be a mess for some folks that use older, no longer supported add-ons...I'm guessing.
While waiting on nightly builds to start running again to actually test, is there anything to look at to see if any of the add-ons that I use will be affected by this change? I don't have enough knowledge about these binary codings to know what to look for.
This could be a mess for some folks that use older, no longer supported add-ons...I'm guessing.
While waiting on nightly builds to start running again to actually test, is there anything to look at to see if any of the add-ons that I use will be affected by this change? I don't have enough knowledge about these binary codings to know what to look for.
Above my "pay grade" as well. Fortunately you have the ability to step back to an older rev, a lot of folks do not. So just wait and see I guess.
Well, what you'd usually do is to have at least a build-time switch for these things. Killing off an entire project like that just because Firefox doesn't like the mechanism it is using is just reckless...
rsx11m wrote:Well, what you'd usually do is to have at least a build-time switch for these things. Killing off an entire project like that just because Firefox doesn't like the mechanism it is using is just reckless...
i dont think it'll hurt TB38 but the next versions after tb38 it will. but they have to start doing this at some point in time. so they might as well do it now. sure its gonna upset some people but not all is lost IMO , but whether Fedora Maintainerss Hack out Lightning from 38 i dont know as someone has been Packaging that for a long time just like someone Packages ABP in Fedora also
In case you missed it, Lightning has been broken by Firefox disallowing a Core feature which it has to rely on. This has absolutely nothing to do with Fedora (though distros could choose to back out respective patches from their builds, at least as long as they aren't bitrotted by further changes).
Thunderbird 38.x will not be affected by this change (TB 40.0 beta and SM 2.37). With respect to "start at some point" you don't push a change of that magnitude through in an obscure bug report within a week and leave other broken like that. Listening to rumors, this has been discussed internally only for quite some time and apparently forgotten to notify the community reasonably in advance, even Thunderbird devs may not have been aware of that (at least no indication in the discussions on making Lightning part of the default TB releases).
rsx11m wrote:Well, what you'd usually do is to have at least a build-time switch for these things. Killing off an entire project like that just because Firefox doesn't like the mechanism it is using is just reckless...
i dont think it'll hurt TB38 but the next versions after tb38 it will. but they have to start doing this at some point in time. so they might as well do it now. sure its gonna upset some people but not all is lost IMO , but whether Fedora Maintainerss Hack out Lightning from 38 i dont know as someone has been Packaging that for a long time just like someone Packages ABP in Fedora also
True it doesn't affect TB38 ... directly. However it directly affects development and the developers, who are already stretched thin.
A few more releases of lead time would have been helpful. But it looks promising that we have an interim solution.
I just looked for "mail.biff.use_system_alert" in my Thunderbird 38.0b4, set it to false, sent myself a test email from one account, to the other account, and received a notification! I did not know that pref was there.
Now to do a reply and see if my primary account displays the notification.
Linux Desktop - AMD Athlon(tm) II X3 455 3.3GHz | 8.0GB RAM | GeForce GT 630 Windows Notebook - AMD A8 7410 2.2GHz | 6.0GB RAM | AMD Radeon R5
To clarify: The pref itself landed in time for 38.0b4, its default being set to "false" will happen with the next beta (if there is any) or the release next week (at least rkent promised that it will be merged into comm-esr38). Thus, Linux users should see the familiar XUL notifications when 31.6 updates to 38.0, without any further action needed.
mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same.
