| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
This reduces one more dependency on webkit from chrome.
BUG=146251
R=jam@chromium.org,ben@chromium.org
TBR=darin@chromium.org,tsepez@chromium.org
Review URL: https://codereview.chromium.org/12036003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@178082 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
It can be copyable but making it copyable makes it difficult to track
which context settings each operation is using.
BUG=none
TEST=green builds
Review URL: https://codereview.chromium.org/12036020
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177980 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now that WebTransformOperations is virtual, this removes code behind
the #else branches of "#if WEB_TRANSFORM_OPERATIONS_IS_VIRTUAL".
This is step 3 of the 3-step plan outlined at
https://chromiumcodereview.appspot.com/11745018 for moving the
implementation of WebTransformOperations into chromium.
BUG=166640
Review URL: https://chromiumcodereview.appspot.com/12047006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177962 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://codereview.chromium.org/12035002/ made the hyphen dictionary lookup
code more robust, but it introduced a relative path in the process, which
no longer work since https://codereview.chromium.org/11782005/ .
https://codereview.chromium.org/12038003 fixed this in a special case. This
change makes that fix more general.
BUG=none
TEST=hyphenate-*.html tests on build.webkit.org turn green.
TBR=tkent
Review URL: https://codereview.chromium.org/12039014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177956 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://bugs.webkit.org/show_bug.cgi?id=107468
It looks like the exact same problem happened when this landed the last time:
https://bugs.webkit.org/show_bug.cgi?id=105813
Please make sure this issue is fixed before you reland.
The CL also likely regressed binary size by 0.25MB: http://crbug.com/171143
> Add wrapper class to media for support of VP9 video, and add a command line flag to enable the support.
>
> This initial version of the wrapper provides support for decoding VP9 video in WebM container files, and is disabled by default.
>
> New flag added: --enable-vp9-playback
>
> TBR=brettw,scherkus,xhwang
> BUG=166094
> TEST=VP9 video in WebM containers plays back in <video> elements when --enable-vp9-playback is specified on the command line.
>
>
> Review URL: https://chromiumcodereview.appspot.com/12025030
TBR=tomfinegan@chromium.org
Review URL: https://codereview.chromium.org/11953017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177953 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
DIR_SOURCE_ROOT returns unreliable results in standalone WebKit checkouts,
to not introduce a layering violation in base (see
https://codereview.chromium.org/8585029/). Make the code that relies on it
more robust to handle the unreliable results.
BUG=171146
TEST=fast/text/hyphens.html passes in a standalone webkit/chromium/mac build
when using ninja.
TBR=tony
Review URL: https://codereview.chromium.org/12035002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177952 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
It doesn't seem necessary as it's only set within the class.
BUG=none
TEST=none
Review URL: https://chromiumcodereview.appspot.com/12043003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177932 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Chromium revision r175642 broke the webkit unit tests at webkit.org
http://wkb.ug/106631 because GetWebKitRootDir() returns a file path
that contains a relative "../.." component on some webkit bots.
Make webkit_support::GetWebKitRootDir() return an absolute path.
TEST=webkit unit tests pass
BUG=http://wkb.ug/106631
Review URL: https://chromiumcodereview.appspot.com/12038003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177931 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=54309
TEST=LocalFileSystemOperationTest.TestReadDirFailure,ObfuscatedFileUtilTest.TestReadDirectoryOnFile
Review URL: https://chromiumcodereview.appspot.com/11953011
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177921 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=164370
TEST=browser_tests:*UDPSocketPrivate*
Review URL: https://chromiumcodereview.appspot.com/11441012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177915 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
flag to enable the support.
This initial version of the wrapper provides support for decoding VP9 video in WebM container files, and is disabled by default.
New flag added: --enable-vp9-playback
TBR=brettw,scherkus,xhwang
BUG=166094
TEST=VP9 video in WebM containers plays back in <video> elements when --enable-vp9-playback is specified on the command line.
Review URL: https://chromiumcodereview.appspot.com/12025030
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177842 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Taking over from Victor's CL: https://codereview.chromium.org/11419131/
Re-landing, with a fix. The original waited to reset the file state until
after the callback had completed. This is too late, as the client should be
able to perform another file operation during the callback.
Changeset #1 is the original patch. The fix is in change set #2
Original author=Victor Hsieh
BUG=none
TEST=browser_tests --gtest_filter=PPAPINaClNewlibTest.FileIO*
Review URL: https://chromiumcodereview.appspot.com/11941022
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177830 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test plugin is needed by several browser and content
tests. The missing plugin was causing these to fail
on the ARM linux bot. This change enables the plugin
for ARM in general (e.g. chromeos and linux) while leaving
it disabled for android and ios builds.
BUG=169810,169813
Review URL: https://chromiumcodereview.appspot.com/11931003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177827 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
There were a few cases where a file system operation went unused.
BUG=169675
Review URL: https://chromiumcodereview.appspot.com/11969034
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177792 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
that were moved to a different directory
Review URL: https://chromiumcodereview.appspot.com/11946050
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177695 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
again between tests. Introduces a ResetTestEnvironment method
to webkit_support, which is intended to be called by DRT's
TestShell::resetTestController method.
ResetTestEnvironment subsumes the Android-specific ReleaseMediaResources
method.
Review URL: https://chromiumcodereview.appspot.com/11946027
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177629 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
This should green interactive_ui_tests on Win and CrOS.
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177624 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
This does not do anything yet.
BUG=170000
Review URL: https://chromiumcodereview.appspot.com/11885035
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177610 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/11938009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177602 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
Platform directory
Review URL: https://chromiumcodereview.appspot.com/11880041
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177581 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Move mount point info bookeeping from CrosMountPointProvider to ExternalMountPoints.
Add some tests for CrosMountPointProvider.
BUG=158837
TEST=content_unittests:CrosMountPointProvider*
TBR=benwells@chromium.org
Review URL: https://chromiumcodereview.appspot.com/11648027
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177578 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Revert "Revert 177288"
TBR=ilevy@chromium.org
This reverts commit 3543975945a5667aa3fb48c6d0e1b6312d1ed293.
BUG=168927
Review URL: https://chromiumcodereview.appspot.com/11902005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177541 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In short:
* Zero-sized buffers are now permitted (they're harmless)
* The buffer copying constructor has been made private and CopyFrom() has been introduced
* End of stream buffers must be explicitly created via CreateEOSBuffer()
* DCHECKs added to forbid calling DataBuffer methods on end of stream buffers
TBR=dmichael
Review URL: https://codereview.chromium.org/11902003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177525 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=151679
TEST=none
Review URL: https://chromiumcodereview.appspot.com/11297002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177517 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=111316
R=tsepez@chromium.org,tony@chromium.org,jam@chromium.org
Review URL: https://chromiumcodereview.appspot.com/11969043
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177509 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
> cc: Add point-based UV coordinate on TextureLayer
>
> Previously, the uv coordinates was using gfx::RectF as a struct.
> This was limitating because it could not handle negative width
> and heights. Soring them as 2 gfx::PointF for the Top-Left and
> Bottom-Right points aleviate that restriction.
> The current implementation of the phone UI rely on this feature.
>
> BUG=168927
>
> Review URL: https://chromiumcodereview.appspot.com/11783094
This is breaking the android internal chrome build, we need green for
a release cut later tonight. Let's reland tomorrow with the
corresponding downstream fix.
TBR=jscholler@chromium.org
Review URL: https://codereview.chromium.org/11959026
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177360 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. To save unnecessary calls
2. To make it more explicit what FileUtil calls we're making in cross Copy/Move operations
BUG=146215
TESTS=existing tests should pass
Review URL: https://codereview.chromium.org/11973007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177345 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some PPB interfaces have methods that set a custom callback. Usually, the callback has to be called on the same thread as the one it was set on. ThreadAwareCallback keeps track of the target thread, and posts a task to run on it if requested from a different thread.
BUG=None
TEST=newly added unittests.
Review URL: https://chromiumcodereview.appspot.com/11859015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177319 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
This ports the implementation of WebTransformOperations into cc::TransformOperations, Also, behind #if WEB_TRANSFORM_OPERATIONS_IS_VIRTUAL, this makes cc use TransformOperations instead of WebTransformOperations; defines a new class WebTransformOperationsImpl that implements WebTransformOperations using an instance of cc::TransformOperations; defines WebCompositorSupportImpl::createTransformOperations; and makes compositor_bindings use WebTransformOperationsImpl instead of WebTransformOperations (extracting the underlying cc::TransformOperations before calling into cc).
This is step 1 of the 3-step plan outlined at https://chromiumcodereview.appspot.com/11745018 for moving the implementation of WebTransformOperations into chromium.
BUG=166640
Review URL: https://chromiumcodereview.appspot.com/11876016
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177290 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, the uv coordinates was using gfx::RectF as a struct.
This was limitating because it could not handle negative width
and heights. Soring them as 2 gfx::PointF for the Top-Left and
Bottom-Right points aleviate that restriction.
The current implementation of the phone UI rely on this feature.
BUG=168927
Review URL: https://chromiumcodereview.appspot.com/11783094
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177288 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Caused PP_ERROR_INPROGRESS when used from within Native Client.
> Refactor FileIO to the new resource host system.
> Taking over from Victor's CL: https://codereview.chromium.org/11419131/
>
> GetOSDescriptor is done by passing raw file descriptor via in-process messaging.
>
> Operations are kept exclusive, but the restriction can be easily removed if needed.
>
> Original author=Victor Hsieh
> BUG=
> TEST=browser_tests --gtest_filter=PPAPINaClNewlibTest.FileIO*
>
> Review URL: https://chromiumcodereview.appspot.com/11824039
TBR=bbudge@chromium.org
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177287 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Spin the message loop, in case an asynchronous cache load is waiting
* Clear the memory cache when unregistering mocked urls.
BUG=170171
TEST=Everything stays green, webkit bug 105667 will use this soon
Review URL: https://chromiumcodereview.appspot.com/11940002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177276 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: https://chromiumcodereview.appspot.com/11939002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177243 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
Review URL: https://codereview.chromium.org/11958006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177240 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
from WebKit/chromium/public/platform to Platform/chromium/public
Review URL: https://chromiumcodereview.appspot.com/11931019
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177203 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
from WebKit/chromium/public/platform to Platform/chromium/public
Review URL: https://chromiumcodereview.appspot.com/11961018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177199 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Now that we have common base::PostTaskAndReplyWithResult helper method
it doesn't seem necessary anymore.
BUG=none
Review URL: https://chromiumcodereview.appspot.com/11946014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177198 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These tests don't depend on webkit/tools/test_shell/test_shell_test.h
and can be moved to content_unittests.
Some tests were relying on the MessageLoop created by TestShell. I've
updated them to create their own MessageLoop.
BUG=126514
Review URL: https://chromiumcodereview.appspot.com/11883022
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177180 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
It's the only way to be sure...
... he doesn't get android code reviews.
Review URL: https://codereview.chromium.org/11968018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177174 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
directory
Review URL: https://chromiumcodereview.appspot.com/11883031
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177153 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
directory
Review URL: https://chromiumcodereview.appspot.com/11887028
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177152 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
FileUtilProxy::Write makes a copy of the data before posting the write job, and it is one of the bottlenecks of the write operation on pepper.
Though, we can safely omit the copy in QuotaFileIO::Write.
BUG=168744
Review URL: https://chromiumcodereview.appspot.com/11615036
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177125 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Provides a means for keeping the top controls in sync with the currently
renderered frame, which will allow us to move the top controls around the
screen.
BUG=161303
Review URL: https://chromiumcodereview.appspot.com/11552009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177081 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
| |
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177080 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The method sends the render passes it is given to the parent compositor via
the output surface. It should include a valid frame metadata with it.
Tests:
DelegatingRendererTestDraw.runSingleThread
DelegatingRendererTestDraw.runMultiThread
DelegatingRendererTestResources.runSingleThread
DelegatingRendererTestResources.runMultiThread
R=piman
BUG=123444
Review URL: https://codereview.chromium.org/11777025
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177073 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The cause is that IsValid32BitImage fails if passed a relative path
afaik this comes from registry entries but could be other sources. Now
we make the path absolute before calling this function.
In addition we now have pepper plugins so avoid doing all the npapi compat
checks on them, which includes disk IO!!
The other change is fix faulty logic in the loop IsValid32BitImage
which due to the 'break' never tested what it meant to test which
is the plugin belonging to the internal plugin list, now this check
is also done earlier, so more disk IO avoided.
The rest is just giving this file a bit of love:
- remove many "plugin" strings all over the place
- change wstring to string16
- tidy up the namespaces
BUG=169160
TEST=see bug
Review URL: https://codereview.chromium.org/11883021
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@177023 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: https://chromiumcodereview.appspot.com/11887029
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@176988 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
media::DataBuffer.
It was never a good idea in the first place.
Our usage is exclusively with DecoderBuffers or DataBuffers. There's never a case where we benefit from using Buffer as a base class aside from hiding GetWriteableData(), however it's not a compelling enough reason to keep Buffer around.
BUG=169614
TBR=dmichael
Review URL: https://codereview.chromium.org/11880008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@176956 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Revert 176846
> Explicitly initialize the IDB Factory after resetting webkit_platform_support, because upstream WebKit will soon require all embedders to do this.
>
> Review URL: https://chromiumcodereview.appspot.com/11878023
TBR=pilgrim@chromium.org
Review URL: https://codereview.chromium.org/11916007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@176954 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: https://chromiumcodereview.appspot.com/11886036
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@176922 0039d316-1c4b-4281-b951-d872f2087c98
|