3 ms·
I maintained a browser extension tha works on Chrome and Firefox, and it depends on a third party project that uses Angular 1.x. Publishing the extension on Chr
by maple3142 6y ago
I maintained a browser extension tha works on Chrome and Firefox, and it depends on a third party project that uses Angular 1.x. Publishing the extension on Chrome Store is easy, whereas Firefox's reviewer requires that only the latest version of Angular 1.x can be used. The third party project that I depend on uses a older version of Angular 1.x, and the author refused to update it. So it forced me to fork the project to update Angular. Although I think this reviewing process is better to user, but as a developer, it is more annoying to deal with.
- DanielDe 6y agoThis is really interesting, and I appreciate the opposing argument! I wasn't aware that Mozilla checked for stuff like this.
- franga2000 6y agoYeah, it's very strict, but at the same time, I've never seen any "Mozilla killed my extension without explanation" rants, which seem to be very common with Google.
- toyg 6y agoAt least you were told why it was rejected. That’s often not the case on Chrome.