Confirmed users
385
edits
Firefox/Windows 8 Integration: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 444: | Line 444: | ||
[http://mxr.mozilla.org/mozilla-central/source/browser/metro/shell/testing/metrotestharness.cpp harness source] | [http://mxr.mozilla.org/mozilla-central/source/browser/metro/shell/testing/metrotestharness.cpp harness source] | ||
== Using Devtools == | |||
* Tracking bug https://bugzilla.mozilla.org/show_bug.cgi?id=850019 | |||
* This hooks into the tools developed & maintained by the devtools team. | |||
* They have been refactoring & improving their tools, so it highly encouraged to use Nightly builds on both sides of the pairing if possible. | |||
* Before you start | |||
** You must have metro installed & working | |||
** You must access to a classic/desktop fx. This need not be a local build | |||
** If you are connecting remotely, you must make sure both machines can ping each other before starting. This will save you a lot of grief later | |||
* Setup | |||
* Notes | |||
** I usually pair on localhost, using an external monitor so I can see metrofx & classicfx at the same time. | |||
** If you are using localhost without an external monitor, beware of windows suspending the metrofx while its waiting for the incoming connection. This will cause the pairing to fail. | |||
** While you can pair classic/metrofx running out of the same obj dir, I frequently experienced unexpected hangs and crashes as a result. | |||
** if you close the devtools window, this usually results in the metro browser shutting down | |||
== Samsung Series 7 == | == Samsung Series 7 == | ||