[desktop] Bugs logged by Desktop Release QA in the last 7 days

Hello, Here's the list of new issues found and filed by the Desktop Release QA team in the last 7 days. Additional details on the team's priorities last week, as well as the plans for the current week are available at: https://tinyurl.com/wjbzdf2. Bugs logged by Desktop Release QA in the last

Soft code freeze for Firefox 75 starts March 5

Hi all, With Firefox 74 RC shipping today, we are nearing the end of the Nightly 75 cycle. In order to avoid invalidating the testing we get out of late Nightly and to ensure that we can roll out Beta 75 to a wider audience with confidence, we'd like to ask that any risky changes be avoided from

Intent to ship: Web Animations implicit to/from keyframes and auto-removing redundant filling animations

Hi, As of some time next week (week of Mar 2) I intend to turn on the following two Web Animations API features by default for release channels: * Implicit to/from keyframes (e.g. elem.animate({ opacity: 0 }, 500) to fade out an element). * Automatically removing filling animations that have been

Deprecation of NS_NewNamedThread

*tl;dr: To create new one-off threads using NS_NewNamedThread, you need to add them to an allowlist. Lots of cases of async work can be done on the background thread pool.* In order to improve our overall threading picture, we're working on reducing the number of one-off threads spun up in Firefox

Security Severity Changes

Hi all, In Berlin we realized that our Bug Severity page is confusing and that sec-critical and sec-high don't have a good distinction. We endeavoured to fix this, and think we have. We have: 1) Split the Web and Client Severity page into separate pages. (And updated them.) 2) Clarified the defi

Intent to ship: Web Animations Animation timelines (without the setter of Animation.timeline)

Hi, We intend to turn on the preference of the Animation timelines this week. * dom.animations-api.timelines.enabled This preference enables Animation.timeline getter, Document.timeline, and DocumentTimeline and AnimationTimeline interfaces. This feature has been implemented in WebKit and Blink

Re: Deprecation of NS_NewNamedThread

Kris, others working on this, On Mon, Mar 2, 2020 at 6:51 AM Kris Wright wrote: > *tl;dr: To create new one-off threads using NS_NewNamedThread, you need to > add them to an allowlist. Lots of cases of async work can be done on the > background thread pool.* > I've been watching this progress

Re: Deprecation of NS_NewNamedThread

That's cool! I wonder if there is (or will be) a way to somehow preserve the naming part of NS_NewNamedThread, which is sometimes precious for debugging, i.e. somehow attach to the background thread a debugging information in addition to the stack that would let us analyze what the thread was atte