Not sure what to do here so I filed bug 1177901.
--HG--
extra : commitid : BCnmZfSMhyF
extra : rebase_source : dd2c7f167d62883616f522ada485e36966bbc862
Note: the tinted view is only a single color while the original asset contains
gradients.
--HG--
extra : commitid : DhaVxpPBMn2
extra : rebase_source : a1991ff478260441e6ac788ba5384a7e7a518d2a
You can now run by `cd mobile/android && eslint . --ext "[.js,.jsm]"`.
--HG--
extra : commitid : AAENN0WrJVl
extra : rebase_source : 4a7fb888ef16a29580fa7b5d394c44aabd387210
eslint can be run by `cd`ing to mobile/android and running `eslint .` (assuming
eslint is installed). Note that .jsm files have not yet been configured.
Add an eslintignore to avoid the files that will take more work.
--HG--
extra : commitid : LcrYaNh2sSn
extra : rebase_source : 43a2b1988049003b1e225fa60671a04f62c3d44a
This removes ambiguity as to which modules are being imported, making
import slightly faster as Python doesn't need to test so many
directories for file presence.
All files should already be using absolute imports because mach command
modules aren't imported to the package they belong to: they instead
belong to the "mach" package. So relative imports shouldn't have been
used.
--HG--
extra : commitid : 6tFME1KKfTD
extra : rebase_source : 78728f82f5487281620e00c2a8004cd5e1968087
DONTBUILD ON A CLOSED TREE: Android-only and the build changes are cosmetic.
Very much a first cut, but I'd like to get some Fennec early adopters testing.
This adds:
* |mach artifact install| to fetch and install Fennec binaries;
* |mach artifact last| to print details about what was last installed;
* |mach artifact {print,clear}-caches|, for debugging.
This code is exposed as a new mozbuild.artifacts Python but it's not
particularly general. My intention was to get things out of the mach command
more than produce a general artifact fetching API. We can leave that bike
shed to Bug 1124378.
I've been testing this with --disable-compile-environment and it works well
locally, although there's no reason a knowledgeable developer couldn't use
this in conjunction with a fully-built tree. (I don't know when such a
situation would arise, but I know of no technical impediment.)
--HG--
extra : commitid : 1T28aVfArqF
extra : rebase_source : b8c11244de8be0a14d605853f30cd47312d0a4ba
extra : histedit_source : 78a224501cd3cf0f86707c9c9549b61b4b248ba7
This was causing crashes on tablet devices.
I'm not sure what it was for but pretty sure it was an artifact that was never
removed in old tablet builds.
--HG--
extra : commitid : HVyBG7WSkjT
Inside a ScrollView. According to Android Lint:
ScrollView children must set their layout_width or layout_height attributes to
wrap_content rather than fill_parent or match_parent in the scrolling dimension
--- Who am I to argue?
--HG--
extra : commitid : EomuSjCkA7a
extra : rebase_source : 7c6fb5539f96744f3dfa2bd3613ecd95fe1d6e2e
We have a custom menu system here and interpret these attributes ourselves so
this warning isn't relevant to us.
--HG--
extra : commitid : 9iDtQH2P86
extra : rebase_source : 1f2e5c37e57057cd92971a3ff637837032f78516
This moves the tabs and clients table into the main per-profile
browser.db database. It's a code savings but it also makes it easier
to query against open tabs when inspecting parts of the browser
database, like history and bookmarks.
--HG--
extra : commitid : GFnp5ADiaKQ
extra : rebase_source : 944afa7a2af67cb177c72fdad2d0340f470e5d23
extra : amend_source : 2a1748ed22db0d9dc984f20ef9f53385c2ce9fdb
