Closed Bug 1395440 Opened 6 years ago Closed 6 years ago
Xmarks Sync migrating to webextension APIs
(Firefox :: Extension Compatibility, enhancement, P4)
(Reporter: shell, Unassigned)
(Whiteboard: [awe:firstname.lastname@example.org], triaged)
Xmarks Sync has a Chrome version. After reaching out to their support team they said they would let the dev team know about the 57 Release deadline for migrating. This is a candidate if there isn't a webextension version by Firefox 57 to have an alternative(s) suggested, until migrated. Alternatives are 100% for the user experience. After they migrate if a user needs an add-on that didn't migrate, they can find one to meet their need. As soon as an add-on has a webextension version update, the add-on will be updated and re-enabled for the user. Alternative suggestions go away automatically (since there is no UX for alternatives for enabled add-ons).
6 years ago
The version on AMO is now a WebExtension, closing.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
I think it should be re-opened . The xmarks web-extension version 188.8.131.52 that was posted on AMO was removed , but was totally buggy and didn't work at all (according to comments on AMO, and my own experience) and the version reverted back to 4.4.1 which is not a web-extension. Also, the current beta on AMO (184.108.40.206a) does not work for me .
You need to log in before you can comment on or make changes to this bug.