3 ms·

Yes for awesome, and the new Web Extension API which now breaks things will make cross-browser browser extension development possible (as far as I have read!).

by kreetx 9y ago

Yes for awesome, and the new Web Extension API which now breaks things will make cross-browser browser extension development possible (as far as I have read!). I can very well live in default-land for a couple of weeks for that. Also, this extension-breakage taking place right now seems to be mostly the extension developers' fault, since they've known well in advance that this is coming. (Not judging, just saying -- many/most extensions are probably hobby projects, and porting them appears to take a non-trivial effort.) EDIT: removed a word from a wrong place :) Definitely not a spelling mistake, not wording either, hmm, what should I write here.

awirth 9y ago
I have a small extension (~100 users) that I forgot to upgrade until 57 landed and broke it. I hastily threw together a WebExt version and pushed on Wednesday night, but forgot to set the strict_min_version flag correctly (which was, unfortunately, Firefox 57). The new version worked fine for people on 57, but for anyone that was on ESR or a slightly out-of-date version of firefox and updated they got a broken WebExtension that I couldn't push another update to to fix it - Firefox doesn't let you "downgrade" from a WebExtension to a native extension. Thankfully a user emailed me about it and I had it fixed in less than 48 hours, but it was still a mess. All I could do was add a note to the addon description and disable the bad versions and anyone that got broke had to manually downgrade. The new Webextensions are nice, but it was definitely easy to shoot yourself in the foot with the transition. I know that NoScript also needs the same API that I was using (the ability to inspect response bodies), FWIW. The extension is https://addons.mozilla.org/en-US/firefox/addon/gpsdetect/ https://addons.mozilla.org/en-US/firefox/addon/gpsdetect/ for those curious EDIT: brevity

by kreetx 9y ago

awirth 9y ago

I have a small extension (~100 users) that I forgot to upgrade until 57 landed and broke it. I hastily threw together a WebExt version and pushed on Wednesday night, but forgot to set the strict_min_version flag correctly (which was, unfortunately, Firefox 57). The new version worked fine for people on 57, but for anyone that was on ESR or a slightly out-of-date version of firefox and updated they got a broken WebExtension that I couldn't push another update to to fix it - Firefox doesn't let you "downgrade" from a WebExtension to a native extension. Thankfully a user emailed me about it and I had it fixed in less than 48 hours, but it was still a mess. All I could do was add a note to the addon description and disable the bad versions and anyone that got broke had to manually downgrade. The new Webextensions are nice, but it was definitely easy to shoot yourself in the foot with the transition. I know that NoScript also needs the same API that I was using (the ability to inspect response bodies), FWIW. The extension is https://addons.mozilla.org/en-US/firefox/addon/gpsdetect/ https://addons.mozilla.org/en-US/firefox/addon/gpsdetect/ for those curious EDIT: brevity