3 ms·

I understand why FF is moving this direction, and I actually think they should. But they should have a plan of action for people who want extensions's that flat

I understand why FF is moving this direction, and I actually think they should. But they should have a plan of action for people who want extensions's that flat-out won't work with the new system. By just telling people "lol no", they are really going to get some backlash, and Mozilla absolutely deserves it. It's frustrating to see the only browser that cares throwing their user's concerns to the wind like that.

ohthehugemanate 9y ago
That's what we've all been using for the last year. Legacy extensions were marked as "legacy," and no one cared. They're tagged as "deprecated", and "incompatible with Firefox <57", and still no one cares. Developers are only now switching because the deadline is fast approaching. That's just human nature, unfortunately. Though I kind of wish Mozilla had gone all the way to labeling them "for fucks sake stahp"
- CaptSpify 9y ago
  But from what I've read, that's not the case. There are some extensions that can't be upgraded, like vimperator. I'd love to be wrong on that though
kuschku 9y ago
They continue to work in Developer Mode, just FYI.
- CaptSpify 9y ago
  But isn't that going away eventually? > We will continue to honor this preference in Nightly builds and in unbranded builds, but when 57 (and later versions) go to beta and eventually to release, that preference will be ignored. Unless I'm mis-understanding that? Additionally, aren't they are removing access to a lot of the internals even for legacy addons as well?
  - yoasif_ 9y ago
    Possibly a slight misunderstanding. Nightly and unbranded builds will always respect that preference. Stable versions, starting with 57 will ignore it.
    - CaptSpify 9y ago
      Then maybe I'm missing something. I've set here: extensions.allow-non-mpc-extensions to true as per https://wiki.mozilla.org/Add-ons/ShimsNightly https://wiki.mozilla.org/Add-ons/ShimsNightly But when I go to https://addons.mozilla.org/en-US/firefox/addon/vimperator/ https://addons.mozilla.org/en-US/firefox/addon/vimperator/, It wont let me install and it says "This add-on is not compatible with your version of Firefox" Edit: Disabling JS allowed me to download it. It's not working yet, but I haven't had time to troubleshoot.

ohthehugemanate 9y ago

That's what we've all been using for the last year. Legacy extensions were marked as "legacy," and no one cared. They're tagged as "deprecated", and "incompatible with Firefox <57", and still no one cares. Developers are only now switching because the deadline is fast approaching. That's just human nature, unfortunately. Though I kind of wish Mozilla had gone all the way to labeling them "for fucks sake stahp"

CaptSpify 9y ago
But from what I've read, that's not the case. There are some extensions that can't be upgraded, like vimperator. I'd love to be wrong on that though

kuschku 9y ago

They continue to work in Developer Mode, just FYI.

CaptSpify 9y ago
But isn't that going away eventually? > We will continue to honor this preference in Nightly builds and in unbranded builds, but when 57 (and later versions) go to beta and eventually to release, that preference will be ignored. Unless I'm mis-understanding that? Additionally, aren't they are removing access to a lot of the internals even for legacy addons as well?
- yoasif_ 9y ago
  Possibly a slight misunderstanding. Nightly and unbranded builds will always respect that preference. Stable versions, starting with 57 will ignore it.
  - CaptSpify 9y ago
    Then maybe I'm missing something. I've set here: extensions.allow-non-mpc-extensions to true as per https://wiki.mozilla.org/Add-ons/ShimsNightly https://wiki.mozilla.org/Add-ons/ShimsNightly But when I go to https://addons.mozilla.org/en-US/firefox/addon/vimperator/ https://addons.mozilla.org/en-US/firefox/addon/vimperator/, It wont let me install and it says "This add-on is not compatible with your version of Firefox" Edit: Disabling JS allowed me to download it. It's not working yet, but I haven't had time to troubleshoot.