- #Waterfox addons how to#
- #Waterfox addons update#
- #Waterfox addons archive#
- #Waterfox addons password#
Unfortunately, we don’t have the capacity to create and maintain an official repository.
#Waterfox addons archive#
Hi Peter, thanks for reaching out! Can you check to see if you received a reply to your email yesterday?Ĭould you at least archive the last version of legacy add-ons the way you archive older versions of Firefox so that people have a safe, official repository for these add-ons should we need them for an older machine we are trying to get running on a network? You do realize Firefox is the last and most recent web browser to support both Windows XP and Vista. Nothing here talks about account/developer support and this doesn’t mean signing up for yet another user account. Sorry to use your blog for a support request, but when I responded to an email it linked to.
#Waterfox addons password#
I tried to reset a password on my account and was told I don’t have one. I got an email saying I had an account and active add-on. I meant systemwide consistency across all browsers (since WE is pretty much Chromium Extensions API and there is polyfill allowing WE to run in Chromium)Īnd to be honest: I was being salty as both things are impossible in WEĪdditionally XUL exposed many nice interface components that are not available currently (maybe web components will change this some day…) Photon is terrible in terms of both usability and looksĢ. Examples using the context-fill and context-fill-opacity properties should be available, too.ġ. The site also provides a wealth of Photon-style SVG icons you can use, as well as instructions for making your own. I couldn’t answer your first question, but as for the second one, following the Photon design guidelines ( ) should be sufficient to making your extension blend in nicely with the Firefox UI.
#Waterfox addons how to#
Sure, where exactly can I find information how to properly implement mouse gestures and keyboard hotkeys? working on each and every possible page, working on userchrome, aware of context (executing different action if performed over website area, different over sidebar, different over tab bar etc.)?Īnd while we are at it: when can I find help in providing native user interface, using the same colors and shapes users know and feel confident with for interface elements? We encourage legacy add-on developers to visit our wiki for more information about upcoming development work and ways to get in touch with our team for help” “For more information about porting legacy extensions to the WebExtensions API is available on MDN. We encourage legacy add-on developers to visit our wiki for more information about upcoming development work and ways to get in touch with our team for help.Ĭategories: compatibility, developers, general, releases 82 responses
#Waterfox addons update#
Once a new version is submitted to AMO, users who have installed the legacy version will automatically receive the update and the add-on’s listing will appear in the gallery.įor more information about porting legacy extensions to the WebExtensions API is available on MDN.
Once this happens, users will no longer be able to find your extension on AMO.Īfter legacy add-ons are disabled, developers will still be able to port their extensions to the WebExtensions APIs. All legacy add-on versions will be disabled in early October, 2018. On September 6, 2018, submissions for new legacy add-on versions will be disabled. Mozilla will stop supporting Firefox Extended Support Release (ESR) 52, the final release that is compatible with legacy add-ons, on September 5, 2018.Īs no supported versions of Firefox will be compatible with legacy add-ons after this date, we will start the process of disabling legacy add-on versions on (AMO) in September.
0 kommentar(er)
