blog.mozilla.org | 504: Gateway time-out
blog.mozilla.org

Quotes from the blog post:

We’re taking a steady approach to opening up the mobile extension ecosystem to ensure Firefox for Android maintains strong performance standards while a vast new array of extensions are utilized for the first time in a mobile environment. If testing continues to progress well, we anticipate unveiling a fully open Firefox for Android extension ecosystem sometime in December.

We anticipate strong interest from users excited to explore all the new ways they can customize Firefox for Android. Current trends indicate we’ll have at least 200+ new Firefox for Android extensions on AMO when open availability debuts in December. And while a couple hundred extensions is more variety than you’ll find on any other mobile browser, it is significantly fewer than the nearly 40,000 desktop Firefox extensions on AMO. So the opportunity for heightened discoverability with new users may be intriguing to some developers.

  • Midnitte@kbin.social
    5·
    1 year ago

    Agreed. Although there is a bug where the current tab won’t respond to any input (such as refreshing or new url entry) and you need to close the tab… it hasn’t yet been annoying enough to open a new issue though…

    • MrFlamey@lemmy.worldEnglish
      1·
      1 year ago

      I uninstalled it because of this bug. Just kept occurring again and again on two separate phones to the point it was totally useless. I hope they fix it.

      • Midnitte@kbin.social
        1·
        1 year ago

        I submitted a bug report about it, but I was never able to reproduce it reliably - seemed like it was due to leaving the tab around for a long time.

        If it happened that frequently, I would definitely see if you can reproduce it while recording logs so it can help them track it down!