google_apis: Add a new target to run the unit tests.

This implements the first step of moving google_apis tests from unit_tests target
to a new google_apis_unittests.

This establishes a new unit test executable (google_apis_unittests) and _copy_
(not move) the test google_api_keys_unittest.cc from unit_tests target into
google_apis_unittests target.

BUG=257421
TEST=google_apis_unittests runs and passes, all green.
R=joi@chromium.org

Review URL: https://chromiumcodereview.appspot.com/23976004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224068 0039d316-1c4b-4281-b951-d872f2087c98
Use the short_name manifest property for app titles in the NTP (chrome://apps)

The "short_name" manifest property is now used for app titles in the
new tab page (chrome://apps). The tooltip displays the full app name.
This was implemented for consistency with app titles in the app
launcher.

BUG=288165
TEST=Test 1) Apps which specify a short_name which is different to
the name and 2) Apps which do not specify a short_name.

Review URL: https://chromiumcodereview.appspot.com/24172002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224069 0039d316-1c4b-4281-b951-d872f2087c98
Set the command line switches in crash reports using the crash key logging system.

BUG=77656

Review URL: https://chromiumcodereview.appspot.com/24204003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224070 0039d316-1c4b-4281-b951-d872f2087c98
Narrow scope of recently disabled *RenderWidgetHostViewBrowserTests.

The tests only fail on Win XP, and it's critical they remain enabled for all other Win flavors during all the Win Aura churn.

BUG=294116
TBR=ben@chromium.org

Review URL: https://chromiumcodereview.appspot.com/24228002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224071 0039d316-1c4b-4281-b951-d872f2087c98
Remove 'drive-enabled-status-changed' event.

Now, Drive's mounting state, including enable/disable state is managed by
DriveIntegrationService via VolumeManager in C++. So we don't need to track
it in Files.app in most cases.
This is the first CL to clean up js-code.

BUG=268817
TEST=Ran browser_tests --gtest_filter="*FileSystemExtensionApiTest*:*FileManagerBrowserTest*:*FileBrowserPrivateApiTest*" and tested manually.

Review URL: https://chromiumcodereview.appspot.com/23437043

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224072 0039d316-1c4b-4281-b951-d872f2087c98
Update cros_disks_client to work with Unmount method returning status.

...in addition to Unmount method that sets dbus error on failure.
This is in preparation of changing Unmount method to return mount
status on cros-disks side.

BUG=288974
TEST=try unmounting a device both while it's busy and idle.
In the first case, unmount fails and a warningis shown.
In the second case, the device is successfully unmounted.

Review URL: https://chromiumcodereview.appspot.com/23684051

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224073 0039d316-1c4b-4281-b951-d872f2087c98
Use IO loop for the compositor thread in the renderer on posix.

MessagePumpDefault breaks PostDelayedTask on posix because it uses system time.
MessagePumpIO uses monotonic time, so is immune to these problems.

(These threads because they schedule things with PostDelayedTask).

BUG=293736

Review URL: https://chromiumcodereview.appspot.com/24234002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224074 0039d316-1c4b-4281-b951-d872f2087c98
Reduced the number of 'important metrics' in the quality tests.

We were printing every single memory metric on the browser test step, as can be seen here: http://chromegw/i/internal.chromium.webrtc/builders/Linux%20Hideout%20Tester/builds/8839. After this patch we'll print less of them, just working set peak size for browser and renderer.

R=tommi@chromium.org
BUG=
NOTRY=True

Review URL: https://chromiumcodereview.appspot.com/23484049

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224075 0039d316-1c4b-4281-b951-d872f2087c98
Documentation for short_name manifest property

BUG=226848
NOTRY=true

Review URL: https://chromiumcodereview.appspot.com/23522005

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224076 0039d316-1c4b-4281-b951-d872f2087c98
rAc: back away from the close button

move account chooser over a little

BUG=294471

Review URL: https://chromiumcodereview.appspot.com/24241002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224077 0039d316-1c4b-4281-b951-d872f2087c98
No longer tolerate unknown fields in gpu blacklist.

Originally we update blacklist independent of chrome update, so a new feature might be added to blacklist, but the old version of chrome may not recognize it.  We don't want the total blacklist to fail.

Now we no longer have live updates, so we should make sure all the info in the blacklist is valid.

BUG=
TEST=gpu_unittests

Review URL: https://chromiumcodereview.appspot.com/24242002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224078 0039d316-1c4b-4281-b951-d872f2087c98
Turn on Synced Notification Sending services by default for all users, and save preferences.

This is for the new Synced Notification feature, which allows servers to send notification toasts to the chrome message center (also called the notification center).

As things stand today (before this checkin), Synced Notifications is enabled, but each data type from an individual server needs to be intentionally enabled by the user finding the notification center settings panel and clicking a check box for that service to the "enabled" state.

After lots of rounds of UI discussion we decided the best experience for the user is to default the sending services to enabled instead of the way it defaults to disabled today.

So, the goal of this checkin is just to change the state of the existing synced notification type from disabled to enabled by default.

As it turns out, it wasn't as easy as just changing false to true somewhere.  We opted (after the first round of code review) for a scheme that maintains two preference lists, a list of enabled synced notification services (which we will now add our first sending service to, and in the future we plan to add other services), and a list of preferences that we have "initialized" (or basically turned them on by default once).  We need the second list because we are turning the service on at runtime, and if the user later wants to turn the service off, we need to remember and not just turn it on again.  I intended to describe this part adequately in my changelist, but apparently I didn't describe it well enough, and I'll try to amend the description.

BUG=280250

Review URL: https://chromiumcodereview.appspot.com/23534048

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224080 0039d316-1c4b-4281-b951-d872f2087c98
Disable WebViewTest.ConsoleMessage on Win.

TBR=fsamuel@chromium.org
BUG=294592

Review URL: https://codereview.chromium.org/24259003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224081 0039d316-1c4b-4281-b951-d872f2087c98
rAc: notifications tweaks

1. Always show "Protect my payment with Wallet" checkbox.
1b. The checkbox is always interactive (it's not visible during submit any more anyway because of the virtual card interstitial).

2. Relax restriction about showing multiple notifications in dialog. Currently to avoid showing too many notifications, wallet promos are not shown when there are warnings in the view. Really this only affects (and confounds) testing, because in testing is where you're likely to see the http:// warning and the sandbox server warning. Actual users shouldn't see the warnings anyway, so there's no win for normal users.

3. Fix a regression where the checkbox was not working on Views.

4. Fix a bug where the account chooser text would sometimes be misaligned (due to a quirk of TextButtonBase sizing).

BUG=289008

Review URL: https://chromiumcodereview.appspot.com/23523050

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224082 0039d316-1c4b-4281-b951-d872f2087c98
drive: Preserve cache entries even when the DB version is incompatible

BUG=256919
TEST=unit_tests

Review URL: https://chromiumcodereview.appspot.com/23468026

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224083 0039d316-1c4b-4281-b951-d872f2087c98
Files.app: Stop multiple times window opening when insetring USB/SD.

The crbug.com/222013 made Files.app open its window asynchronously and this
causes to fail the existing window check.
This CL serializes the request of window opening.

BUG=293925
TEST=call onExecute method from the inspector multiple times at once.

Review URL: https://chromiumcodereview.appspot.com/24152008

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224084 0039d316-1c4b-4281-b951-d872f2087c98
Added sounds for CrOS startup, lock, unlock and shutdown from go/ChromeSounds.

BUG=271057
TEST=none
R=jennyz@chromium.org, nkostylev@chromium.org, sky@chromium.org

Review URL: https://codereview.chromium.org/23702046

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224085 0039d316-1c4b-4281-b951-d872f2087c98
Fix typo with ENABLE_MDNS define.

Review URL: https://chromiumcodereview.appspot.com/23615016

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224086 0039d316-1c4b-4281-b951-d872f2087c98
[Sheriff] Disable flaky browser test on windows.

BUG=282116
R=grunell@chromium.org
TBR=grunell@chromium.org

Review URL: https://codereview.chromium.org/24261002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224087 0039d316-1c4b-4281-b951-d872f2087c98
CC: Disable raster-on-demand during prefer-smoothness

We prioritize memory in the active tree during accelerated
gestures, so we can't trigger raster-on-demand if the
pending tree tiles are missing.

This patch delays raster-on-demand, by not
activating until the accelerated gesture is complete.

This patch follows these two fixes (which guarantee
activation, and showing new visible tiles while waiting
for activation).
https://codereview.chromium.org/23686011/
https://codereview.chromium.org/23495022/

BUG=264566

Review URL: https://chromiumcodereview.appspot.com/23921005

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224089 0039d316-1c4b-4281-b951-d872f2087c98