Re: Mozillabuild 2.0 ready for testing

Hi Ryan, good news. One thing that's a bit unfortunate from the l10n perspective is the svn drop. SVN is still used quite frequently to host the website localizations, so keeping that in would be helpful. Axel, who should probably give this a test run in reals on his VM. On 3/9/15 2:44 AM,

Re: Intent to Ship: Fetch API

Removed pref on m-c. This will ship in 39 except for cache mode and authentication prompt. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: Intent to deprecate: persistent permissions over HTTP

FWIW I am for the original set of HTTPS only restrictions proposed by Anne. I think doing so sends a strong security minded message, even if some think too strong. Pop-ups: I realize including pop-ups in this is a minority opinion (judging by this thread), however, I have not seen a single

Re: Mozillabuild 2.0 ready for testing

Nice, I like the new terminal. When I try to run |./mach mercurial-setup| from m-c tip, it gives me the following error after pressing enter: WindowsError: [Error 193] %1 is not a valid Win32 application File c:\Users\Emanuel\firefox\mozilla-central\tools/mercurial/mach_commands.py, line

Re: Intent to deprecate: persistent permissions over HTTP

Thanks everyone for weighing in. It sounds like we don't want to touch popups :-) And yes, negative persistence (never allow) should remain available. The Notifications API is a bit in flux and the most interesting notifications require service workers so are already restricted. I guess I'm okay