We really should start making these posts more often, because phew there's a lot that happened in the last 8 months! There's so many improvements to Ruffle, that we really can't do it justice with an easy summary here. This blog post is going to be a little long, but the highlights are at the top!

As before, let's summarize with some fancy numbers first.

Since the last blog post (8 months ago)...

• ActionScript 3 Language has gone up from 75% to 90%!
• ActionScript 3 API has gone up from 68% to 76%!
• ActionScript 1/2 Language has remained at 95%. We're fairly sure we're feature complete, just some pesky bugs left!
• ActionScript 1/2 API has gone up from 75% to 78%!
• We've merged 933 pull requests from 53 people! (And 4 bots.)
• We've closed 1031 issues! (and some of them were real issues! Crazy!)
• We've added 435 new automated tests!

It's been a very busy 2023 for Ruffle, so much so that we didn't find the time to write a new progress report with everything going on! Let's fix that!

Let's summarize with some numbers first.

Since the last blog post...

• ActionScript 3 Language has gone up from 60% to 75%!
• ActionScript 3 API has gone up from 60% to 68%! (And it was only 25% at the start of the year!)
• We've merged 852 pull requests from 43 people! (And 3 bots.)
• We've closed 1,288 issues (and some of them weren't even duplicates or anything!)

We have some exciting Ruffle developments to share today!

On December 11th, 2022, our extension submissions to Firefox's extension repository, addons.mozilla.org (abbreviated as A.M.O), got stuck in review. This was shortly followed up with a far scarier notice a few days later on the 14th:

Ruffle will be disabled on addons.mozilla.org Due to issues discovered during the review process, one or more versions of your add-on Ruffle will be disabled on addons.mozilla.org in 14 day(s).

What followed was a list of every prior submitted version of Ruffle, and a statement requesting corresponding source code. Following this, Ruffle would be unavailable for Firefox users for two months, and we spent an additional month and a half improving our CI processes to support source code review requirements for Mozilla. This is now behind us, but it is important to know why it happened.

Get ready for the biggest Ruffle announcement yet! And the first one on the blog!