Closed Bug 1330100 Opened 3 years ago Closed 3 years ago
Bar from Chrome
The Moz bar extension on Chrome has 330,000+ installs. We'd like to port it to Firefox to capture some goodwill and users from this savvy, influential segment. I followed the "examine chrome extension" howto, which found no blocking issues. But when I ran the code I got a handful of errors. Looks like the most blocky of the blockers is "TypeError: chrome.storage.sync is undefined". When bug 1220494 is resolved I will try again and, if all looks good, reach out to the company to see if they would consider porting or maintaining/promoting a gifted port.  https://moz.com/products/pro/seo-toolbar  https://github.com/andymckay/examine-chrome-extensions  https://pastebin.mozilla.org/8961227
From the content of this thread it looks like Moz would love to have this addon working (and lots of their users, too). Just dropping this here to remind myself (or whoever) to follow up on this thread when the blocker drops: https://moz.com/community/q/mozbar-login-change-update-firefox-temporarily-disabled
FYI, you can run chrome.storage.sync on nightly if you'd like to give it a try: https://mail.mozilla.org/pipermail/dev-addons/2016-November/002125.html
Component: WebExtensions: Untriaged → WebExtensions: Compatibility
hey, any updates on Mozbar for Mozilla? using only Mozilla when promoting http://essay.expert/ and need this addon. At the moment am using SEO Quake but it just a temporary solution. would love this bug to be fixed as soon as possible
Closing based on the lack of blocking bugs. (In reply to Lexie Kings from comment #3) > hey, any updates on Mozbar for Mozilla? using only Mozilla when promoting > http://essay.expert/ and need this addon. At the moment am using SEO Quake > but it just a temporary solution. would love this bug to be fixed as soon as > possible We think it should work and its up to the add-on author to update their add-on, so please contact them.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.