The best I can think of is that the explainer language used to justify the extension’s removal was just boilerplate language that got copy+pasted here because someone clicked the wrong button. But even that makes a mockery of the review process.
I think “oops clicked wrong button” would be slightly more defensible, but not by much. If they truly rejected the extension for content in it that it does not have, it’s hard to see how a human could make that mistake even accidentally. But maybe there’s something I’m missing.
Correct, this two-sided discourse is due to a massive lack of communication on Mozilla’s part, leaving room for speculation.
The best I can think of is that the explainer language used to justify the extension’s removal was just boilerplate language that got copy+pasted here because someone clicked the wrong button. But even that makes a mockery of the review process.
I think “oops clicked wrong button” would be slightly more defensible, but not by much. If they truly rejected the extension for content in it that it does not have, it’s hard to see how a human could make that mistake even accidentally. But maybe there’s something I’m missing.