GitLab

This change reverts necessary changes in patch
http://crrev.com/413983002 which was needed to successfully rename
WebAnimation to WebCompositorAnimation.

This is the patch 4 of 4 and follows on from http://crrev.com/412123002 

BUG=396358

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

Cr-Commit-Position: refs/heads/master@{#290729}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290729 0039d316-1c4b-4281-b951-d872f2087c98

We'll use this under ChromeOS ozone/freon builds for keyboard layout
support.

BUG=362698
TEST=ran install-build-deps.sh on trusty

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

Cr-Commit-Position: refs/heads/master@{#290727}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290727 0039d316-1c4b-4281-b951-d872f2087c98

BUG=405076
TEST=none

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

Cr-Commit-Position: refs/heads/master@{#290725}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290725 0039d316-1c4b-4281-b951-d872f2087c98

Cr-Commit-Position: refs/heads/master@{#290724}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290724 0039d316-1c4b-4281-b951-d872f2087c98

http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog_blink.html?url=/trunk&range=180601:180609&mode=html
TBR=mkwst@chromium.org,dglazkov@chromium.org
BUG=

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

Cr-Commit-Position: refs/heads/master@{#290723}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290723 0039d316-1c4b-4281-b951-d872f2087c98

Video recording allows sequences of frames to be recorded and delivered
to the client for performance-evaluation purposes. The client can save
recorded sequences out to files on disk. Since live playback is not a
requirement, performance of the implementation is not a priority.

See crrev.com/372943002 for the host side of this.

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

Cr-Commit-Position: refs/heads/master@{#290721}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290721 0039d316-1c4b-4281-b951-d872f2087c98

NOTRY=true

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

Cr-Commit-Position: refs/heads/master@{#290720}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290720 0039d316-1c4b-4281-b951-d872f2087c98

For now this uses extensions_unittests_main.cc as there are no differences
in startup between extensions_unittests and app_shell_unittests.

This allows ShellNaClBrowserDelegate to have a test.

BUG=402612
TEST=app_shell_unittests

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

Cr-Commit-Position: refs/heads/master@{#290719}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290719 0039d316-1c4b-4281-b951-d872f2087c98

This CL (1) handles the case that Array<>'s element number or total size exceeds what we can represent in Mojo messages; (2) makes the validation code of the num_bytes field doesn't rely on sizeof(size_t) > sizeof(uint32_t).

The newly-added test passes with/without this CL. But I think it is good to have such a test.

BUG=None
TEST=None

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

Cr-Commit-Position: refs/heads/master@{#290718}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290718 0039d316-1c4b-4281-b951-d872f2087c98

Cr-Commit-Position: refs/heads/master@{#290717}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290717 0039d316-1c4b-4281-b951-d872f2087c98

This picks up a new version of the web-platform-tests repo that
does not contain the tests in the
custom-elements/registering-custom-elements/unresolved-element-pseudoclass
directory. Those tests were causing us to hit path length limits on the
windows bots.

TBR=tonyg@chromium.org, rschoen@chromium.org
BUG=405274

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

Cr-Commit-Position: refs/heads/master@{#290716}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290716 0039d316-1c4b-4281-b951-d872f2087c98

This add an window.ipcEcho API that sends do-nothing IPC 
message to measure RTT. The API is behind a flag, 
and will be used to build IPC benchmark using JavaScript.

TEST=none (Will add blink-side LayoutTest once this is landed)
BUG=402185
R=darin@chromium.org, jam@chromim.org, jochen@chromium.org

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

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

Cr-Commit-Position: refs/heads/master@{#290715}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290715 0039d316-1c4b-4281-b951-d872f2087c98

For release, looking at the stats pages the two testers for each config should be roughly equal. For debug, it appears that this simplified configuration will make the second tester ~10 minutes slower than the first one. However they should still cycle faster the current config on the new machine.

This rebalancing should hopefully be a temporary step until we use swarming for the main waterfall.

BUG=373847
NOTRY=true

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

Cr-Commit-Position: refs/heads/master@{#290714}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290714 0039d316-1c4b-4281-b951-d872f2087c98

Flaky on Mac as well. Disabling.

TBR=tonyg@chromium.org
NOTRY=True
BUG=384733

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

Cr-Commit-Position: refs/heads/master@{#290713}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290713 0039d316-1c4b-4281-b951-d872f2087c98

BUG=393873
R=tbreisacher@chromium.org,dbeam@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#290712}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290712 0039d316-1c4b-4281-b951-d872f2087c98

'debugger' only references browser code, so I think this was always
in the wrong place (probably my mistake from a while back when we split
the DLLs).

There are other places where browser depends on debugger already.

R=sky@chromium.org
BUG=404809

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

Cr-Commit-Position: refs/heads/master@{#290711}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290711 0039d316-1c4b-4281-b951-d872f2087c98

Since the Tracer factory is implemented within gpu_tracer, it is simpler
to have the GPUTracer be a flat class rather than implementing
the noop behavior in a different object through inheritance. This CL
does not change any functionality but simply flattens GPUTracer and
combines the code for GPUTracerImpl and GPUTracerARBTimerQuery.

BUG= https://code.google.com/p/chromium/issues/detail?id=397294
TEST= trybots

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

Cr-Commit-Position: refs/heads/master@{#290710}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290710 0039d316-1c4b-4281-b951-d872f2087c98

This change introduces ServiceWorkerRegistrationObjectInfo which carries
'handle_id' and 'scope' for ServiceWorkerRegistration object in the renderer
side over the IPC message, and removes unnecessary reference counting for
ServiceWorker object on the registration sequence.


BUG=384119, 396400
TEST=content_unittests --gtest_filter=ServiceWorker*
TEST=run_webkit_tests.py --debug http/tests/serviceworker

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

Cr-Commit-Position: refs/heads/master@{#290709}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290709 0039d316-1c4b-4281-b951-d872f2087c98

- Was loading thumbnails in little endian, but since the files were from java's
output stream they were in big endian.  This was causing all sorts of issues
with old thumbnails.
- Added back ETC1 header and fixed the file format to match the old version.

BUG=398319

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

Cr-Commit-Position: refs/heads/master@{#290708}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290708 0039d316-1c4b-4281-b951-d872f2087c98

It used to be that CreateEntropyProvider() was only
called once in a process, during the init sequence,
and then never again. So previously, these DCHECKs
could never fire by virtue of the function always
being called once.

Now that this function is called by VariationsService
when simulating new variations seeds, it will be
called multiple times during the process life time.
It's perfectly valid to return an entropy provider
that uses a different entropy source in that context
(e.g. post changing your UMA opt-in setting), since
that's exactly what the simulation code wants (i.e.
it simulates what will happen on a restart).

So simply remove the checks, since their conditions
no longer hold.

BUG=405010

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

Cr-Commit-Position: refs/heads/master@{#290706}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290706 0039d316-1c4b-4281-b951-d872f2087c98

Cr-Commit-Position: refs/heads/master@{#290702}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290702 0039d316-1c4b-4281-b951-d872f2087c98

http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog_blink.html?url=/trunk&range=180550:180600&mode=html
TBR=mkwst@chromium.org,dglazkov@chromium.org
BUG=

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

Cr-Commit-Position: refs/heads/master@{#290701}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290701 0039d316-1c4b-4281-b951-d872f2087c98

R=jamesr@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#290700}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290700 0039d316-1c4b-4281-b951-d872f2087c98

patterns in the extension's Content Security policy and update the documentation
to clarify the constraints of the CSP.

BUG=404295

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

Cr-Commit-Position: refs/heads/master@{#290699}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290699 0039d316-1c4b-4281-b951-d872f2087c98

We'll add an integrated page as a further test case next.

Also, this fixes the missing URL for core-scroll-header

BUG=401203, 394756

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

Cr-Commit-Position: refs/heads/master@{#290698}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290698 0039d316-1c4b-4281-b951-d872f2087c98

Cr-Commit-Position: refs/heads/master@{#290697}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290697 0039d316-1c4b-4281-b951-d872f2087c98

BUG=332205

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

Cr-Commit-Position: refs/heads/master@{#290694}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290694 0039d316-1c4b-4281-b951-d872f2087c98

BUG=377933,377921

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

Cr-Commit-Position: refs/heads/master@{#290693}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290693 0039d316-1c4b-4281-b951-d872f2087c98

when the system comes up in dark resume.  It also adds a
DarkSuspendImminent() method that observers within chrome can implement
if they want to be notified of this event.

BUG=397346
Signed-off-by: Chirantan Ekbote <chirantan@chromium.org>

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

Cr-Commit-Position: refs/heads/master@{#290692}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290692 0039d316-1c4b-4281-b951-d872f2087c98

Packet::Copy AddRefs the address resource returned from
PPB_UDPSocket::RecvFrom. But the convention is that when returning a new
resource, the resource will already have a refcount of 1. So the resource has
an leaked reference and will never be destroyed.

This memory leak cannot be detected from untrusted code (I overrode
mmap/mmunmap, but was unable to find it), but can be seen from the Chrome task
manager.

See user report here:
https://groups.google.com/d/msg/native-client-discuss/fEc6v7_wjkI/lnFNO09yw9kJ

BUG=none
R=noelallen@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#290691}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290691 0039d316-1c4b-4281-b951-d872f2087c98

BUG=405223

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

Cr-Commit-Position: refs/heads/master@{#290690}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290690 0039d316-1c4b-4281-b951-d872f2087c98

This makes mojo_shell, mojo_shell_tests and the wget, sample_app and
surfaces_app samples work along with their dependent services.

R=brettw@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#290689}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290689 0039d316-1c4b-4281-b951-d872f2087c98

R=brettw@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#290688}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290688 0039d316-1c4b-4281-b951-d872f2087c98

This is required in order for the host to be able to safely use X11
across multiple threads, e.g. for input-injection, screen capture and
any UX.

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

Cr-Commit-Position: refs/heads/master@{#290687}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290687 0039d316-1c4b-4281-b951-d872f2087c98

separate the process to initialize environment, and
start the session.

These are necessary step to launch athena in chrome.

BUG=397167

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

Cr-Commit-Position: refs/heads/master@{#290686}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290686 0039d316-1c4b-4281-b951-d872f2087c98

This uses substitution patterns in toolchains to allow the toolchain to specify more flexibly how files are to be named and generated at each step. The toolchain now has control over the naming of object and executable files, for example, where before these were hardcoded.

This removes most of the OS-specific logic hardcoded into the GN tool. There is still a bunch in action invocation; this will be done in a followup.

R=jamesr@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#290685}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290685 0039d316-1c4b-4281-b951-d872f2087c98

Now, WillStartBrowser method is never called on the benchmark tests.
This patch override the stub PageTest.WillStartBrowser in
RecorderPageTest. When WillStartBrowser is called, it forwards the call
to it's benchmark test.

The same behaviour is also applied to DidStartBrowser method

R=
BUG=400894

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

Cr-Commit-Position: refs/heads/master@{#290684}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290684 0039d316-1c4b-4281-b951-d872f2087c98

Revert of Re-land: content: Enable impl-side painting on Windows. (patchset #2 of https://codereview.chromium.org/392623003/)

Reason for revert:
Breaks telemetry unittests.

NOTRY=TRUE
NOTREECHECKS=TRUE
TBR=
Original issue's description:
> Re-land: content: Enable impl-side painting on Windows.
> 
> BUG=169282
> 
> Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=290535

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

Cr-Commit-Position: refs/heads/master@{#290682}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290682 0039d316-1c4b-4281-b951-d872f2087c98

This fixes:
Tooltip for NO_BLUETOOTH state has '$1' instead of Chromebook
Adds PHONE_UNSUPPORTED state
Clears screenlock state when Easy Unlock gets turned off

BUG=403831,404775

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

Cr-Commit-Position: refs/heads/master@{#290681}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290681 0039d316-1c4b-4281-b951-d872f2087c98

BUG=398964
NOTRY=True

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

Cr-Commit-Position: refs/heads/master@{#290680}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290680 0039d316-1c4b-4281-b951-d872f2087c98