This means the nest of native objects (once built up) have the same life-times,
and the mismatch is handled at the JNI boundary.
GC might cause WebContents to get deleted before ContentViewCore (if AwContents is finalized before the java ContentViewCore)
BUG=
Review URL: https://chromiumcodereview.appspot.com/11067002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@162052 0039d316-1c4b-4281-b951-d872f2087c98
This implements the host side of the sync ppapi function EnumerateVideoCaptureDevices.
BUG=none
TEST=Wrote a sample that runs the sync and non-sync versions. Ran it and compared the outputs.
Review URL: https://chromiumcodereview.appspot.com/11016007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@162048 0039d316-1c4b-4281-b951-d872f2087c98
This will help us diagnose corruption in the wild.
BUG=140543
Review URL: https://codereview.chromium.org/11098057
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@162016 0039d316-1c4b-4281-b951-d872f2087c98
If we navigate to 'http://www.google.com', then navigate to '' (empty src), reading <browser>.src would now give us (expected) 'http://www.google.com' since we ignore setting empty src attribute in browser_plugin.cc.
BUG=149001
TEST=In web inspector, setting src on <browser> element and reading it.
Added platform app test for verifying the change.
Ran content_browsertests for BrowserPluginTest* and BrowserPluginHostTest*
Review URL: https://chromiumcodereview.appspot.com/11111020
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@162011 0039d316-1c4b-4281-b951-d872f2087c98
The hope for this refactor is that adding new bindings will be
easier since the code will be isolated in one place. Stylewise,
this is consistent with other parts of chrome too (chrome
extension functions are somewhat similarly defined, for example).
BUG=none
Review URL: https://codereview.chromium.org/11116003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@162010 0039d316-1c4b-4281-b951-d872f2087c98
Guests don't recover from crashes very well. Basically, the only
actions that would properly recover the browser plugin from crash
is the reload method and setting the src attribute. This change
moves the resetting of the guest_crashed_ flag to UpdateRect in order
to make crash recovery more robust. If we're receiving new pixels from
guests, then we can assume that the guest has recovered from a crash.
BUG=155324
Test=BrowserPluginHostTest.BackAfterTerminateGuest
Review URL: https://chromiumcodereview.appspot.com/11094080
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161986 0039d316-1c4b-4281-b951-d872f2087c98
Panel fitting is used by mirror display mode on Chrome OS.
This GPU feature type will tell if it is supported by GPU hardware.
Initially enable it only for Ivy Bridge GPU via blacklisting everything else.
Also add a disable_panel_fitting command flag,
to be able to quickly turn the feature off.
When hardware supports panel fitting,
and there are no common modes between the internal and the external displays,
configure the internal display to the external's resolution,
and let the panel fitter take care of displaying it correctly.
BUG=chromium-os:34442
TEST=Panel Fitting should appear as Hardware Accelerated in about:gpu
on IVB Chrome OS, Unavailable everywhere else.
TEST=Tested mirror mode on device.
Review URL: https://chromiumcodereview.appspot.com/10909242
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161980 0039d316-1c4b-4281-b951-d872f2087c98
Avoid needlessly expensive scanning of system call ranges.
This CL improves how we deal with discontiguous ranges of system call numbers.
(Original CL by markus@chromium.org)
TEST=sandbox_linux_unittests on x86_64 and ARM
BUG=148856
Review URL: https://chromiumcodereview.appspot.com/11096012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161943 0039d316-1c4b-4281-b951-d872f2087c98
Move the perf test events to use START/FINISH TraceEvent paths, which will work properly
if they are not triggered in the right nested order.
BUG=http://crbug.com/150584
Review URL: https://chromiumcodereview.appspot.com/11090082
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161942 0039d316-1c4b-4281-b951-d872f2087c98
This is also needed to make it possible for content_shell and test_shell
to use mobile as user agent. Some methods and files had to be moved out of chrome
to be able to use them in content_shell
BUG=152807,154122
Review URL: https://chromiumcodereview.appspot.com/11066087
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161933 0039d316-1c4b-4281-b951-d872f2087c98
This tells the client that it should schedule a composite operation
(i.e. during next vsync signal).
Review URL: https://codereview.chromium.org/11108004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161887 0039d316-1c4b-4281-b951-d872f2087c98
- Add new MediaObserver method to enable new tab capture chrome extension API's to be notified of stream request changes for Tab type streams.
- Adds constants for chrome-specific MediaStreamConstraints: mediaSource and mediaSourceId to be used to request video/audio streams with tab media.
- Plumbing/Tweaks to GenerateStreamForDevice for the API to work.
Dependent change: http://codereview.chromium.org/11038021
BUG=153388
Review URL: https://chromiumcodereview.appspot.com/10928043
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161881 0039d316-1c4b-4281-b951-d872f2087c98
In single-process mode, WebKit isn't yet initialized before we start a renderer, so we can't pass around WebURLs
BUG=111316
TEST=content_shell --dump-render-tree --single-process doesn't crash
Review URL: https://codereview.chromium.org/11137015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161879 0039d316-1c4b-4281-b951-d872f2087c98
It seems that some pages attempt to enable accelerated compositing in guests
even if the force-compositing-mode flag is disabled. As the browser tag does
not yet currently support accelerated compositing, these pages fail to update
the browser plugin's backing store.
Setting the accelerated_compositing_enabled flag to false seems to solve
this problem.
BUG=152568
Review URL: https://chromiumcodereview.appspot.com/11118028
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161864 0039d316-1c4b-4281-b951-d872f2087c98
The check is added since BlobData has expected_modification_time field.
Add tests (mostly copied from LocalFileStreamReaderTest).
BUG=141835
TEST=content_unittests --gtest_filter="FileSystemFileStreamReaderTest.*"
TBR=jam@chromium.org
Review URL: https://chromiumcodereview.appspot.com/11098067
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161853 0039d316-1c4b-4281-b951-d872f2087c98
Even though content shell and DumpRenderTree can use sample dictionaries in 'third_party/hyphen', Chrome cannot use them and it needs to use dictionaries downloaded to 'chrome::DIR_APP_DICTIONARIES'. This change adds the ContentBrowserClient::GetHyphenDictionaryDirectory function so Chrome can change the directory to 'chrome::DIR_APP_DICTIONARIES' and read hyphenation dictionaries from the directory.
BUG=47083
TEST=none
Review URL: https://chromiumcodereview.appspot.com/11036054
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161845 0039d316-1c4b-4281-b951-d872f2087c98
In single-process mode, WebKit isn't yet initialized before we start a renderer,
so we can't pass around WebURLs
BUG=111316
TEST=content_shell --dump-render-tree --single-process doesn't crash
Review URL: https://codereview.chromium.org/11151007TBR=jochen@chromium.org
Review URL: https://codereview.chromium.org/11143013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161844 0039d316-1c4b-4281-b951-d872f2087c98
In single-process mode, WebKit isn't yet initialized before we start a renderer,
so we can't pass around WebURLs
BUG=111316
TEST=content_shell --dump-render-tree --single-process doesn't crash
Review URL: https://codereview.chromium.org/11151007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161839 0039d316-1c4b-4281-b951-d872f2087c98
Also add an explicit dependency from content_shell to osmesa
BUG=111316
TEST=content_shell --dump-render-tree still works after a clobber build
Review URL: https://codereview.chromium.org/11144012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161832 0039d316-1c4b-4281-b951-d872f2087c98
Flash has some third-party code which depends on additional
environment settings over what we pass to ICU.
BUG=155396,134911
Review URL: https://chromiumcodereview.appspot.com/11116008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@161813 0039d316-1c4b-4281-b951-d872f2087c98
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
