GitLab

If interactive_ui_tests can't change the foreground window, print the name of the Window that is currently in the front.

This helps debug problems on bots.

R=sky@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#294485}

Create a standalone executable that plumbs public Mojo API calls into a NaCl
sandbox.  This allows the public Mojo unit tests to run inside NaCl.

BUG=401761

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

Cr-Commit-Position: refs/heads/master@{#294484}

Some Linux drivers implement the GLX_SGI_video_sync
extension in a way that eats a ton of CPU resources.
Only call it periodically to reduce CPU usage.

BUG=373489

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

Cr-Commit-Position: refs/heads/master@{#294483}

https://skia.googlesource.com/skia/+log/790ffe3feb90370318f42b28eb9c6af6e38cd4f9..0b36e6b65f8c124f2ef2601294288219b3c3a1f0

CQ_EXTRA_TRYBOTS=tryserver.blink:linux_blink_rel,linux_blink_dbg
TBR=fmalita@google.com

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

Cr-Commit-Position: refs/heads/master@{#294482}

When changing from software mirroring mode to sinlge display mode, it
is possible there is no need to update |displays_| and we early out
UpdateDisplays(). But we still want to run the PostDisplayConfigurationChange()
cause there are some clients need to act on this, e.g.
TouchTransformerController needs to adjust the TouchTransformer when
switching from dual displays to single display.

BUG=chrome-os-partner:31868
TEST=tested on Big, after existing software mirroring mode, the touch location
     transformation is still correct.

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

Cr-Commit-Position: refs/heads/master@{#294481}

Revert of Remove a broken link. (patchset #2 id:20001 of https://codereview.chromium.org/546713003/)

Reason for revert:
I found the link I thought didn't exist.

Original issue's description:
> Remove a broken link.
>
> BUG=none
> R=
> TEST=none
> NOTRY=true
> (documentation only change)
>
> Committed: https://crrev.com/3b9f3449861b9bfc196a152a2c74f6e7cdd18ef1
> Cr-Commit-Position: refs/heads/master@{#294234}

TBR=mkearney@chromium.org,smain@chromium.org,jfb@chromium.org,sbc@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=none

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

Cr-Commit-Position: refs/heads/master@{#294480}

This brings in:
  12a9940 Check object type for objects used in the dictory of 'Index'
  9175bee Change the forced clear order of CPDF_DocPageData::Clear, and remove m_pDocument in CPDF_Color
  663af99 Fix uninitialized value in CPDF_ColorStateData
  6eee264 Revert of Fix uninitialized value in CPDF_ColorStateData
  a38d4c3 Fix uninitialized value in CPDF_ColorStateData
  0fb1b3d Fix un-initialized R G B value

TBR=inferno@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#294479}

Choose to put the UMA reporting code in content_decryptor_delegate.cc because:
- It's hard to do UMA in CdmAdapter due to pp::UMAPrivate limitations.
- I want to report system code for OnPromiseRejected() and OnSessionError() in
  one file. So I can't do it in CdmPromise.

BUG=412987
TEST=Tested by hacking Chromium to provide a wrong license. Then check about://histograms and I see the histogram generated.

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

Cr-Commit-Position: refs/heads/master@{#294478}

BUG=406064

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

Cr-Commit-Position: refs/heads/master@{#294477}

R=byungchul@chromium.org,lcwu@chromium.org,yfriedman@chromium.org
BUG=400876

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

Cr-Commit-Position: refs/heads/master@{#294476}

WebCacheManager::ClearCacheOnNavigation() is used by webrequest api, which will be moved to //extensions. So we need to resolve its the dependency on WebCacheManager by moving WebCacheManager to //components.

There are two ipc messages sent in WebCacheManger:
-ChromeViewMsg_SetCacheCapacities
-ChromeViewMsg_ClearCache

Both ipc handlers were in ChromeRenderProcessObserver. These two ipcs are renamed as WebCacheMsg_XXX, and we introduce WebCacheRenderProcessObserver and handle these ipcs in //components.

BUG=352293,411437
TBR=agl@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#294475}

Previously TransportFactory interface was responsible for creation
and initialization of several protocol layers, including PseudoTCP and
authentication (TLS). Simplified it so now it only creates raw datagram
transport channel. PseudoTcpChannelFactory is now responsible for
setting up PseudoTcpAdapter and AuthenticatingChannelFactory takes care
of channel authentication. Also added DatagramChannelFactory for
Datagram channels.

This change will make it possible to replace PseudoTcpChannelFactory
with an object that creates SCTP-based channels.

Also fixed a bug in SslHmacChannelAuthenticator. It wasn't working
properly when deleted from the callback. (base::Callback objects
shouldn't be deleted while being called because when deleted they
also destroy reference parameters values they are holding).

BUG=402993

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

Cr-Commit-Position: refs/heads/master@{#294474}

Cr-Commit-Position: refs/heads/master@{#294473}

BUG=409938

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

Cr-Commit-Position: refs/heads/master@{#294472}

BUG=408446,413226
TBR=tim@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#294471}

BUG=412398

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

Cr-Commit-Position: refs/heads/master@{#294470}

BUG=411755

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

Cr-Commit-Position: refs/heads/master@{#294469}

These notifications are used by the browser to manager power save
blocking, inaccuracies will result in erroneously holding blockers
after playback has stopped.

BUG=43667, 367785
TEST=DCHECKs in WebContentsImpl no longer fire.

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

Cr-Commit-Position: refs/heads/master@{#294468}

Windows 7 appears to sometimes return an incorrect value for max touch
points, returning 1 when there's in fact no touch devices present. This
breaks some web pages that use a non-zero number of touch points as a
signal that the devices has a touch screen. As this is specific to certain
Win7 configurations, I don't have a repro; however, reports in the bug
show that the SM_DIGITIZER setting does indeed return the correct status
of "no touchscreen". In light of this, we speculatively return 0 touches
if there's no touchscreen device present.

BUG=352942

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

Cr-Commit-Position: refs/heads/master@{#294467}

R=stevenjb@chromium.org,asvitkine@chromium.org,benchan@chromium.org
BUG=404791

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

Cr-Commit-Position: refs/heads/master@{#294466}

This pulls in the following Native Client changes:

r13725: (hidehiko) Non-SFI mode: Support CMSG family for nonsfi_helper.
r13726: (dschuff) PNaCl: Update LLVM revision in pnacl/COMPONENT_REVISIONS
r13727: (jvoung) Update revision for PNaCl r13714->r13726
r13728: (dbrazdil) Added support for passing arguments to MinSFI's entry function
r13729: (hidehiko) Non-SFI mode: Add prototype declaration for recv() and send().
r13730: (dschuff) build_nexe: Tolerate variants of Release and Debug in build config names

BUG=none
TEST=browser_tests and nacl_integration
CQ_EXTRA_TRYBOTS=tryserver.chromium.linux:linux_rel_precise32,linux_arm_cross_compile,linux_nacl_sdk_build,linux_chromium_dbg

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

Cr-Commit-Position: refs/heads/master@{#294465}

BUG=372607

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

Cr-Commit-Position: refs/heads/master@{#294464}

Note that the pattern used to check commit position appears two times in reverted
CL, therefore match the pattern at begining of the line

BUG=413365,412054
NOTRY=true

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

Cr-Commit-Position: refs/heads/master@{#294463}

This also includes a bit of JS cleanup to use ONC properties directly
where possible.

BUG=279351
R=pneubeck@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#294462}

This is wrong according to the HTML Media specification:

http://dev.w3.org/html5/spec-preview/media-elements.html#offsets-into-the-media-resource

"If the media resource somehow specifies an explicit timeline whose
origin is not negative (i.e. gives each frame a specific time offset
and gives the first frame a zero or positive offset), then the media
timeline should be that timeline."

BUG=413292
TEST=updated unittest.

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

Cr-Commit-Position: refs/heads/master@{#294461}

A previous patch commented these out, but this ended up not being necessary. Put them back.

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

Cr-Commit-Position: refs/heads/master@{#294460}

https://chromium.googlesource.com/chromium/blink/+log/5af3948f23b6954c5f76bac93474432805751cae..a1f6307669c32a40076d299272d220343ff74bb9
TBR=jianli@chromium.org,loislo@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#294459}

On Oct 26, 2014, Russia will switch from 9 timezones to 11 timezones with
most of the current zones going back by an hour from the current zone.
(e.g. Europe/Moscow will be UTC+0300 instead of UTC+0400).

Add new Russian time zones and shuffle the timezone order in the tz
selection UI to make them roughly in the order of their tz offsets
when the change gets effective on Oct 26, 2014. In the meantime, some
zones will be out-of-place.

This ordering can't be perfect beause of DST. To address that issue,
this CL will be followed by a CL to sort them dynamically instead of
using the hardcoded order.

BUG=404445
TEST=Go to settings - advanced - timezone setting and look for
Asia/Kamchatka.

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

Cr-Commit-Position: refs/heads/master@{#294458}

Better coordinate what's responsible for associating a registration to a document. During navigation, its the ServiceWorkerControlleeRequestHandler responsibility, but the ServiceWorkerRegisterJob takes over there after.

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

Cr-Commit-Position: refs/heads/master@{#294457}

Looks like nobody is using this script? Checked in Chromium, Blink
and Buildbot repos.

BUG=338338
TEST=None
R=dpranke@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#294456}

BUG=398467
TEST=ExtensionTest

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

Cr-Commit-Position: refs/heads/master@{#294455}

Also change from the observer pattern to the simpler callback pattern, as there is only a single notification type (TPM is enabled/disabled).
This simplifies ownership of the observer/receiver especially if multiple threads (typically UI and IO) are involved: A temporary callback with a WeakPtr can be used instead of an observer object that has to be owned by someone.

BUG=413219

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

Cr-Commit-Position: refs/heads/master@{#294454}

Since the introduction of nano protobufs for Java in
https://codereview.chromium.org/532303003 (and updated in
https://codereview.chromium.org/549543002), there is no need for the
lite protocol buffers anymore.

This CL removes the checked out files initially introduced when
protobuf lite support for Java was added in
https://chromiumcodereview.appspot.com/11347026 and cleans up the
infrastructure regarding generating protocol buffers.

Since lite is not supported anymore, this also removes the requirement
for setting the 'proto_runtime' variable for targets using
build/protoc_java.gypi.

BUG=377891
TBR=zea@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#294453}

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

Cr-Commit-Position: refs/heads/master@{#294452}

R=wez
BUG=

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

Cr-Commit-Position: refs/heads/master@{#294451}

This was recently broken by https://codereview.chromium.org/476313003/.
The problem is that when opening a new window, the fullscreen button was not
enabled yet by the time we layout the profile button.
We need to call layoutSubviews after the fullscreen button is enabled because
the avatar button's position depends on it. But with the old avatar button,
we need to call layoutSubviews first because the fullscreen button's position
depends on it.

BUG=412018

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

Cr-Commit-Position: refs/heads/master@{#294450}

This will disable low res tilings on all platforms but android, since
RenderWidgetCompositor only sets this to true on android.

R=vmpstr
BUG=410610

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

Cr-Commit-Position: refs/heads/master@{#294449}

BUG=409349

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

Cr-Commit-Position: refs/heads/master@{#294448}

NOTRY=true

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

Cr-Commit-Position: refs/heads/master@{#294447}

All of the subclasses do the same thing for the polling part, so share
it. Not all of them use DispatchEventToCallback, so remove that part.

NOTRY=true

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

Cr-Commit-Position: refs/heads/master@{#294446}