I knew that I'd have to/want to add other OAuth providers down the line, but in testing with friends it's been a much more frequent request than I thought. I am afraid that I've coupled tightly with Google Auth (thinking it was a Chrome Extension after all), but it should be doable with only minor re-work to the user flows (around the automatic login into the extension). I'll comment back here once I am underway. Luckily the approach I took involved backflips to avoid logging the user into Chrome, the side-effect of which may be that this may be slightly easier to do in the extension portion.
On the subject of WebExtensions, I was aware of them when I started, but the LML does rely a bit heavily on the Chrome APIs. I will take a look at the portability subject :).
Mozilla provides a nifty automated compatibility test as a first step to getting everything compatible. It threw a weird report when I submitted the extension (The "Report" section where errors should be is just blank), so I am reaching out to see if I can get a response before I dive deeper.
Hrm, looks like maybe the way manifests are generated differs between the two? That should only occur when it is running unpacked (ie when I am working on it locally). Thanks for bringing it to my attention, I should've thought to test that, I will upload a revision as soon as I have a chance to look into it.
I am working on getting this fixed, but I am blocked by AMO/Firefox Add-on Review. It looks like for listed extensions they disallow any remote scripts (I use apis.google.com for auth), so I may have to figure out an alternative distribution method once I get the fix for the localhost thing (which is just a difference in how the browser can be detected between chrome and FF).
Thanks for the thoughtful feedback!
I knew that I'd have to/want to add other OAuth providers down the line, but in testing with friends it's been a much more frequent request than I thought. I am afraid that I've coupled tightly with Google Auth (thinking it was a Chrome Extension after all), but it should be doable with only minor re-work to the user flows (around the automatic login into the extension). I'll comment back here once I am underway. Luckily the approach I took involved backflips to avoid logging the user into Chrome, the side-effect of which may be that this may be slightly easier to do in the extension portion.
On the subject of WebExtensions, I was aware of them when I started, but the LML does rely a bit heavily on the Chrome APIs. I will take a look at the portability subject :).
I’d be interested in Firefox support too.
Mozilla provides a nifty automated compatibility test as a first step to getting everything compatible. It threw a weird report when I submitted the extension (The "Report" section where errors should be is just blank), so I am reaching out to see if I can get a response before I dive deeper.
LinkMeLater is now available for Firefox on AMO at addons.mozilla.org/en-US/firefox/a...
Unfortunately doesn't seem to work - it loads a tab to localhost:5000, which doesn't seem to work.
Hrm, looks like maybe the way manifests are generated differs between the two? That should only occur when it is running unpacked (ie when I am working on it locally). Thanks for bringing it to my attention, I should've thought to test that, I will upload a revision as soon as I have a chance to look into it.
I am working on getting this fixed, but I am blocked by AMO/Firefox Add-on Review. It looks like for listed extensions they disallow any remote scripts (I use apis.google.com for auth), so I may have to figure out an alternative distribution method once I get the fix for the localhost thing (which is just a difference in how the browser can be detected between chrome and FF).
Happy to test but I avoid authorizing via Google. Email + pwd sign in please, if you get a chance.