Being annoyed at how Firefox has handled the introduction of add-on signing, this stuck out like a sore thumb:<p>&quot;&quot;&quot;
the problem was discovered, and filed as bug 1240559.
This was on January 18th, which is 8 days before the beta gets shipped to
release.<p>A workaround for add-on developers was posted in
<a href="https:&#x2F;&#x2F;bugzilla.mozilla.org&#x2F;show_bug.cgi?id=1240559#c10" rel="nofollow">https:&#x2F;&#x2F;bugzilla.mozilla.org&#x2F;show_bug.cgi?id=1240559#c10</a>, and the bug was
marked as a WONTFIX on the 21st.<p>On the 22nd, an add-on developer reopened the bug, saying that the
workaround wasn’t acceptable, as they wouldn’t have time to fix their
add-on and get it approved before 44 went out the door.<p>A patch was written, and then the decision was made to land the fix
directly onto release. The add-on author confirmed the fix, and the bug was
closed out. This is what we ended up shipping.
&quot;&quot;&quot;<p>The add-on developer in question who got this reopened, Ben Bucksch, got it absolutely right:<p>&quot;&quot;&quot;
This is a major goof for ext compat. You goofed, you&#x27;ll have to fix it. You can&#x27;t leave the dirt on our carpet.
You can&#x27;t just remove APIs without warning and then say &quot;sorry&quot;.<p>This is a must fix. And even if FF4 were to be released tomorrow, you should still be glad to have found it before it hits end users.<p>&gt; No, there isn&#x27;t anything left to do.<p>NewTabURL.jsm was accidentally removed. There&#x27;s a trivial fix: Re-add the file.
&quot;&quot;&quot;<p>Mozilla devs appear to be completely out of touch with what their core goal should be: a stable open-source browser with an awesome add-on community. Instead the Process is holy and cannot be altered. In the process they&#x27;re alienating add-on devs, people who make their product more awesome <i>for free</i>. Come on, guys, who gives a shit about whether about:newtab is remotely hosted?