This patch does a few other small things as well:
* It exposes the client device type. This will be used later, as part of
the visual refresh.
* Aligns the field names in remote_tabs_child with the names used by
TwoLinePageRow. This will be used later, when we finally use said
standard view class.
--HG--
extra : rebase_source : 291f69a5f9b68801dd9154c5d291c6795d218ff6
In order to launch in response to the MAIN activity (via |adb shell am
start -a android.intent.action.MAIN org.mozilla.fennec|, for example),
the activity must have category default. That is added automatically to
<activity> elements that have category LAUNCHER, but apparently not to
<activity-alias> elements. This patch adds it manually.
In general, <intent-filters> are prioritized by their order in the
manifest file. To avoid future confusion, this patch bumps the
android:priority of the existing filter.
--HG--
extra : rebase_source : 021da06af2f3e41fc0f38eee7fc33360797f64b0
The menu is exposed as "More..." on devices that do not have a hardware
menu button.
========
8adeb1be57
Author: Nick Alexander <nalexander@mozilla.com>
Bug 984503 - Part 4: Show a toast after removing Firefox Account.
========
aeffca77dc
Author: Nick Alexander <nalexander@mozilla.com>
Date: Thu Aug 28 15:05:11 2014 -0700
Bug 984503 - Part 3: Hide "More..." option if device has a hardware menu button.
The reason for this dance is to keep the "Remove Account" button out of
view if at all possible. I don't want to make it too easy to delete
your account.
========
4efe597308
Author: Nick Alexander <nalexander@mozilla.com>
Date: Thu Aug 28 15:04:38 2014 -0700
Bug 984503 - Part 2: Add "More..." to Firefox Account status list.
========
ad6a55dc33
Author: vivek <vivekb.balakrishnan@gmail.com>
Date: Thu Aug 21 00:25:30 2014 +0300
Bug 984503 - Part 1: Add menu option to remove Firefox Account.
--HG--
extra : rebase_source : 946b86baaa36de4b143d6d8a614f7cc3a2118a6a
This creates libmozsandbox.so on builds that use sandboxing
(MOZ_CONTENT_SANDBOX or MOZ_GMP_SANDBOX).
The unavoidably libxul-dependent parts, for invoking the crash reporter
and printing the JS context, are separated into glue/SandboxCrash.cpp
and invoked via a callback.
========
f9d27162dc
Author: Nick Alexander <nalexander@mozilla.com>
Date: Tue Aug 26 17:47:33 2014 -0700
Bug 958341 - Test and review comments.
========
7b82898363
Author: Nick Alexander <nalexander@mozilla.com>
Date: Mon Aug 18 14:53:54 2014 -0700
Bug 958341 - Present "motivating service" to /account/create calls.
This is used for metrics and for personalizing the welcome emails.
Since no email gets sent for /account/login, it is not needed there.
========
3cd96669bc
Author: Nick Alexander <nalexander@mozilla.com>
Date: Mon Aug 18 17:43:24 2014 -0700
Bug 1026005 - Review comments.
========
5aefe1f716
Author: Nick Alexander <nalexander@mozilla.com>
Date: Mon Jun 16 11:16:16 2014 -0700
Bug 1026005 - Part 2: Add AccountLoader.
========
61bc36bd7d
Author: Nick Alexander <nalexander@mozilla.com>
Date: Mon Jun 16 11:12:37 2014 -0700
Bug 1026005 - Part 1: Add and broadcast ACCOUNT_STATE_CHANGED_ACTION.
========
9d80df0aa7
Author: Nick Alexander <nalexander@mozilla.com>
Date: Mon Aug 18 17:42:11 2014 -0700
Bug 1026005 - Pre: Allow testing with |mvn integration-test|.
This avoids errors like:
W dalvikvm(24082) Class resolved by unexpected DEX: Lorg/mozilla/gecko/fxa/AccountLoader;(0x42c13358):0x75440000 ref [Landroid/support/v4/content/AsyncTaskLoader;] Landroid/support/v4/content/AsyncTaskLoader;(0x42c13358):0x74a71000
W dalvikvm(24082) (Lorg/mozilla/gecko/fxa/AccountLoader; had used a different Landroid/support/v4/content/AsyncTaskLoader; during pre-verification)
W dalvikvm(24082) Unable to resolve superclass of Lorg/mozilla/gecko/fxa/AccountLoader; (247)
W dalvikvm(24082) Link of class 'Lorg/mozilla/gecko/fxa/AccountLoader;' failed
E dalvikvm(24082) Could not find class 'org.mozilla.gecko.fxa.AccountLoader', referenced from method org.mozilla.gecko.background.fxa.TestAccountLoader.testInitialLoad
W dalvikvm(24082) VFY: unable to resolve new-instance 1299 (Lorg/mozilla/gecko/fxa/AccountLoader;) in Lorg/mozilla/gecko/background/fxa/TestAccountLoader;
D dalvikvm(24082) VFY: replacing opcode 0x22 at 0x0005
W dalvikvm(24082) Class resolved by unexpected DEX: Lorg/mozilla/gecko/fxa/AccountLoader;(0x42c13358):0x75440000 ref [Landroid/support/v4/content/AsyncTaskLoader;] Landroid/support/v4/content/AsyncTaskLoader;(0x42c13358):0x74a71000
W dalvikvm(24082) (Lorg/mozilla/gecko/fxa/AccountLoader; had used a different Landroid/support/v4/content/AsyncTaskLoader; during pre-verification)
W dalvikvm(24082) Unable to resolve superclass of Lorg/mozilla/gecko/fxa/AccountLoader; (247)
W dalvikvm(24082) Link of class 'Lorg/mozilla/gecko/fxa/AccountLoader;' failed
D dalvikvm(24082) DexOpt: unable to opt direct call 0x1df8 at 0x07 in Lorg/mozilla/gecko/background/fxa/TestAccountLoader;.testInitialLoad
I TestRunner(24082) started: testInitialLoad(org.mozilla.gecko.background.fxa.TestAccountLoader)
I TestRunner(24082) failed: testInitialLoad(org.mozilla.gecko.background.fxa.TestAccountLoader)
I TestRunner(24082) ----- begin exception -----
I TestRunner(24082)
I TestRunner(24082) java.lang.NoClassDefFoundError: org.mozilla.gecko.fxa.AccountLoader
I TestRunner(24082) at org.mozilla.gecko.background.fxa.TestAccountLoader.testInitialLoad(TestAccountLoader.java:145)
I TestRunner(24082) at java.lang.reflect.Method.invokeNative(Native Method)
I TestRunner(24082) at java.lang.reflect.Method.invoke(Method.java:525)
I TestRunner(24082) at android.test.InstrumentationTestCase.runMethod(InstrumentationTestCase.java:214)
I TestRunner(24082) at android.test.InstrumentationTestCase.runTest(InstrumentationTestCase.java:199)
I TestRunner(24082) at android.test.ActivityInstrumentationTestCase2.runTest(ActivityInstrumentationTestCase2.java:192)
I TestRunner(24082) at junit.framework.TestCase.runBare(TestCase.java:134)
I TestRunner(24082) at junit.framework.TestResult$1.protect(TestResult.java:115)
I TestRunner(24082) at junit.framework.TestResult.runProtected(TestResult.java:133)
I TestRunner(24082) at junit.framework.TestResult.run(TestResult.java:118)
I TestRunner(24082) at junit.framework.TestCase.run(TestCase.java:124)
I TestRunner(24082) at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:191)
I TestRunner(24082) at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:176)
I TestRunner(24082) at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:554)
I TestRunner(24082) at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1738)
I TestRunner(24082) ----- end exception -----
I TestRunner(24082) finished: testInitialLoad(org.mozilla.gecko.background.fxa.TestAccountLoader)
========
1c4a5d5c13
Author: Nick Alexander <nalexander@mozilla.com>
Date: Wed Aug 20 10:53:40 2014 -0700
Bug 1056227 - Don't always go back to status after updating Firefox Account credentials.
This was a simple oversight. With embedded links to update your
credentials in Fennec's Remote Tabs interfaces, just returning to where
you came from is the right thing to do.
I took the most commented version. There are two things to note here:
* Several panels did not define onConfigurationChanged. It's not clear
if these panels didn't need it (after some analysis?) or if they just
didn't copy-paste thoroughly. This version is always safe, if
inefficient, and I've commented to say as much.
* The order of operations for the Bookmarks panel may be delicate. I
did not preserve the original order (save stack first, then detach and
attach); it appears to not be necessary to save the stack first,
because the configuration change is completed before the containing
Activity is restarted (and the stack is restored). I tested that the
folder stack was preserved across device rotations locally.
The C++ GLContext wrapper doesn't know about the changes to the GL state that the
Java code does, so Java must be careful to restore the GL state to the way
it was. The ScopedGLState RAII code doesn't quite accomplish this because of caching
in the C++ GLContext wrapper, so we have to do this directly from Java code.
This patch does two things. First, it adds the Search Activity sources
to the main Fennec Eclipse project (when enabled). There's no reason
for a separate project for these, since they are built as part of the
main Fennec package by moz.build.
Second, it arranges for Eclipse to generate the R.java and Manifest.java
files for all Android libraries and ignores the files generated by
moz.build. (The relevant classes are org.mozilla.{gecko,search}.R.)
This means renaming the FennecResources Eclipse project's package to
org.mozilla.gecko, and renaming the FennecResourcesSearch project's
package to org.mozilla.search. To be consistent, I switched
org.mozilla.fennec.resources to org.mozilla.gecko throughout.
To accommodate the crash reporter resources, which depend on the static
and generated resources, I added a layer of indirection. By moving the
main resources into project FennecResourcesStatic, we can have (reading
indentation as "depends on"):
FennecResources
FennecResourcesCrashReporter
FennecResourcesStatic
FennecResourcesGenerated
FennecResourcesBranding
This lets us break the bidirectional dependency between FennecResources
and FennecResourcesCrashReporter.
========
5b97feec90
Author: Ben Curtis <androiddev@nosolutions.com>
Bug 1046020 - Include URI port in token server audiences.
--HG--
extra : amend_source : 706eaa493e969ce27470aafd482f6b61f5f88db8
