3 ms·
As a FF user, yay! However, I am a tad confused if the comparison is indeed apples-to-apples. E.g is chrome and firefox app team running similar suite of tests?
by ahurmazda 6y ago
As a FF user, yay! However, I am a tad confused if the comparison is indeed apples-to-apples. E.g is chrome and firefox app team running similar suite of tests? What if firefox app team only checks for typos in the title (contrived). Of course it feels good to get an immediate approval.
In any case, the process (both Chrome/FF) should be as transparent as possible so a dev knows what they are dealing with. I can't imagine the frustration to have to deal with unhelpful automated responses.
- DanielDe 6y agoYep, this is a great point. But as you say, it's hard to know if Chrome is actually doing anything substantively better or not since I don't actually know what they're doing. And from what I've observed through this process it seems like whatever they're doing isn't consistent. For what it's worth, Firefox asks for an unminified source bundle during the submission process (including for all updates), and Chrome does not. This doesn't mean that anyone over at Mozilla is actually looking through that source, but it's an interesting difference.