The Rumbling Edge

Something to ponder on, for all non-Firefox devs, by a Firefox dev:

"We certainly aren't going to block the Firefox release on an issue that doesn't affect Firefox. I don't think blocking 1.9- means we won't take a fix for other Gecko apps, which have their own release schedules."

A reply goes like:

"> I don't think blocking 1.9- means we won't take a fix

In this case, sure it does. Since it's minused, none of the people involved in causing this regression will work on it (as they've publicly said in other regressions they've caused). No one else knows the code involved. Once we ship Gecko 1.9 with this, we won't be able to change it on the branch because of compat issues (at least at that point I'd certainly avoid any changes to this on the branch). That's if we even remember this bug exists, since it got taken off all the tracking lists. And assuming anyone bothers to try to fix regressions on branch at all; given how 1.8 has worked, I wouldn't bet on it."

More info at an earlier thread by KaiRo on mozilla.dev.platform discussing the future of Gecko 1.9 for non-Firefox apps.

(I'm disabling comments here to avoid wars. Please air your thoughts at the follow-up thread on the newsgroup.)