Remove pp_ifdef from grd files in ui/.

Generated using:
> cd src/ui
> git grep -l pp_ifdef | xargs sed -i "s:pp_ifdef('\([^']\+\)'):\1:g"

BUG=343235
R=arv@chromium.org, joi@chromium.org, oshima@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251895 0039d316-1c4b-4281-b951-d872f2087c98
Remove the --ui-enable-threaded-compositing flag.

We're not planning to enable this on any new platforms, so we can just
hardcode it off when not on ChromeOS. Leaving the disable flag for
ChromeOS for now, as we're working on disabling that code path there.

R=piman
BUG=

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251896 0039d316-1c4b-4281-b951-d872f2087c98
Exclude Translate Bubble strings from non Views builds.

BUG=326023

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251897 0039d316-1c4b-4281-b951-d872f2087c98
cc: Remove the --enable-partial-swap flag.

R=piman
BUG=

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251898 0039d316-1c4b-4281-b951-d872f2087c98
Attempt at making ToplevelWindowEventHandlerTest.RunMoveLoopFailsDuringInProgressDrag less flaky

The test seems to pass fine when I run it manually on Windows Ash (including with high values of --gtest_repeat)
This CL:
- Makes ToplevelWindowEventHandlerTest.RunMoveLoopFailsDuringInProgressDrag look more like ToplevelWindowEventHandlerTest.Caption which I don't think is flaky on Windows Ash.
- Adds an extra check which will help better understand the source of the flakiness should it occur again

BUG=343167
TEST=None

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251899 0039d316-1c4b-4281-b951-d872f2087c98
[Refactor] Always pass in screen coordinates to UIControlsAura::SendMouseMove()

BUG=None
TEST=None

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251900 0039d316-1c4b-4281-b951-d872f2087c98
Set a reasonable icon for the media galleries scan result dialog folder viewer.

Resubmission of https://codereview.chromium.org/130263007/ with the binary resources added with dcommit.

BUG=334309, 161119
TBR=oshima@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251901 0039d316-1c4b-4281-b951-d872f2087c98
Properly initialize logging in quic_server and quic_client so
that --v=1 is functional.

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251903 0039d316-1c4b-4281-b951-d872f2087c98
android envsetup: Use gyp defines instead of env vars for sdk root and sdk tools.

If ANDROID_SDK_ROOT is set, it's still added to the path for now, but it's
no longer passed to gyp. If you want to set a custom sdk root, call gyp like
"build/gyp_chromium -Dandroid_sdk_root=path".

If ANDROID_SDK_ROOT is not set, it's still getting exported with a default
value that's identical to the default value of gyp's android_sdk_root variable.

ANDROID_SDK_TOOLS and ANDROID_SDK_BUILD_TOOLS_VERSION are now
completely ignored. Set the android_sdk_tools or android_sdk_build_tools_version
gyp defines instead if you need to change either. If they are not set,
envsetup no longer sets them.

(Dependent on an internal that changes a bot to set these gyp defines in
addition to the env vars.)

BUG=330631
NOTRY=true

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251904 0039d316-1c4b-4281-b951-d872f2087c98
Whitespace change to kick all the bots.

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251911 0039d316-1c4b-4281-b951-d872f2087c98
Remove allow-webui-compositing switch

Long ago, we used to disable compositing on chrome: and about: URLs by default
since that caused a startup performance hit. We then had an --allow-webui-compositing
switch to override this behavior when desired.  The usefulness of this behavior
has long gone and we completely ignore the behavior and the flag on aura builds. This
nukes it from the code

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251915 0039d316-1c4b-4281-b951-d872f2087c98
Requests stats on webrtc-internals as soon as the initial peer connection records are received.
This will get rid of the 1 second delay from waiting for setInternal to fire.

BUG=

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251916 0039d316-1c4b-4281-b951-d872f2087c98
Pass in correct parameter to MenuController::SelectByChar() on Linux Aura

BUG=342316
TEST=MenuControllerMnemonicTest*.*

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251917 0039d316-1c4b-4281-b951-d872f2087c98
Do not send a frame swap ack from the browser until the frame is drawn

Code to do this was recently removed because it was no longer being
used in r241225 (https://codereview.chromium.org/116103002). This is
now necessary again to throttle renderers when using CoreAnimation.

Frames are acked only when they are drawn. Both the CoreAnimation and
the non-CoreAnimation paths are changed to behave this way. By virtue
of the fact that the non-CoreAnimation path draws immediately, this
should have no functional effect on that path.

This differs from the mechanism deleted in the aforementioned patch in
two ways.

First, it uses a scoped_ptr of a struct instead of a vector of pairs to
store the information about the swap being returned. This should improve
readability in that the ack has struct names instead of just first and
second in the pair, and in that the scoped_ptr does not suggest support
for multiple pending swaps (which does not exist).

Second, it does makes RWHVMac ack frames more aggressively when
inside a draw call, rather than adding a call from RWHImpl to the view,
to effect the ack (which is what the old way does).

BUG=340133

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251918 0039d316-1c4b-4281-b951-d872f2087c98
[WebsiteSettings] Set view to null on manager to ensure no stale access.

R=leng@chromium.org, markusheintz@chromium.org
BUG=343234

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=251392

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251919 0039d316-1c4b-4281-b951-d872f2087c98
Inline devtools_discovery_page_resources.grd into browser_resources.grd.

BUG=297672

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251920 0039d316-1c4b-4281-b951-d872f2087c98
Add version info resource to the it2me and me2me native messaging hosts.

BUG=338952,325567

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251921 0039d316-1c4b-4281-b951-d872f2087c98
Don't use nested message loop during EndSession

Previously during EndSession, a nested message loop and a task posted to
the FILE thread that posted a MessageLoop::Quit were used to communicate
that the FILE thread had completed outstanding writes. However, during
shutdown the GPU process might be terminated before the browser has run
through this code. In that case, the GPU process host might process the
"lost context" and try to re-establish (synchronously) a connection with
the GPU process. In this case, Windows can deny the launch of the gpu
process because the window station is terminating. This results in a
browser hang waiting for the GPU, which turns into a crash when the
watchdog timer kills the browser.

To avoid all this, use the same mechanism as Linux -- create a waitable
event and simply have the FILE thread signal it (meaning it's completed
previous writes). By not re-entering a UI-thread message loop, we avoid
having the GPU process host messages get processed.

As a side-benefit, this also means that GPU paint messages are not
processed, which (I think) will avoid the ugliness of sometimes having
sad tabs rendered during shutdown. This could happen because the
renderers are also asynchronously killed during shutdown and so it's a
race between painting the next frame and the browser window being
closed.

R=piman@chromium.org, cpu@chromium.org, darin@chromium.org
BUG=318527,47908,142501

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251922 0039d316-1c4b-4281-b951-d872f2087c98
Fix launching crashed apps from the command line while Chrome is running.

BUG=341820

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251925 0039d316-1c4b-4281-b951-d872f2087c98
Remove duplicated code from sync related unit tests.

Consolidate the various implementations of SyncChangeProcessorDelegate and
fake into sync/api.  Replace many of the fake SyncChangeProcessor
implementations with a slightly more advanced FakeSyncChangeProcessor.

TBR=brettw@chromium.org
BUG=

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

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