Porting a firefox add-on to a Chrome extension

3,568 views
Skip to first unread message

Jan Schnitzler

unread,
Mar 1, 2012, 9:32:05 AM3/1/12
to Chromium-extensions
Hi there,

I know this question must have been asked thousands of times... But I
cannot find an answer anywhere.

Is there some reasonable estimate on how complicated it is to port a
Firefox add-on to a Chrome extension?

The add-on is a password-reminder using images (https://
addons.mozilla.org/de/firefox/addon/picpasso/). One main part of the
code deals with the recognition of the password-fields on the pages.
When the user clicks on the field, a pop-up opens. Is this possible in
Chrome (maybe using a content script)? Most of the rest is JavaScript
and SQLite.

Best regards,
Jan

John J Barton

unread,
Mar 1, 2012, 12:06:17 PM3/1/12
to Jan Schnitzler, Chromium-extensions
I have experience with writing both Firefox and Chrome extensions. Any
part of your code that touches the browser API is a complete re-write.
Extension UI code in XUL should be partly portable to HTML and more
easily backportable to jetpack. You will probably have to divide your
code differently because the process model in the two browsers is
quite different.

My suggestion is that you approach the project as a start-over, then
be pleasantly surprised if you can re-use.

jjb

> --
> You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
> To post to this group, send email to chromium-...@chromium.org.
> To unsubscribe from this group, send email to chromium-extens...@chromium.org.
> For more options, visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/?hl=en.
>

Jan Schnitzler

unread,
Mar 1, 2012, 3:14:31 PM3/1/12
to Chromium-extensions
Thanks a lot. Guess it will be more work than I expected...
> > To post to this group, send email to chromium-extensi...@chromium.org.
> > To unsubscribe from this group, send email to chromium-extensions+unsubscr...@chromium.org.

Jordan Rushing

unread,
Nov 14, 2014, 12:50:56 PM11/14/14
to chromium-...@chromium.org, ogo...@googlemail.com
I actually took this approach going from my Chrome Ext to a new Firefox Add-On. Surprisingly was able to make the code cleaner and more concise. So now I can go back to the Chrome version and clean it up and optimize it further. Going to take this same exact approach with going to Safari as well. 
It may seem like extra work, and it is. But in the long run can be very beneficial.

Thanks,
Jordan Rushing
Co-Founder PatentMonk.com
Reply all
Reply to author
Forward
0 new messages