content/public/test/content_test_suite_base.cc includes media/base/media.h
but its gyp file is missing media.gyp dependency. This is a spin-off CL from
11075006.
BUG=
Review URL: https://chromiumcodereview.appspot.com/11066124
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161800 0039d316-1c4b-4281-b951-d872f2087c98
When a texture is returned via ReusePictureBuffer(), we know
that it has been inserted into command stream, but it may not
have been read out yet.
This inserts an EGL sync object into the GPU command stream.
All commands that have already been in the stream at the time
of insertion are finished when the object is signaled,
thus guaranteeing that the commands to read out the texture
have been finished. The texture will be reused for decoding
after the object has been signaled.
BUG=155602
Review URL: https://chromiumcodereview.appspot.com/11076009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161759 0039d316-1c4b-4281-b951-d872f2087c98
- Set active root window early when creating browsers on startup.
- Send screen info when device scale factor chagned.
- gfx::Screen::GetDisplayNearestWindow should return Primary when the window's root doesn't exist. I missed this condition in https://chromiumcodereview.appspot.com/10961021
BUG=155201, 152728
TEST=manual: see bug for repro steps
Review URL: https://chromiumcodereview.appspot.com/11066130
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161758 0039d316-1c4b-4281-b951-d872f2087c98
the swap-buffers calls (which get issued anyway, when in FCM).
This patch has most of the contents of: https://codereview.chromium.org/10914247 except that it doesn't change any of the field trial probabilities.
It fixes the following tests: Canvas2DDisabled, Canvas2DBlocked, WebGLBLocked, WebGLDisabled, AcceleratedCompositingDisabled,
AcceleratedCompositingBlocked .
It also disables ExtensionApiTest.CaptureVisibleTabJPeg as it triggers flakiness on it. chrome.tabs.captureVisibleTab is inherently racy as there is no way to guarantee that the tab has been painted at least once when that call is made. Note how the other variants of CaptureVisibleTab tests have already been disabled for similar reasons. (this was done with aa@'s advice)
BUG=155336
Review URL: https://chromiumcodereview.appspot.com/11091072
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161733 0039d316-1c4b-4281-b951-d872f2087c98
Simplifies the content/ layer by not having to know about the webkit.DownloadListener interface.
BUG=
Review URL: https://chromiumcodereview.appspot.com/11139003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161727 0039d316-1c4b-4281-b951-d872f2087c98
This allows external users to request that a render view show a context menu. This mostly exposes is a reaonsable interface the existing functionality, and removes the pepper-plugin-delegate-specific hacks.
Review URL: https://codereview.chromium.org/11083002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161703 0039d316-1c4b-4281-b951-d872f2087c98
It appears that we've been hitting this limit again,
presumably in the "fork" command. This will hopefully give
us more headroom (a previous change makes us crash when we
hit the limit).
BUG=154409
Review URL: https://codereview.chromium.org/11092109
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161676 0039d316-1c4b-4281-b951-d872f2087c98
This adds CHECKs to the browser if it attempts to send a
message to the zygote that exceeds the maximum message size
(which causes an EMSGSIZE error in the zygote) or that
contains too many file descriptors.
I'm hoping that this will help make the source of the
problem more apparent when we hit the message size limit,
which we appear to have done multiple times (it was
originally 1 KB and is now 2 KB).
BUG=154409
Review URL: https://chromiumcodereview.appspot.com/11108019
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161645 0039d316-1c4b-4281-b951-d872f2087c98
This is in support of supporting separate Screen implementations on Aura for desktop and metro on Windows.
Some callsites are not yet correct, and noted with a reference to the http://crbug.com/133312. As-is those sites will behave the same as before this patch, but may not be correct once desktop/metro can run simultaneously.
BUG=133312
Review URL: https://chromiumcodereview.appspot.com/11030017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161644 0039d316-1c4b-4281-b951-d872f2087c98
BUG=111316
TEST=compositing/iframes/iframe-in-composited-layer.html does not time out
Review URL: https://chromiumcodereview.appspot.com/11116013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161634 0039d316-1c4b-4281-b951-d872f2087c98
This patch change IOKit notification to use AudioObjectAddPropertyListener on kAudioHardwarePropertyDevices. By doing so, we will get notification after the driver initializes the devices.
BUG=153411
TEST= manual test with Pepper flash device enumeration.
Review URL: https://chromiumcodereview.appspot.com/11106013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161594 0039d316-1c4b-4281-b951-d872f2087c98
This is the first half of the change, the second half will send the parent frame id with the webNavigation events
See RenderViewImpl::willSendRequest when it creates the RequestExtraData for a place where we already send the parent frame id (this is for the webRequest API that looks at network requests instead of navigation events)
BUG=128927
TEST=FrameNavigationState.*
Review URL: https://chromiumcodereview.appspot.com/11090068
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161570 0039d316-1c4b-4281-b951-d872f2087c98
This will catch patterns like if ('foo' in window.testRunner)
BUG=111316
TEST=animations/longhand-timing-function.html doesn't time out
Review URL: https://codereview.chromium.org/11110011
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161554 0039d316-1c4b-4281-b951-d872f2087c98
Having both frameForEnteredContext and frameForCurrentContext in the API is too
confusing. Code seems to randomly pick one or the other to call. Almost
everyone wants to call frameForCurrentContext, so this patch removes all the
callers of frameForEnteredContext. Soon we'll remove frameForEnteredContext
from the API entirely.
Review URL: https://chromiumcodereview.appspot.com/11111004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161521 0039d316-1c4b-4281-b951-d872f2087c98
ContentViewCore methods are unaccessible from other packages that
need to hook it to the View containers of their choice.
BUG=146570
Review URL: https://chromiumcodereview.appspot.com/11092094
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161505 0039d316-1c4b-4281-b951-d872f2087c98
Switch from posting file operations on the file thread to posting them
on the blocking worker pool. Previous instrumentation indicated that
this reduces hung-plugin infobars by around 20%.
BUG=153383
Review URL: https://chromiumcodereview.appspot.com/11093059
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161459 0039d316-1c4b-4281-b951-d872f2087c98
On windows, chrome used to switch between raw-touch and gesture modes depending on
whether the touch-start event was processed by the renderer or not. But now, the
switch happens iff touch-events is enabled (using command-line flag) on appropriate
version of windows. So cleanup the relevant code.
BUG=138153
TBR=avi@chromium.org (content/port/)
Review URL: https://codereview.chromium.org/11028144
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161458 0039d316-1c4b-4281-b951-d872f2087c98
This allows dragging content from within the embedder (or other windows) into
the browser-tag plugin.
BUG=120264
Review URL: https://codereview.chromium.org/11088043
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161457 0039d316-1c4b-4281-b951-d872f2087c98
Also, for each such shared library included in an apk, create a link in
the appropriate directory in <(android_product_out) to enable annotating
native stack traces for those apks.
BUG=
Review URL: https://chromiumcodereview.appspot.com/11096038
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161440 0039d316-1c4b-4281-b951-d872f2087c98
This change allows you to call a function that expects a floating point
object with an integer object and have things just work. The addition
operator for Points is outside the Point classes so it can add/subtract integer
and float points together implicitly.
Tested to verify compilation with:
ui_unittests:RectTest.ToRectF
ui_unittests:SizeTest.ToSizeF
ui_unittests:PointTest.ToPointF
BUG=147395
R=sky@chromium.org
Review URL: https://chromiumcodereview.appspot.com/11028127
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161415 0039d316-1c4b-4281-b951-d872f2087c98
createPluginReplacement and didCreateScriptContext is no longer
in WebKit::WebFrameClient or called anywhere else. Removing them.
numberOfWheelEventHandlersChanged and hasTouchEventHandlers are
overriding methods from WebKit::WebViewClient. Moving them up.
Review URL: https://chromiumcodereview.appspot.com/11094062
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161384 0039d316-1c4b-4281-b951-d872f2087c98
This change makes sure deviceScalefactor is initialized consistently with the deviceInfo
value.
BUG=136745
Review URL: https://chromiumcodereview.appspot.com/11087067
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161365 0039d316-1c4b-4281-b951-d872f2087c98
Adds browser_main_loop.cc to the build on iOS and ifdefs out the parts that are
not supported on iOS.
Review URL: https://chromiumcodereview.appspot.com/11087007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161362 0039d316-1c4b-4281-b951-d872f2087c98
The one difference is to check if ResourceBundle is initialized before initializing it. This is needed because on content_browsertests it's not initialized while in browser_tests it is. We can't make the two browser test binaries behave the same because of differences in how chrome's browser_tests and unit_tests can share the same test suite while in content that's not possible.
TBR=cpu
Review URL: https://codereview.chromium.org/11091058
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161361 0039d316-1c4b-4281-b951-d872f2087c98
When AwSettings.getAllowFileAccess returns false, data URIs loaded with a non-data base URL should be able to access file:///android_asset and file:///android_res/, but not the wider filesystem.
We grant the WebView process access to file:// via ChildProcessSecurityPolicy (as WebView is single process we do this on process startup) and add a field to ViewMsg_NavigateParams that indicates if the URL being loaded should have access to local loads. This is bit is checked when the provisional load commits and if set, grants the SecurityOrigin access to local resources. The bit defaults to false and is only set in android_webview when AwContents loads a data URL with a non-data base URL, so there should be no behavior change outside of android_webview.
Once the SecurityOrigin allows local loads, code already present in android_webview controls whether the URL should be able to load either only android_asset and android_res or any file:// URL (see https://codereview.chromium.org/11090003/).
[1]
http://developer.android.com/reference/android/webkit/WebView.html#loadDataWithBaseURL(java.lang.String,
java.lang.String, java.lang.String, java.lang.String, java.lang.String)
BUG=152223
Review URL: https://codereview.chromium.org/10990056
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161355 0039d316-1c4b-4281-b951-d872f2087c98
This patch upstreams code to display text selection handles in the Android
content shell. While in selection mode, we also display an action bar with
editing commands; I have stubbed this out because we don't yet have the
necessary resources (added a TODO for that).
BUG=138468
TEST=none
Review URL: https://chromiumcodereview.appspot.com/11068010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161353 0039d316-1c4b-4281-b951-d872f2087c98
This is now configured in the ShellURLRequestContext
BUG=111316
TEST=none
Review URL: https://chromiumcodereview.appspot.com/11093069
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161337 0039d316-1c4b-4281-b951-d872f2087c98
