GitLab

R=lcwu@chromium.org
BUG=391045

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

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

The lookup table for sniffing text/plain messages for binary characters
was 256 bytes in size. The information it encoded could be stored in 32
bits.

Use a 32-bit lookup table instead of the 256-byte lookup table. This
reduces binary size.

This change is mostly performance neutral; micro-benchmarks show
no statistically significant change on Android. Micro-benchmarks on
high-performance Intel processors show an additional cost of around
400ns, apparently due to branch mis-prediction.

However, real-world performance is likely to be dominated by the time taken to
load the table into CPU cache, which the new implementation should win
easily.

Also add a micro-benchmark test.

BUG=
TEST=net_unittests

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

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

This CL
- Adds an unregister method to the remoting.WindowShape so that clientUI can unhook itself.
  This is a preparation work for the in-DOM reconnect window.
- Adds an centerToDesktop() method to center a DOM element to the union of desktop rectangle.

BUG=486888

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

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

BUG=473205

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

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

Flaky failures on the ChromeOS/MSan bot.

BUG=475516
TBR=xiyuan@chromium.org
NOTRY=true

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

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

When compiling Objective C, warns if a method is used whose availability is
newer than the deployment target.

BUG=471823

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

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

This is not longer needed since we only guard the API under
_api_features. This extra guard is causing the test failures in officla
builds since extensions::ScopedCurrentChannel does not affect the
regular chrome channel settings.

BUG=489368
TEST=existing tests

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

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

Tests various behaviors for the passphrase creation UI; specifically
when error messages are displayed and when submission succeeds.

BUG=480604

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

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

This change is motivated by some complex test flakiness issues that were
discovered in http://crrev.com/1118833002. Making it impossible to store
a reference means that if we overwrite it for tests, we know everyone is
then using the overwritten version.

The approach here is to make every public method static and take the
context as an argument, so it can initialize the inner object if
necessary.

This CL is part 1/3 and leaves in deprecated versions of all the methods.
In part 2/3 the downstream uses of AndroidSyncSettings will be changed,
and in part 3/3 the deprecated methods will be removed upstream.

BUG=480604

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

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

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

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

Exclude techcrunch.com from power.top_25 . It is not suitable for this
benchmark because it does not consistently become quiescent within
60 seconds.

BUG=489214
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_perf_bisect;tryserver.chromium.perf:win_perf_bisect;tryserver.chromium.perf:android_nexus5_perf_bisect

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

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

BUG=489779
TBR=jam@chromium.org
NOTRY=true

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

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

BUG=466799

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

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

This design is based on this mock: https://drive.google.com/a/chromium.org/file/d/0B-DVbqI3huZGZGhIcTFtRWRTSTA/view?usp=sharing

BUG=458664

TEST=
1. Launch chrome and make sure there is more than one available profile.
2. Left-click on the Avatar Button.
3. A tutorial bubble should be displayed informing the user they can
   right-click the button to see other users.
4. Close the bubble without dismissing the tutorial, for example by
   clicking in the content area.
5. Reopening the Avatar Menu should still display the tutorial until it
   is explicitly dismissed (clicking the X or the "Ok, got it!" button)
   or until the user right clicks the button.
6. Once dismissed, the tutorial should never be shown again.

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

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

Do not let the invalidations service to fall back to XMPP if GCM is disabled, since we already finished traansite from GCM to XMPP, and XMPP do not have prepare for such load spike.
Since Sync have backoff mechanism, so if GCM server some how disabled, sync will retry it later.

BUG=479300

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/55b88ca..89aeb69

TBR=hiroshige@chromium.org,szager@chromium.org

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

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

The callback updates the |visible| property to NO so clients can
correctly determine if the context menu has been dismissed.

BUG=489121

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

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

A number of cc unit tests have started checking property tree output,
primarily visible_rect_from_property_trees but also needs_rebuild on the
trees.

Because of this, these tests now depend on running the property tree
code, so setting verify_property_trees=false forces these tests to run
only CDP code which causes them to fail.

Therefore, convert these specific tests to use property tree updates
directly.  This also requires a PrecalculateMetaInformation function
for LayerImpl, as LayerTreeHostCommonTest.SkippingSubtreeImpl touched
LayerImpl properties that could only theoretically be changed from
the main thread.

In the future, I think all layer tree host common tests will need to go
down the property tree update path, but (in my opinion) it's not worth
doing that until we have property trees everywhere.  This patch is just
a step in that direction to unblock property trees for the compositor
thread first.

R=ajuma@chromium.org,vollick@chromium.org
BUG=481585

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

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

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/9b4b91f5..4b91f76

CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
TBR=bungeman@google.com

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

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

1) file manager's chrome web store widget
2) wallpaper gallery spinner

BUG=485779

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

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

This makes the build/test cycle easier for Release builds.

BUG=none
R=brucedawson@chromium.org

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

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

By default, OnSSLCertificateError() just cancels current request.
For connectivity_checker, it needs to cancel the current request
and starts next check. In particular, this handles the case that
SSL cert fails when device system time is changing (syncing to
NTP server).

BUG=internal b/20775908

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

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

R=byungchul@chromium.org,lcwu@chromium.org
BUG=internal b/21262248

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

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

4 raster threads improve performance on 8 core machines.
8 core machines might not be a priority but it seems
like an unnecessary limitation to have.

BUG=

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

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

The test is failing due to the lack of WebGL support.
See crbug.com/488059#c24
Link to failing step:
https://build.chromium.org/p/chromium.perf/builders/Win%20XP%20Perf%20%284%29/builds/3243/steps/blink_perf.canvas/logs/stdio

BUG=488059
TBR=skyostil@chromium.org
NOTRY=true
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_perf_bisect;tryserver.chromium.perf:win_perf_bisect;tryserver.chromium.perf:android_nexus5_perf_bisect

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

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

BUG=467734

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

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

The tools/git/move_source_file.py tool relies on the alphabetic ordering, and will mess up changes if the gypi files are not initially sorted.

BUG=486739

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

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

BUG=484139

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

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

With this change, closing the window shuts down Mandoline cleanly.

This is split off https://codereview.chromium.org/1139673003

BUG=484234

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

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

Following https://codereview.chromium.org/1129863003/ which added
support for loading an apply an ICC file based on EDID product id a new
entry was added to the chromeos paths switch statement. Unfortunately
the break statement was missing in the newly added case.

Failing to break from the switch statement triggered a DCHECK failure in
path_service.cc which would result in in asserts in builds where DCHECK
is fatal.

BUG=489643
TEST=None

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

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

In order to avoid the touch event queue keep growing when render handles
async touchmove events longer than 200ms, which is the async touchmove
interval, we keep coalesce touch moves and send the next touchmove
until passing the async touchmove interval and receive the ACK from render.

BUG=448760

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

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

When an extension is removed, if an element was focused, the analogous element
on the previous/next extension should be focused.

BUG=479092

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

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

Also clarify the split between Deterministic and non-Deterministic
socket data providers.

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

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

This is a followup to r329965

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

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

BUG=None

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

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

There are no remaining call sites for either BlitContextToCanvas or
BlitCanvasToContext. Also remove some leftover #includes.

TEST=Linux built compiles & links.

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

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

The capabilities section is a map, not an array. This CL fixes the example
snippet.

TEST=Testing docs server.
BUG=489217

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

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

This test fails (same symptoms as bug 443352) on hardware with <= 256MB
of RAM.

BUG= internal b/21093117

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

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

mojo.ContentHandler is a core thing used by the shell, and thus should
be part of the Application interface. This should enable further
refactoring.

BUG=

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

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

Sheriffs: if WebRtcBrowserTest.CanSetupVideoCallAndDisableLocalVideo
flakes, revert this patch. It shouldn't flake after this fix.

Instead of looking at color values of individual pixels, see if we can
get more reliable results by looking at luma values instead. This way
we can detect black frames more reliably in the tests.

This is a partial re-land of codereview.chromium.org/1108803002.

This is essentially the black frame algorithm used in testrtc.

BUG=477498

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

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