petea / sage

A feed reader for Firefox.
http://sagerss.com
27 stars 8 forks source link

sage protocol is not registered #140

Open gialloporpora opened 8 years ago

gialloporpora commented 8 years ago

With the new version of Firefox Developer Edition (44.0) the content are not loaded because sage protocol is not registered.

This is the error message trying to open a feed from Sage sidebar:

Firefox doesn't know how to open this address, because one of the following protocols (sage) isn't associated with any program or is not allowed in this context.

Sage 1.5.4
Mozilla/5.0 (Windows NT 5.1; rv:44.0) Gecko/20100101 Firefox/44.0

Perhaps this happens still with the new Beta (43.0).

petea commented 8 years ago

FF 43.0 looks fine. I'm only seeing the problem in 44.0. It's either an FF bug or a problem with our nsIProtocolHandler implementation.

https://github.com/petea/sage/blob/master/src/components/sageProtocolHandler.js https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Reference/Interface/nsIProtocolHandler

gialloporpora commented 8 years ago

I confirm, now in 43.0 it looks fine, but I believe that the change could be landed in some future Beta1/Betan version of 43. branch. I have both FDE and Beta installed, if I note the problem in Beta channel I update the bug.

davidholtz commented 7 years ago

That time has arrived with the release of Firefox 48.0. screen shot 2016-08-15 at 9 01 56 pm

petea commented 7 years ago

I'm not seeing this on OS X or Windows. Can you provide steps to reproduce here?

petea commented 7 years ago

Related Get Satisfaction topic:

https://getsatisfaction.com/sagerss/topics/ever-since-installing-firefox-48-0-the-sage-protocol-ceases-to-work

davidholtz commented 7 years ago

Interesting. I have been using your fantastic add-on daily for years without a hitch and use Firefox as my default browser. Last night I updated from version 47 to version 48. After that, I receive the error above when attempting to access any of the feeds I have saved.

When I click on a feed's title in the sidebar, the url looks like this: sage://viewer/#feed/http%3A%2F%2Fwww.macrumors.com%2Fmacrumors.xml Does that URL look correct to you?

Also, could this be related to the inclusion of e10s / "Multiprocess Windows"?

petea commented 7 years ago

The URL looks right. Can you tell me what OS you're on?

davidholtz commented 7 years ago

My apologies. I am on OS X El Capitan 10.11.6

petea commented 7 years ago

Could you try creating a clean test profile, install Sage, and see if you get the same results?

https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

davidholtz commented 7 years ago

This did work for me. If you had to guess, do you think this is more likely related to a Firefox setting or conflict with an add-on? As far as I can tell, none of my add-ons have been updated for compatibility.

davidholtz commented 7 years ago

I've determined my issue. It's totally related to e10s, but only if you add the boolean "browser.tabs.remote.force-enable" and set it to true.

DanaMW commented 7 years ago

Build identifier: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:51.0) Gecko/20100101 Firefox/51.0 On this freshly installed Firefox Developers Edition setup Sage is broken, Firefox Version 51.0a2 Build ID 20161112004002

The address wasn’t understood

Firefox doesn’t know how to open this address, because one of the following protocols (sage) isn’t associated with any program or is not allowed in this context. - You might need to install other software to open this address

E10 is enabled.

Is there a development build of Sage that can be installed? I use sage a lot and I don't really want to replace it if that can be helped. Thank you, Dana