Firefox 52 breaks Libx

[Peter Tagtmeyer]

What to do?

Peter

Peter Tagtmeyer
Science Librarian
Colgate University
ptagt...@colgate.edu
315-228-7402

[kel...@g.harvard.edu]

Confirmed for us as well. 

Last time this happened (January 2016), it was because Mozilla started requiring add-ons to be signed starting in Firefox v43 (https://support.mozilla.org/t5/Problems-with-add-ons-plugins-or/Add-on-signing-in-Firefox/ta-p/30262). However, this doesn't seem to be the problem now, since Firefox is allowing the add-on to be installed and not giving a "could not be verified for use in Firefox and has been disabled" error. I've emailed LibX to report the issue.

Emily

Emily Kelly

Production Systems Librarian

Library Technology Services

Harvard University

617-495-3724

emily...@harvard.edu

[Godmar Back]

We'll try to take a look.

Neel Arora is currently working for us to freshen up the LibX codebase. Our goal is to drastically reduce it to bring it back to a more maintainable state.

As part of this effort, we are hoping to dump the Firefox XUL code and replace it with WebExtensions. He's had some initial success.

As another part of this effort, we are hoping to replace the current libapp framework with a leaner framework in which LibX modules use Promises, which are statically combined via webpack into one large content script (which is then centrally updated).

 - Godmar

[Peter Tagtmeyer]

Thank you and your team very much for the update and the sustained effort.

For me this is an invaluable tool.

Best,

Peter

Peter Tagtmeyer
Science Librarian
Colgate University
ptagt...@colgate.edu
315-228-7402

[Darcy Duke]

Yes, this was reported to us by a user here at MIT as well. A lot of our users love this tool so I would love to be able to support it better. Godmar, I can't promise anything but is there anything we can do to help you support this tool? Happy to chat offline...

Darcy Duke

Head, UX and Web Services

MIT Libraries

da...@mit.edu | 617.253.9370

[Kelly, Emily]

Hello all,

Does anyone know if there's any investigation yet on the Firefox 52 issue, or even a timeline for when someone may be able to look at it? We have more and more users upgrading to v52 and discovering LibX no longer works.

Thanks,

Emily

[Godmar Back]

We put a new version at http://libx.org/releases/

I don't believe, however, that auto-update will work. Users will have to reinstall libx from the link above.

Auto-update doesn't work because, basically, we couldn't find information anymore about how to sign our update.rdf under the current AMO signing regime :-(

 - Godmar

[kel...@g.harvard.edu]

Thank you so much! I've tested and confirmed that it's working on my Firefox 52 (Mac). Thanks for the heads up about the need to manually reinstall LibX.

Emily