562426 - running 'fennec -chrome chrome://mochikit/content/harness.xul' doesn't result in chrome harness as expected

Status: RESOLVED WORKSFORME

(Core :: IPC, defect)

Description

[Joel Maher ( :jmaher ) (UTC -8) (PTO back normal Nov 17)]

if you build fennec with tests, you get all the test binaries and you can run something like:
python runtests.py --appname=<path>/fennec --chrome

This will create a profile and launch fennec similar to (manually removing the redirect here):
<path>/fennec -no-remote -profile <path>/profile -chrome chrome://mochikit/content/harness.xul


looking at the mochikit.manifest I have this:
oel@joel-ubuntu:~/e10s/mochitest$ cat ../fennec/chrome/mochikit.manifest 
content mochikit /home/joel/e10s/mochitest/ contentaccessible=yes
joel@joel-ubuntu:~/e10s/mochitest$ 


Basically this works for desktop firefox and fennec with no problems.  Doing this with e10s fennec builds launches a normal fennec window with the regular init screen instead of a chrome harness screen with a button to "run tests".

Comment 1

[Doug Turner (:dougt)]

did this ever work w/ fennec (without xr)?

Comment 2

[Doug Turner (:dougt)]

joel, any update?

Comment 3

[Joel Maher ( :jmaher ) (UTC -8) (PTO back normal Nov 17)]

ok, I am able to run mochitest-chrome tests on a fennec 2.0 build with browser.tabs.remote=true.

This is looking like a WFM.