I don't know what happened, but after downgrading to the stable version, I updated to this one again, and after restarting FF (which I also did on the previous attempt) it's visible now.
Although it appears in Firefox, I can't enable it after disabling, even after removing and reinstalling the package. Can you check if you can enable it, even after disabling?
I found that the only way to reenable HTTPS Everywhere while using 5.1.1-1.fc22 is to downgrade to 4.0.3-1.fc22, then enable, then update back to 5.1.1-1.fc22. Not ideal, but at least it's working again.
To clarify, I'm talking about disabling by selecting "Disable HTTPS Everywhere" after clicking on the HTTPS Everywhere icon. Clicking on Disable/Enable under Add-ons/Extensions doesn't seem to have the same effect.
It got auto-pushed to stable, and I'm not going to bother trying to replace it. Because it at least does its job now. I don't think it a good idea to try to replace a partially-functioning build with a non-functioning one while working on a fully-functioning build.
Regarding your bug, I can reproduce the behavior. However, I am able to fix it via about:config.
The bug does not exist on Windows. It does exist on a fresh profile in SeaMonkey on Fedora 22. Can you check for me whether it works properly in Firefox with a fresh profile?
The bug also exists in Firefox with a fresh profile (I also responded in your bug). Setting my karma back to +1 since this version is still better than 5.1.0.
This update has been submitted for testing by niveusluna.
Sorry, this one doesn't appear either.
I don't know what happened, but after downgrading to the stable version, I updated to this one again, and after restarting FF (which I also did on the previous attempt) it's visible now.
Although it appears in Firefox, I can't enable it after disabling, even after removing and reinstalling the package. Can you check if you can enable it, even after disabling?
This update has been pushed to testing.
This update has been submitted for stable by bodhi.
Taskotron: upgradepath test FAILED on noarch. Result log: https://taskotron.fedoraproject.org/resultsdb/results/3458524 (results are informative only)
I found that the only way to reenable HTTPS Everywhere while using 5.1.1-1.fc22 is to downgrade to 4.0.3-1.fc22, then enable, then update back to 5.1.1-1.fc22. Not ideal, but at least it's working again.
To clarify, I'm talking about disabling by selecting "Disable HTTPS Everywhere" after clicking on the HTTPS Everywhere icon. Clicking on Disable/Enable under Add-ons/Extensions doesn't seem to have the same effect.
This update has been pushed to stable.
It got auto-pushed to stable, and I'm not going to bother trying to replace it. Because it at least does its job now. I don't think it a good idea to try to replace a partially-functioning build with a non-functioning one while working on a fully-functioning build.
Regarding your bug, I can reproduce the behavior. However, I am able to fix it via about:config.
The bug does not exist on Windows. It does exist on a fresh profile in SeaMonkey on Fedora 22. Can you check for me whether it works properly in Firefox with a fresh profile?
bugzilla link: https://bugzilla.redhat.com/show_bug.cgi?id=1261182
The bug also exists in Firefox with a fresh profile (I also responded in your bug). Setting my karma back to +1 since this version is still better than 5.1.0.