Keep in mind the perspective of the people trying to ship Firefox:<p>* The bug does not break the vanilla (and therefore vast majority of userbase) firefox experience<p>* The bug is easily worked-around (as opposed to completely unfixable)<p>* The release candidates were already being built (which means you don&#x27;t want to make changes, because you have to rebuild+resend to manual QA+resign)<p>* The bug was merged in as part of a security fix which they can&#x27;t risk touching<p>They&#x27;re not necessarily out of touch. It could easily be that people who didn&#x27;t have all the details (e.g. release managers who didn&#x27;t realize the fix was re-adding a single trivial file) were worried about the risks of upsetting a security release.<p>Sometimes it takes time for the severity of a regression to work its way up to a decision maker. And in the end they did exactly the right thing, with 5 separate people all putting in work on a weekend to make it right.