GitLab

This will only land after a corresponding change in CQ will land.

R=phajdan.jr@chromium.org
BUG=408675

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

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

These browser tests verify that we can load notification icons from
data: URLs and blobs when displaying Web Notifications.

R=johnme@chromium.org
BUG=none

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

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

Redesign of MD introduce strange tabfocus behavior around searchBox. This patch fixes it.

BUG=467872
TEST=browsertets pass

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

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

It's no longer necessary. And the handler is fired unexpected timing after unminimized and causes the issue (see the issue for detail). This patch removes it.

BUG=462065
TEST=browsertest passes

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

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

BUG=429399

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

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

We are not going to use 'EmbeddedSignIn' endpoint for OOBE, so this code
could be safely removed.

BUG=468439
TEST=manually

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/7f2e7cb..732bda7

TBR=pilgrim@chromium.org

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

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

The underlying reason for not finding the profile is probably crbug.com/464616,
but this should still not crash.

BUG=421215

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

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

BUG=468679
TBR=mnaganov@chromium.org

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

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

Add "--privileged" and "--privileged=<num>" that works similar to
"--sandboxed" to make it easier to debug the GPU process on Android.

BUG=468697

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

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

Revert of gpu: Measure texture uploads with glTexSubImage2D and glTexImage2D. (patchset #2 id:80001 of https://codereview.chromium.org/1022603002/)

Reason for revert:
This is causing gpu_perftests to fail on android perfbots. See http://crbug.com/468748

Original issue's description:
> gpu: Measure texture uploads with glTexSubImage2D and glTexImage2D.
>
> glTexImage2D and glTexSubImage2D could have different performance
> properties.
> With this patch we benchmark both of these upload techniques.
>
> When using glTexSubImage2D the texture storage is specified with
> glTexStorage2D when available, or glTexImage2D passing an empty pointer as data.
>
> BUG=423481
>
> Committed: https://crrev.com/1b9c0f6571baefe70dad41d504cbe3136ce41ae4
> Cr-Commit-Position: refs/heads/master@{#321300}

TBR=reveman@chromium.org,dcastagna@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=423481

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

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

BUG=468741
TBR=dschuff@chromium.org

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

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

WebRTC 8786:8790
Changes: https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+log/3b9d0a5..78aaaa6

TBR=tommi,pbos

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/b2ae98a..7f2e7cb

TBR=pilgrim@chromium.org

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

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

This CL adds a comment on how logging is used to report script and test failures.

R=battre@chromium.org
BUG=468245

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

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

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

(By manual request.)

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

Revert of "Log force-alt-protocols command line flag usage" (patchset #2 id:20001 of https://codereview.chromium.org/879863004/).  Created manually by git revert ; git cl upload.

Reason for revert:
Reverting bogus CL.  base::RecordAction cannot be called on the IO thread.  This
CL actually causes debug build Chromium to crash upon startup if invoked with
the --use-spdy=force-alt-protocols command line flag.

Nothing else in io_thread.cc seems to be using "base/metrics/user_metrics.h", so
it seems to be safe to remove.

Original issue's description:
> Log force-alt-protocols command line flag usage.
>
> BUG=452514
>
> Committed: https://crrev.com/493bc568527caeab93a173e4feea85c0c86c439e
> Cr-Commit-Position: refs/heads/master@{#313566}

TBR=rch@chromium.org,asvitkine@chromium.org
BUG=452514

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

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

Revert of Add second batch JS benchmark and code generator (patchset #5 id:60001 of https://codereview.chromium.org/1000203002/)

Reason for revert:
Breaks check_licenses on linux: https://build.chromium.org/p/chromium/builders/Linux/builds/59754/steps/check_licenses/logs/stdio

Notice: This was also caught by the trybot. Please don't commit manually - use the CQ instead.

Original issue's description:
> Add second batch JS benchmark and code generator
>
> This patch adds a "Second batch JS" benchmark and a code generator for
> creating synthetic Javascript content for the different variants of the
> benchmark.
>
> The benchmark flow is:
>
> 1. Load an initial page quickly. We also start a continuous animation
>    which gauges the responsiveness of the main thread.
> 2. Start loading Javascript asynchronously.
> 3. When the loading completes, wait 1 second and click on a button
>    which causes about 5% of the Javascript to execute.
>
> The aim is to keep the page responsive during loading and minimize the
> latency of the click handler. There are three variants with a small (15K),
> medium (150K) and large (1.2M) amount of Javascript.
>
> The generated Javascript consists of half top-level closures, half top-level
> functions, each of which calls a varying number of inner functions to
> perform arithmetic.
>
> Note that currently the benchmark only measures the responsiveness of the
> click handler, but eventually it will be able to track this over the entire
> interaction flow (crbug.com/460206).
>
> BUG=428350
> R=rmcilroy@chromium.org
>
> Committed: https://chromium.googlesource.com/chromium/src/+/b0a90f4b6c81fc65dd0c57ebc00b0ba6fe784b22

TBR=rmcilroy@chromium.org,skyostil@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=428350

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

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

This parameter is unused in almost every class derived from WebContentsObserver.
This will make refactoring the OnDid{Start|Stop}Loading IPCs from
WebContentsImpl to RenderFrameHostImpl simpler.

BUG=429399,450799

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

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

This patch adds a "Second batch JS" benchmark and a code generator for
creating synthetic Javascript content for the different variants of the
benchmark.

The benchmark flow is:

1. Load an initial page quickly. We also start a continuous animation
   which gauges the responsiveness of the main thread.
2. Start loading Javascript asynchronously.
3. When the loading completes, wait 1 second and click on a button
   which causes about 5% of the Javascript to execute.

The aim is to keep the page responsive during loading and minimize the
latency of the click handler. There are three variants with a small (15K),
medium (150K) and large (1.2M) amount of Javascript.

The generated Javascript consists of half top-level closures, half top-level
functions, each of which calls a varying number of inner functions to
perform arithmetic.

Note that currently the benchmark only measures the responsiveness of the
click handler, but eventually it will be able to track this over the entire
interaction flow (crbug.com/460206).

BUG=428350
R=rmcilroy@chromium.org

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

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

BUG=467059

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

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

This CL makes all output of the tests to go through the Python standard logging:
 * script-level debugging messages gets logged on a custom SCRIPT_DEBUG level (9)
 * logs from failed tests get logged at level DEBUG
 * summary of the tests run gets logged at level INFO

This allows to remove the knowledge of how the results are passed on from the test running scripts. In particular, the Google Spreadsheet writing code has been removed. To restore that functionality, the caller of these scripts will need to implement a custom logging handler. That will happen in a separate CL, because the caller is in a separate repository.

BUG=468245

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/b11c5cb..b2ae98a

TBR=pilgrim@chromium.org

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

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

BUG=468713
TBR=alexmos@chromium.org

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

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

Revert of Added EventSender.setTouchPointRadius() for layoutTests (patchset #4 id:60001 of https://codereview.chromium.org/990183003/)

Reason for revert:
Layout tests failures, see crbug/468704

Original issue's description:
> Added EventSender.setTouchPointRadius() for layoutTests
>
> A link to the Blink patch (layoutTests) https://codereview.chromium.org/990193002/
>
> BUG=
>
> Committed: https://crrev.com/97a6dbc41736e484f1b5ad544f68f8d34013179b
> Cr-Commit-Position: refs/heads/master@{#321167}

TBR=rbyers@chromium.org,d.pikalov@partner.samsung.com
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=468704

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

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

BUG=468675
TBR=erikchen@chromium.org

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

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

The original config of 2 buffers is too few. The kernel may be throttled with no
buffer to queue when Chrome doesn't return the buffer in time. Reserve two more
buffers gives Chrome extra 60ms to process incoming frame on a 30fps camera.

BUG=chrome-os-partner:32570
TEST=Check 'uvcvideo: Dropping payload' messages in kernel logs

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

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

BUG=468679
TBR=mnaganov@chromium.org

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

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

d319ad9 Import BUILD.gn into ICU repo

Also remove the now superfluous secondary BUILD.gn files for ICU

BUG=none
TBR=dpranke@chromium.org

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

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

V8 caches FunctionTemplates for a lifetime of a web page for its own internal
reasons, thus it is generally a good idea to cache the template returned by
gin::CreateFunctionTemplate function. Otherwise, repeated method invocations
from JS will create substantial memory leaks.

BUG=463487

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

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

Request time from the OS when the application is backgrounded on iOS to
try to commit all pending history transactions.

BUG=429756

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

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

The distillation does not need to start in this cases, the data
source is going to fallback to the error webpage.

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

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

Match objects are more convenient since they would also allow the caller
to define further groups to retrieve in the message_regex, or have
access to the full line being matched.

BUG=

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

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

The old WebSocket implementation did not support header
continuations. The new implementation does. Add a regression test so
that we do not regress the fix accidentally.

TEST=net_unittests
BUG=169448

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

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

This CL adds warning message for setParameters API of vpnProvider.
The vpnProvider extension API is further filled to stable channel
from dev channel.

BUG=467911
TBR=stevenjb

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

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

We can use this option, e.g., to request only the "crash" portion of a
logcat.

BUG=

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

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

This CL fixes typos in JS types introduced by CL 1006553002.

BUG=460428
TEST=None

TBR=stevenjb

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

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

OS X has contained Hiragino Kaku Gothic/Mincho ProN fonts which adapt JIS X 0213:2004 glyph forms and used them since 10.5. This CL makes Chromium use ProN fonts instead of Pro fonts.

This is in line with Firefox and Safari.

BUG=447843
TEST=On OS X, ProN fonts are used (per dom inspector).
data:text/html,<ul lang="ja"><li>&#x845b;<li style="font-family:serif">&#x845b;<li style="font-family:sans-serif">&#x845b;

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

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

This message is shown when the remote device's name cannot be determined.

BUG=453998
TEST=none
R=tengs@chromium.org

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

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