Closed tbranyen closed 7 years ago
Currently I've come up with a very hacky method of returning which is effectively:
history.go(history.length-1);
Returning the user back to the furthest they've been in their history. This "should" work most of the time, since the extension is opened on a button press (making it first in the history). However, this means no data can be shared, so a successful transaction must always be inferred.
I've been able to share data via localStorage
. I think we can do some cleverness if the settings are set and we're on the homepage. If this happens we know the user just came from a payment gateway and we can use window.confirm
to figure out if it was successful or not. From there we can update the log automatically.
Firefox-specific support was dropped, can close out. Eventually they will support CRX files and this extension will "just work".
This bug tracks some of their intent: https://bugzilla.mozilla.org/show_bug.cgi?id=1260836, it's a bit hard to navigate their bugzilla, but internal sources have been pretty vocal about finding extension parity.
The redirection isn't working back to
resource://
protocol. This may be a limitation with Firefox.