After I go thru the registration process, it says e-mail sent. Installation of the app goes flawlessly, but when I try to register an account, BIG FAIL. (I have no idea what ppl stuck in the Apple ecosystem would have to do.) I don't use Firefox, and the extension doesn't work on the Firefox derivative I use (Pale Moon), so I figure installing mydownloader on my phone isn't too bad. Only a terse explanation that we will either have to install a Firefox browser extension or use the Android mydownloader app. Or rather, mishandled.įirst, the system stops working without prior notice. What bugs me more about all this is the way it was handled. If you rather NOT to install the browser extension or Andriod app that is fine, just you wont be able to download or process decrypter tasks from any site that utilises didn't go out of our way to break it. Once again this is NOT our doing, just the framework/constraints that we have to work with. If you're using JD on localised system you do not need to setup My.JDownloader account (as mentioned in posts above), just the My.JDownloader browser extensionĮlse if you're using JD on a remote system you will need setup My.JDownloader with an account. Firefox or Chrome (or clones that support the same extensions) along with the My.JDownloader browser extension Moving forward the only working solutions are: This means my original 'proof of concept'/jd backend implementation (coalado did most of it) that supports ReCaptchav2, can no longer work. You can even port your Chrome extension to use WebExtension APIs just by loading the Chrome Web Store page of the extension in a Firefox instance with the Chrome Store Foxified addon.Didn't go out of our way to break it, Google changed default setting to no longer allow 'localhost' access. If you were relying on Chrome's command line option for loading an unpacked extension, check out the web-ext tool which automates temporary installation in Firefox for development. Submit your add-on to AMO for signing and distribution.If you have any problems, contact us on the dev-addons mailing list or #webextensions on IRC.Install your extension in Firefox and test it out.If you're using features or APIs that are not yet supported in Firefox, you may not be able to port your extension yet. Review your use of manifest.json features and WebExtension APIs against the Chrome incompatibilities reference.The process of porting an extension from Chrome or Opera is like this: Extensions written for these browsers will in most cases run in Firefox with just a few changes. Extensions developed with WebExtension APIs are designed for cross-browser compatibility: to a large extent the technology is compatible with the extension API supported by Google Chrome and Opera.
0 kommentar(er)
