On 2/10/2014, 9:39 AM, Chris Mills wrote:
Hi all,
Could I get someone to do me a quick technical review on the following article
set?
https://developer.mozilla.org/en-US/Firefox_OS/Security/Debugging_and_security_testing
Particularly the following section needs some details added, as it’s still TBD.
https://developer.mozilla.org/en-US/Firefox_OS/Security/Testing_in_a_privileged_context#Windows
They are not very long, so looking through should be pretty quick.
Many thanks in advance!
Chris Mills
Senior tech writer || Mozilla
developer.mozilla.org || MDN
[email protected] || @chrisdavidmills
At the time of reading this, the "flavor of nightly build (Linux, Mac
OS, Windows)" limk pointed to
http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-b2g18/
which may not be what you want for *nightlies*. That would be
ftp://ftp.mozilla.org/pub/b2g/nightly/latest-mozilla-central/.
And to be pedantic, "Marionette: A JavaScript debugging shell for
Firefox OS" is inaccurate. Marionette is an automation driver, allowing
you access to automate actions in chrome and content and to inject
javascript. The shell you're using is built on top of marionette. I'd
rewrite that as "Getting a debugging shell for Firefox OS", then
continue to describe the process of setting up the shell.
I'd also change "Marionette is based on the Selenium/WebDriver API, and
provides a debugging shell to automate Firefox OS testing." to something
like "Marionette is based on the Selenium/WebDriver API, and provides
the basis for the debugging shell we use to automate Firefox OS testing."
This will help mitigate any bugs, and help people get a better
understanding of why they're installing what they're installing:)
Furthermore, if these are nightly builds, they don't need to modify the
prefs.js stuff. It's set up to work when you start up b2g, so you can
remove those instructions.
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
