Understanding Performance Impact in Firefox and Native Messaging Support
-
Understanding Performance Impact – Mozilla Performance
A few years ago, a small group of engineers at Mozilla introduced a process to identify the tasks that would have the greatest impact on the performance of Firefox. They would gather each week to look over user submitted profiles, and discuss bugs reports. Each bug would then be assigned a category and a score to reflect its impact on performance. This would help teams to prioritise their work for performance, and proved crucial in delivering the significant speed improvements that were present in Firefox Quantum.
Fast forward to today, and this performance triage process has continued, but you’d be forgiven for not knowing about it. This year we have been making improvements to the way bugs are nominated for triage, how the impact and keywords are determined, and getting more people involved. I’d like to share some of these changes with you, starting with how to request a performance impact review for a bug.
-
Native Messaging Support Arrives in Stable Version of Firefox Snap - OMG! Ubuntu!
Satisfied users of the Firefox Snap on Ubuntu — hey, if Big Foot can exist, so can they — will be stoked to hear they can FINALLY take advantage of native messaging support without needing to get dicey with dev builds.
Got a sense of deja vu?
Back in July I reported that the Firefox Snap finally “fixed” its extant ability to use this feature, but at the time it was limited to beta builds of the browser (thus meaning users who wanted it us either had to switch Snap channel to enjoy.
However, as of early November the relevant bits and pieces that make it all work HAVE made their way in to stable builds, meaning all users of the Firefox Snap, regardless of channel, benefit.