In particular, the sage:// URIs cannot be referenced from content (running in the content process) because we don't register protocol handlers in content process.
Picking (navigating to) an RSS feed leads to "Address not understood" error. Cause: the protocol handler for sage schema is not found on the process that tries to load that URL.
There are APIs available today in Firefox to register a protocol handler in content processes and also to communicate between content and chrome process.
In particular, the sage:// URIs cannot be referenced from content (running in the content process) because we don't register protocol handlers in content process.
Picking (navigating to) an RSS feed leads to "Address not understood" error. Cause: the protocol handler for sage schema is not found on the process that tries to load that URL.
There are APIs available today in Firefox to register a protocol handler in content processes and also to communicate between content and chrome process.