It's time to port your extension to Firefox

I wish more people would talk about the goods of Firefox!!!<p>It&#x27;s becoming so un-loved and so neglected by users (and specially developers!) this days that I fear that tomorrow there won&#x27;t be an alternative to chrome at all :(.<p>Those who lived the Internet Explorer 6 should be the ones to rise up first.<p>But everyone seems to have forget how bad it was and how hard it was to destroy that monopoly.<p>Developers should be the first to rise for Mozilla.<p>I think we own Firefox the good things we still have on the web. They fought for standards, for example...<p>Please, create a movement or something... Make noise... But don&#x27;t neglect Firefox.<p>We need alternatives and we all are responsible for allowing projects like Firefox to exist (by using them)...<p>It&#x27;s very sad to be ungrateful!!!<p>Everyone should take clues on the post from the OP...

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&#x27;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.

I must be in the minority, but I stopped using browser extensions many years ago. The amount of security and privacy issues of allowing 3rd party software to run on pages I visit makes me shudder. It&#x27;s difficult enough to stop the pages themselves, their analytics and ad partners from tracking me and leaking my data, I don&#x27;t want to voluntarily add to this problem.<p>The only extensions I would need are for ad blocking, which is solved with a DNS blocker on my router, avoiding the need to set it up on all my devices separately, and a password manager, which I find I don&#x27;t actually need since copy&#x2F;pasting from a terminal with pass works well enough. So now all my browsers run as vanilla as possible, with maybe a built-in dark theme.<p>In this specific case Keysmith can record any input <i>on any page</i> and play it back. While the functionality is undoubtedly useful, the keylogger aspect sounds like a huge privacy risk. Their privacy policy[1] &quot;promises&quot; they will never collect or sell any sensitive data, but frankly why should I trust it or trust that it won&#x27;t change without my knowledge? Especially with a proprietary app I can&#x27;t inspect the source code of.<p>The Chrome Web Store submission process sounds like a nightmare, but I&#x27;m more concerned that such an invasive extension was ultimately allowed on both platforms, and that it was approved on Firefox in just 24h.<p>[1]: <a href="https:&#x2F;&#x2F;www.keysmith.app&#x2F;privacy-policy" rel="nofollow">https:&#x2F;&#x2F;www.keysmith.app&#x2F;privacy-policy</a>

&gt; [Google] had rejected our extension 6 times with no detail because of a technicality.<p>Sounds like a good company to do business with.

Wow, I didn&#x27;t know that porting to FF was so easy. Good to know!

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.<p>In any case, the process (both Chrome&#x2F;FF) should be as transparent as possible so a dev knows what they are dealing with. I can&#x27;t imagine the frustration to have to deal with unhelpful automated responses.

It&#x27;s not clear which version of the extension was initially submitted for Firefox approval: the one with the redundant permission or the one without. If the latter, even though I&#x27;m inclined to believe Mozilla probably do have a more developer-friendly process in place, it&#x27;s not really a fair comparison.<p>&gt; So we created a Firefox developer account, submitted our extension, and girded ourselves for another rough ride.<p>Again, if the permissions had been fixed by this point, and Google had accepted it, why would you assume a rough ride from Mozilla?

I am personally using a lots of browser extensions because of my dev job. I have switched some years ago to Chrome when it was faster than Firefox for a short moment. Now i consider going back because Chrome eats so much RAM there is little left for node.js and vscode. Even more with every extension installed. I had to disable bunch of these for that reason.<p>I know it is off topic. However, can anyone share info if Firefox is better at this point considering memory usage?

I can only wonder if the experience has been similar for Brook Hong, the developer of Surfingkeys[0], which is the only extension I&#x27;ve experience with that works on both Firefox and Chrome.<p>[0] <a href="https:&#x2F;&#x2F;github.com&#x2F;brookhong&#x2F;Surfingkeys" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;brookhong&#x2F;Surfingkeys</a>

Wait, so the reason why google is evil in this case is because the extension was requesting multiple overlapping permissions, some of which were subsets of others?

Firefox is a dead browser. #ChangeMyMind