A more complete solution would rework our fullscreen support to ensure the
flags are consistently used (e.g. reader mode just uses low_profile even though
ActivityUtils.setFullScreen does both low profile and fullscreen).
This patch does several things, all in one commit because of a schema update:
* Uses _id instead of guid when referring to reading list items, allowing the guid column to be null.
* Reworks schema upgrading.
* Completely revises the reading list schema itself.
* Fixes the tests.
* Cleans up how we do deletion: if an item hasn't yet been synced, it's simply deleted immediately. We can do this because the server allocates GUIDs.
* Adds columns to manage sync-related metadata.
This does not always work in the case that one of the last few tabs (to the
right) are selected and the device is rotated from landscape to portrait.
Filed bug 1134408 to track this.
The Android ARchive contains the compiled Gecko libraries that Firefox
for Android interfaces to. It does not contain the Gecko resources
(the omnijar, omni.ja) nor the compiled Java code (classes.dex).
This also uploads metadata and sha1 hashes for future consumption by
Maven and/or Ivy dependency managers. In some brave future world,
we'll work out exactly what that looks like; for now, this solves a
storage problem (each .aar file is ~20MB) and it's possible to point
Gradle directly at the uploaded Ivy metadata and artifacts.
Sometimes it's convenient to want to do an UPDATE query like:
UPDATE foo
SET bar = bar | 5
or similar -- that is, refer to existing values in the SET expression.
This patch allows that, accepting an array of ContentValues and an array of
operations as input. A single UPDATE will be constructed from the entire input.
This does not always work in the case that one of the last few tabs (to the
right) are selected and the device is rotated from landscape to portrait.
Filed bug 1134408 to track this.
BitmapFactory seemingly can't handle resource aliases:
http://stackoverflow.com/a/14553767
Note that this bug affected all phone devices, not just 2.3.
Also removed some unused imports while I was at it.
We couldn't do this before because the button declaration was shared by old and
new tablet - this is no longer a problem now that old tablet is no longer in
use.
As a cleanup, this required the move of favicon -> favicon_globe and the
creation of new resources toolbar_favicon_default, which is aliased to
favicon_globe on phones.
