Make windowed NPAPI plugins not cover constrained windows in Aura.

Also add more comments to the code that deals with cutout rects, and split the transient window observation into a separate class to make things clearer.

BUG=174121
Review URL: https://codereview.chromium.org/12298007

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@183054 0039d316-1c4b-4281-b951-d872f2087c98
Logs how often users clear Omnibox.

We're interested in the scenario that, a user wanted to use IME in Omnibox, but forgot to turn IME on, or opposite (wanted to not use IME, but forgot to turn IME off).  In these cases, most users realize their mistake just after typing a few characters, which are not what they expected, then delete all the text in Omnibox with backspace key (or escape key), turn IME on/off, and type again what they wanted to input.
We're interested in how often this scenario happens, and would like to see this frequency will reduce as we improve the Omnibox UX for IME users.

This CL adds a histogram named "Omnibox.UserTextCleared" which shows the number of times that users deleted all their input and the number of times that users hit escape key to revert their input.

BUG=172180
TEST=no regression

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@183058 0039d316-1c4b-4281-b951-d872f2087c98
interactive ui tests: Trigger the mouse up/down events after the mouse-move event is complete.

TBR=sky@chromium.org
BUG=none

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@183059 0039d316-1c4b-4281-b951-d872f2087c98
cc: Add raster debug colors to aid in debugging paint problems.

BUG=173567
R=enne@chromium.org


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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@183060 0039d316-1c4b-4281-b951-d872f2087c98
Android ScreenInfo size in DIP instead of device pixels.

So far, Chrome for Android has always passed around screen sizes in
physical device pixels instead of DIPs (density independent pixels).

Most other platforms (e.g. Chrome OS) are sizing everything in DIPs
(except in places like the compositor that actually do painting).
This patch make Chrome for Android also size the screen in DIPs.

This is visible all the way to JavaScript/CSS:
- JS screen.{width,availWidth} and CSS @media device-width
- use: width() and availWidth()
       in third_party/WebKit/Source/WebCore/page/Screen.cpp
  and: device_widthMediaFeatureEval
       in third_party/WebKit/Source/WebCore/css/MediaQueryEvaluator.cpp
- that use: screenRect and screenAvailableRect
            in third_party/WebKit/
               Source/WebCore/platform/chromium/PlatformScreenChromium.cpp
- that use: screenInfo()
            in third_party/WebKit/
               Source/WebKit/chromium/public/WebWidgetClient.h
- implemented by: content/renderer/render_widget.cc
- whose screen_info_ member is initialized by the constructor
- with a value from: GetWebScreenInfo(WebKit::WebScreenInfo* result)
                     in content/browser/renderer_host/render_widget_host_impl.cc
- that uses: GetScreenInfo(WebKit::WebScreenInfo* result)
             in content/browser/renderer_host/render_widget_host_view_android.cc
- that uses: GetDefaultScreenInfo(WebKit::WebScreenInfo* results)
             in content/browser/renderer_host/render_widget_host_view_android.cc
- that before this patch, used: GetDisplayWidth()
                                in ui/gfx/android/device_display_info.cc
                                which called out to JNI
- but after this patch, uses: bounds()
                              in ui/gfx/display.h
- whose bounds_ member is initialized by the constructor
- with a value from: GetPrimaryDisplay()
                     in ui/gfx/screen_android.cc
- which also uses: GetDisplayWidth()
                   in ui/gfx/android/device_display_info.cc
                   but first divides by device_scale_factor

Hence JS screen.{width,availWidth} and CSS @media device-width now
return values in DIPs (which is good) instead of physical device
pixels (which was bad).

Miraculously, this change doesn't seem to have broken anything in
Chrome for Android, though I'm still awaiting the try results ;-)

BUG=168325

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@183061 0039d316-1c4b-4281-b951-d872f2087c98
Make chrome_tests build on Win64 

Just c4267 build suppressions. 

BUG=166496
BUG=167187
TBR=brettw@chromium.org
R=brettw@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@183062 0039d316-1c4b-4281-b951-d872f2087c98
chromeos: Add test for DriveDownloadHandler::CheckForFileExistence

BUG=161181
TEST=unit_tests --gtest_filter="DriveDownloadHandlerTest.CheckForFileExistence"


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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@183063 0039d316-1c4b-4281-b951-d872f2087c98
Revert revisions 183059, 183047 and 183039.

BUG=173235
TBR=sadrul@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@183064 0039d316-1c4b-4281-b951-d872f2087c98
cros: Use /var/run/debugfs_gpu for graphics memory info

The /sys/kernel/debug file system was recently made non-world-readable,
but we've added a bind mount in /var/run for this information. Switch
to the new path.

BUG=175828
TEST=manual, on a device about:discards shows a "Graphics" line at the bottom


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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@183065 0039d316-1c4b-4281-b951-d872f2087c98
Fix more remaining FilePath -> base::FilePath.

This removes the "using" in file_path.h for Mac since Mac now passes trybots with no using. It still leaves the using for Windows.

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@183066 0039d316-1c4b-4281-b951-d872f2087c98
[Cleanup] Files.app: remove an unused argument and a member-variable.

'sensitivity' seems not to used anywhere.

BUG=none
TEST=none
R=mtomasz@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@183069 0039d316-1c4b-4281-b951-d872f2087c98
Files.app: show the warning message when drive authentication is failed.

When authentication is failed on drive, files.app goes offline-mode. This patch adds message to notify that drive is unreachable and encourage user to log out. 

Major changes: 
- Add the private API to logout (fileBrowserPrivate.logout).
- Add the message "Google Drive could not be reached. Please <log out> and log back in."(IDS_FILE_BROWSER_DRIVE_NOT_REACHED).
- Show this message when |OnRefreshKeyInvalid()| is observed.

BUG=160486
TEST=Clear refresh token on drive-internals, and confirm the offline-mode message shows.

R=kinaba@chromium.org, satorux@chromium.org
TBR=asargert@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@183071 0039d316-1c4b-4281-b951-d872f2087c98
net: Split URLFetcherFileWriter from URLFetcherCore

BUG=126753
TEST=net_unittests


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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@183072 0039d316-1c4b-4281-b951-d872f2087c98
Delay the creation of the WebView until after the construction of the RenderViewImpl.

During layout tests, we use a class derived from RenderViewImpl, and therefore
the vtable of the WebViewClient is not yet completely set up during
RenderViewImpl's constructor.

Also change the configuration of the TestRunner library such that it doesn't
try to access the WebView before the RenderViewImpl is completely constructed
and initialized.

BUG=111316
R=jam@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@183073 0039d316-1c4b-4281-b951-d872f2087c98
Fix compilation of WebKitTestRunner

TBR=marja@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@183074 0039d316-1c4b-4281-b951-d872f2087c98
Valgrind: Suppress a couple of Webkit errors and update an IndexDB suppression.

BUG=162829,176616,176619
TBR=timurrrr
NOTRY=true

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@183075 0039d316-1c4b-4281-b951-d872f2087c98
Retry: Fix VirtualPath::GetComponents to handle drive letter string as usual path component

Also fix the function comment as the existing code seems to handle the
'.' component correctly (and so does the new code).

Original review: https://codereview.chromium.org/12253006/

BUG=none
TEST=FileSystemUtilTest.VirtualPathGetComponents
TBR=ericu, tzik (original reviewers)

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@183076 0039d316-1c4b-4281-b951-d872f2087c98
Automated Commit: Committing new LKGM version 3720.0.0 for chromeos.

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@183077 0039d316-1c4b-4281-b951-d872f2087c98
We should not use FilePath::DirName() for sandboxed virtual paths

As well as FilePath::BaseName(). When a virtual path starts with drive-letter-like string like 'a:b' FilePath::DirName() returns 'a:' on Win32.

This is a follow-up patch for https://codereview.chromium.org/12253006/

BUG=176253
TEST=content_browsertests:FileSystemLayoutTest.OpRestrictedChars, content_unittests:FileSystemUtilTest.VirtualPathDirName

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

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

TBR=marja@chromium.org

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

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