Yeah, if this was some bug that had been languishing for years without anyone caring to look at it, I'd consider this a stain on Firefox's reputation. But that

Yeah, if this was some bug that had been languishing for years without anyone caring to look at it, I'd consider this a stain on Firefox's reputation. But that's not what's happening: it's a bug that manifests in what probably looks to the user like a simple way, but tracking down the problem and fixing it is not simple at all. People are working on it, and it looks like it'll be fixed in a public release before too long. Agree: this is the process working.