This also completely remove build/automationutils.py.
--HG--
extra : commitid : 50v6EAQNEHV
extra : rebase_source : 4ac1347d73498f068979514c6afb16ac50ab4033
I want to include a file built during the Fennec build to the
roboextender extension; this is an easy way to arrange it.
I took the opportunity to make the extension file tree mirror the XPI
file tree, which always used base/.
--HG--
rename : testing/mochitest/roboextender/Makefile.in => mobile/android/tests/browser/robocop/roboextender/Makefile.in
rename : mobile/android/tests/browser/robocop/roboextender/SelectionUtils.js => mobile/android/tests/browser/robocop/roboextender/base/SelectionUtils.js
rename : mobile/android/tests/browser/robocop/roboextender/paymentsUI.html => mobile/android/tests/browser/robocop/roboextender/base/paymentsUI.html
rename : mobile/android/tests/browser/robocop/roboextender/robocop_home_banner.html => mobile/android/tests/browser/robocop/roboextender/base/robocop_home_banner.html
rename : mobile/android/tests/browser/robocop/roboextender/robocop_prompt_gridinput.html => mobile/android/tests/browser/robocop/roboextender/base/robocop_prompt_gridinput.html
rename : mobile/android/tests/browser/robocop/roboextender/testInputSelections.html => mobile/android/tests/browser/robocop/roboextender/base/testInputSelections.html
rename : mobile/android/tests/browser/robocop/roboextender/testSelectionHandler.html => mobile/android/tests/browser/robocop/roboextender/base/testSelectionHandler.html
rename : mobile/android/tests/browser/robocop/roboextender/testTextareaSelections.html => mobile/android/tests/browser/robocop/roboextender/base/testTextareaSelections.html
rename : testing/mochitest/roboextender/bootstrap.js => mobile/android/tests/browser/robocop/roboextender/bootstrap.js
rename : testing/mochitest/roboextender/chrome.manifest => mobile/android/tests/browser/robocop/roboextender/chrome.manifest
rename : testing/mochitest/roboextender/install.rdf => mobile/android/tests/browser/robocop/roboextender/install.rdf
rename : testing/mochitest/roboextender/moz.build => mobile/android/tests/browser/robocop/roboextender/moz.build
extra : commitid : 2BkQaW1ESSI
extra : rebase_source : cd7ca3327f77584542a77b26519c9a812f48c48e
extra : histedit_source : fe49f2ab0b6193b49a8c5c5cf4da51a5a4b993f7
This introduces a new medule ContentTask, which includes a spawn method.
This new method can be used to spawn a task in the content process of a
browser. When called, a promise will be returned which resolves to the
value returned by the task.
This allows you to quickly write test code which can touch the content
and return information without having to write custom framescripts all
the time (The content code can be written inline as a simple generator
definition). ContentTask is automatically included in the scope of
mochitests.
An example use follows:
yield ContentTask.spawn(browser, {}, function* gen_replaceState() {
content.window.history.replaceState({}, "", 'test-entry/');
return "Value that the promise will resolve with";
});
--HG--
extra : rebase_source : 9b6ae71407da582cdaa8087b5e367c72fa08a337
Simple refactor that moves logic out of manifestparser.py and into cli.py, expression.py and ini.py.
--HG--
extra : rebase_source : dd454973cdb3bcb7ec29dd2e1c0c594e3b3fb817
Every directory with a jar.mn now has JAR_MANIFESTS defined in its
moz.build file.
We also removed the may_skip special consideration of jar.mn files
because this information is now available during tier traversal by the
reader courtesy of the variables being present in moz.build files.
--HG--
extra : rebase_source : 21049b15e6bd9cf65b0805ccaccc4ba5aae93c98
extra : amend_source : 0b1ea866d725beef92d37c6f6d475369ac002e19
Julien Pagès
Geoff Brown
Ryan VanderMeulen
Nick Alexander
Andrew Halberstadt
Nathan Froyd
Vaibhav Agrawal
Joel Maher
Steven MacLeod
Kershaw Chang
Michal Novotny
Dave Townsend
Ted Mielczarek
Gregory Szorc
Joshua Cranmer
Kyle Machulis