On 3/9/2015 8:47 PM, Emanuel Hoogeveen wrote:
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-
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
And I’d like to thank you guys for updating the relevant pages on MDN as part
of your project. This is a big help for not just the writing team but all of
Mozilla.
Eric Shepherd
Senior Technical Writer
Mozilla
https://developer.mozilla.org/
Blog: http://www.bitstampede.com/
Twitter: http://tw
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 con
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
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, R
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 w
7 matches
Mail list logo
