Enable new detached bookmark bar by default

For Instant Extended we have a new look for the detached bookmark bar.
This CL enables that look by default.

BUG=256343
TEST=Disable instant extended in chrome://flags. Open a new tab.
Verify that the new detached bookmark bar is visible.
NOTRY=true

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209567 0039d316-1c4b-4281-b951-d872f2087c98
cc: Made use color estimator a const instead of a flag.

Color estimator has been running for some time now, and it seems
to be stable. This change removes the piping of the flag down to
where it's used. The flag is still in the code for easy debugging.

R=reveman@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209568 0039d316-1c4b-4281-b951-d872f2087c98
[Android] Fix bug in sense of setting isSyncable.

The API specifies that >0 means syncable is true. After
https://codereview.chromium.org/16092014/ when Android sync settings
change, we have to read-back values to make sure we have the right
settings. This started causing tests to fail as we stored the wrong
value.

BUG=238506
NOTRY=true

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209569 0039d316-1c4b-4281-b951-d872f2087c98
Let the Android OOM kill inactive renderers.
    
This patch lowers the bind priority for inactive renderer services so that the
system out-of-memory killer is able to manage and kill them like background
apps.

In order to ensure that renderers that are not yet visible (i.e. before being
swapped in) are not killed, every renderer service is bound with a possibly 
short-lived high priority connection first, another (persistent) low priority
connection is added right after that.

The patch refactors ChildProcessConnection class, hiding the implementations of
the ServiceConnection interface within the class and decoupling the actual
bindings from the abstraction of ChildProcessConnection.

BUG=249214

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209570 0039d316-1c4b-4281-b951-d872f2087c98
Message center profile fix

Message center changed to use last used profile instead of default profile.

BUG=256415

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209573 0039d316-1c4b-4281-b951-d872f2087c98
Revert "roll breakpad 1182:1198"

The breakpad roll in 209552 had compile errors on the chromium.chrome
builders.

TBR=thakis@chromium.org
BUG=none

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209574 0039d316-1c4b-4281-b951-d872f2087c98
Cleanup: move AlwaysOnTopController to RootWindowController
remove if (shelf_) as it should always be there.

BUG=253991

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209575 0039d316-1c4b-4281-b951-d872f2087c98
cros: Fix launcher size not properly initialized.

On Chrome OS, launcher is created after user login and could be created
after its container Window and status widget has finished sizing. An explicit
LayoutShelf call is needed to ensure its size is properly initialized.

BUG=252533

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209576 0039d316-1c4b-4281-b951-d872f2087c98
Revert 209505 "[Telemetry] Fix page_cycler for pages with client..."

Looks to have caused an unexpected perf regression.

BUG=256492

> [Telemetry] Fix page_cycler for pages with client side redirects.
> 
> Page.disable clears all scripts to evaluate on commit. There is no way
> to detect client side redirects because linkedin, for example, performs
> its client side redirect after the page has fully loaded.
> 
> In order for the page_cyclers to work on pages with client side
> redirects, the script to evaluate on commit must execute on the
> redirected page.
> 
> So to workaround this, we avoid ever calling Page.disable. I don't
> expect continuing to listen for notifications here to impact
> performance, but if we do see any performance reduction on the bots we
> should revert and search for another approach.
> 
> BUG=253604
> TEST=tools/perf/run_measurement --browser=canary page_cycler tools/perf/page_sets/key_mobile_sites.json --pageset-repeat=1
> NOTRY=True
> 
> Review URL: https://chromiumcodereview.appspot.com/18270002

TBR=tonyg@chromium.org

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

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209578 0039d316-1c4b-4281-b951-d872f2087c98
Upgrading Mesa to 9.0.3

BUG=238755
R=apatrick@chromium.org, nduca@chromium.org

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

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

This test is timing out pretty consistently on ARM linux.

BUG=239366

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

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209581 0039d316-1c4b-4281-b951-d872f2087c98
[Android] Add an action to check/record attached devices

When doing a gyp_managed_install, we install APKs to the attached
device. Currently this can fail in many ways (no device attached,
multiple devices attached, device offline, device doesn't have root,
etc.). In addition, we need to detect changes to the attached device
(particularly when the device is switched, when an APK is
 uninstalled/updated).

The current approach is to check all this information in the action
interacting with the device. This means that when there is some
problem we print the same warning messages for every APK that is built,
and, in some cases, multiple times for each APK. Also, we have to run
every install/push action every build because we detect changes to the
attached device in that action.

This change creates a new build action, "get device configurations".
This action inspects the attached devices, filters out offline devices,
filters out devices without root, and then writes a configuration
file with the id+metadata for the first non-filtered device. This
configuration is then used by each of the build steps that interacts
with the device. This consolidates all the device checking to a single
place, and the build actions don't need to do any checking. In
addition, to detect changes in the attached device, we only need to run
this single action every build and the install/push actions will only
change when the device/metadata changes.

Also, with this change we can now gracefully handle the case where
multiple devices are attached (currently just write the configuration
for the first valid device and install to that one).

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209582 0039d316-1c4b-4281-b951-d872f2087c98
Doc server tabs.html message passing URL fix

BUG=256359

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209583 0039d316-1c4b-4281-b951-d872f2087c98
Add files to third_party/mesa missed in r209759.

TBR=kbr@chromium.org
BUG=238755

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209584 0039d316-1c4b-4281-b951-d872f2087c98
Update details area when Wallet is disabled.

BUG=254684

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209585 0039d316-1c4b-4281-b951-d872f2087c98
Add extension name to Extension Status tab. (More human readable than Extension ID)

BUG=256122
TEST=manual
open chrome://syncfs-internals
click on Extension Status tab
For each entry you should see the Extension name beside its ID and sync status

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209586 0039d316-1c4b-4281-b951-d872f2087c98
Doc server table of contents works for anchors that contain spaces.

BUG=256316

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209587 0039d316-1c4b-4281-b951-d872f2087c98
This should add a Salsa App chrome:// page for ChromeOS

Salsa is a rapid user testing system developed for use by the ChromeOS
touch team to quickly run blind studies on various settings.  There are
a lot of subjective decisions to be made about tuning various
parameters, so being able to quickly take a blind poll to see which
people prefer can be very valuable.

Salsa already exists for testing the "X Input" parameters.  These are
the settings you can change with the xinput command at a shell on your
Chromebook.  However, previously you could only do those.  This change
adds a chrome://salsa page to Chrome for ChromeOS only where you can
do a similar experiment but changing the Chrome gesture configurations
and preferences (those that you can change manually at chrome://gesture)
as your experiment instead

The way it works:
    1) An experiment is made, which generates a URL for the experiment
    that can be emailed out to the participants.

    2) Participants will click on the link.  The page shows them a form
    for ranking their experiences, and an encoded string to use when
    running the test.  In this case it will be something like:

    chrome://salsa/#A_HEX_ENCODED_STRING_FOR_THE_EXPERIMENT

    3) The new salsa page parses this string into "treatments" and
    applies them one at a time while the user can try them out and see
    which they prefer before reporting their results.

BUG=chromium:249762
TEST=manually built Chrome and tested with an experiment string I made.

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

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