Closed
Bug 752690
Opened 12 years ago
Closed 12 years ago
Various problems encountered with mozdevice when trying to get Google Chrome and Stock ICS working with Eideticker
Categories
(Testing :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla15
People
(Reporter: wlach, Assigned: wlach)
Details
Attachments
(1 file)
5.94 KB,
patch
|
jmaher
:
review+
|
Details | Diff | Splinter Review |
When trying to get google chrome and the ICS stock browser working with eideticker, I found a few problems with the way I had written the launchApplication method in droid.py: * Google Chrome doesn't understand the way we quote the URL * You can't set the right activity name for the stock browser: we want 'com.android.browser.BrowserActivity', but the way we expand things out you can only specify activity names like '.BrowserActivity' that are an expansion of the package name, which is 'com.google.android.browser' in ICS's case (so the only possibility is 'com.google.android.browser.<foo>' when what we need is 'com.android.browser.<foo>'). I didn't quite understand this before but now I do. :) * There are various fennecisms in the method which do not correspond to the way android works. What we really need is to enable the user to provide an "extras" dictionary which the application can later access. For fennec, the types of extras we're interested in are "args" (simulated command line "arguments") and "env" (a list of environment variables which fennec should export). Other applications may want to do something different. Fortunately droid.py is only used in Eideticker at the moment, so I have free rein to fix things. :)
Assignee | ||
Updated•12 years ago
|
Summary: Various problems encountered with mozdevice when trying to get Google Chrome and Stock ICS working → Various problems encountered with mozdevice when trying to get Google Chrome and Stock ICS working with Eideticker
Assignee | ||
Comment 1•12 years ago
|
||
I'm generally pretty happy with this patch. The one thing I'm a little uncertain about is my addition to a launchFennec method. As I say in the comments, I think it would go better in the mozrunner module (I think it's better to seperate mozdevice from actually managing firefox stuff as much as possible), but I'm not sure if *that* makes sense to do just yet as my "remote firefox runner" is still very much a work-in-progress. Maybe it's better just to leave it in eideticker-only for now? That's the only place it would be used.
Assignee: nobody → wlachance
Attachment #621736 -
Flags: review?(jmaher)
Comment 2•12 years ago
|
||
Comment on attachment 621736 [details] [diff] [review] Improvements to devicemanager to make google chrome and stock ics launchable Review of attachment 621736 [details] [diff] [review]: ----------------------------------------------------------------- nice. I suspect we will find yet another case in the future that will require some fiddling with this. Overall I think it is a lot more generic now!
Attachment #621736 -
Flags: review?(jmaher) → review+
Assignee | ||
Comment 3•12 years ago
|
||
Inbound: http://hg.mozilla.org/integration/mozilla-inbound/rev/a9d94e8f4073 (removed some whitespace-only changes from the patch before applying)
OS: Linux → Android
Hardware: x86_64 → ARM
Target Milestone: --- → mozilla14
Comment 4•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/a9d94e8f4073
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: in-testsuite-
Resolution: --- → FIXED
Target Milestone: mozilla14 → mozilla15
You need to log in
before you can comment on or make changes to this bug.
Description
•