I’m developing an extension for my ibgib protocol that wraps an Ionic/Angular app. Because the protocol is meant to be a relatively thin layer of DLT for distributed computation, I’m also trying to leverage the pretty amazing Mozilla synergy in web-ext to target ff desktop, ff android and chrome. All of these targets work well when triggered via the browser action button (ok the ff android is a little slow). When clicking the browser action button, it opens up the Angular app’s ‘index.html’ in a new tab and the Angular router knows how to route the empty route to something like
moz-extension://[123-extension-hash-456]/ibgib/tag%20home%5E...[DLT hash content address]
An actual example would be:
If I duplicate this tab, it will fail to load in all targets (ff desktop, ff android, chrome). I figure this has something to do with sandboxing extensions and it may not be possible, but I would really love to be able to coax the routing to work via the deep linking. (It’s a primary benefit of the protocol with content addressing.)
Does anyone know of how to properly route the incoming URL, or if this is even possible to access outside of the browser action button? Is this only an artifact of using the self-signed developer certificates, and would it magically route properly with a proper cert?