GitLab

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/774a6cb..326aae8

TBR=caseq@chromium.org,apavlov@chromium.org,cbiesinger@chromium.org

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

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

Revert of Exclude readonly and disabled elements from autofill form. (patchset #3 id:40001 of https://codereview.chromium.org/621503003/)

Reason for revert:
breaks requestAutocomplete

Original issue's description:
> Exclude readonly and disabled elements from autofill form.
>
> R=isherman@chromium.org
> BUG=231160
>
> Committed: https://crrev.com/cfe1912bcc70118364c9156e1e12c6c89b1a06b9
> Cr-Commit-Position: refs/heads/master@{#298436}

TBR=isherman@chromium.org,mkwst@chromium.org,ziran.sun@samsung.com
NOTREECHECKS=true
NOTRY=true
BUG=231160

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

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

BUG=chromedriver:926

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

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

This reverts commit 5727ebd7.

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

This pulls in the following Native Client changes:

r13868: (dschuff) Add setjmp and a simple crtbegin for nacl-clang
r13873: (dschuff) Update revision for PNaCl r13828->r13868
r13874: (dyen) Fixed issue on windows where directory removal sometimes fails.
r13875: (dyen) Added i686-nacl-as and i686-nacl-ld for PNaCl direct to NaCl toolchain.
r13876: (shyamsundarr) stop building/testing old x86 validator.
r13877: (jvoung) Update GCC and GLIBC revisions to revert va_list definition.
r13878: (dschuff) Revert "Pass naclsdk_validate=0 to scons runs run by main waterfall bots"
r13879: (dschuff) Update all newlib revisions to 9f95ad0
r13880: (petarj) PNaCl: Update LLVM revision in pnacl/COMPONENT_REVISIONS
r13881: (dschuff) Update revision for PNaCl r13868->r13879
r13882: (yyanagisawa) Fix: forget to import time.
r13885: (dschuff) Add back one exclusion to libcxx test known failures.
r13886: (jvoung) Update NaCl x86 GCC newlib/glibc revision from 13729 to 13880.
r13887: (mazda) Make nonsfi_tests with pnacl_generate_pexe=0 run on buildbot.
r13888: (dschuff) Add nacl-clang testing to SCons
r13889: (dschuff) Upload packages for nacl_clang libc++ and support libs
r13890: (mcgrathr) Remove floating-point support from serialization library
r13891: (dschuff) Update revision for PNaCl r13879->r13890
r13892: (jvoung) Enable x86-32 cross calling convention test for varargs and va_list and method pointers.
r13894: (dschuff) Run nacl-clang tests on PNaCl bots

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

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

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

BUG=422376
R=oshima@chromium.org
TEST=manually

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

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

The signiture of this method is changed, so old Paint() method is removed.

BUG=407079

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

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

BUG=None
R=nkostylev@chromium.org
TEST=None

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

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

Revert "Updating trunk VERSION from 2186.0 to 2187.0" Revert "Updating trunk VERSION from 2187.0 to 2188.0"

This reverts commit a47856bb.
This reverts commit a47856bb.

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

This always enables the --enable-mime-handler-view FeatureSwitch when
--out-of-process-pdf is specified.

BUG=303491

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

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

Previously, we'd start WPR on an available host port and then just
assume that the same port was free on the device -- oops.

Now, we pass 0 to the forwarder for the device port so that it chooses
an available port, and then read back the port that it chose to use
for the mapping.

I believe this fixes a major case of device forwarder flake.

BUG=421599
TBR=slamm@chromium.org

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

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

BUG=399775

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

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

This test exhibits flaky failures on Linux. Example:

https://build.chromium.org/p/chromium.linux/builders/Linux%20Tests%20%28dbg%29%281%29/builds/34099

BUG=422998
TBR=hanxi@chromium.org
NOTRY=true

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

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

The switches are integrated with the new predictive network actions unified preference.

BUG=405690, 406203

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/1772da1..774a6cb

TBR=caseq@chromium.org,apavlov@chromium.org,cbiesinger@chromium.org

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

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

This patch is an alternative approach to only attempting to push gtest
deps once. (The first attempt to do this, landed in
https://codereview.chromium.org/560133002, caused issues and had to be
reverted.)

BUG=400440

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

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

Move the setup from BrowserActionsContainerTest into a
platform-independent test, so that we also start to get
test coverage on Mac.  In this first patch, move the
infrastructure and the basic test.  More to follow.

BUG=422381

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

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

This reverts commit 6a1f7b51.

The above commit was only intended for cherry-picking to M37/M38 branches.

R=qinmin@chromium.org,ycheo@chromium.org
BUG=

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

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

Added a bit more high-level documentation to android power monitors. Explained what ds2784 is and what android releases the data is available on.

BUG=

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

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

This CL teaches the mojom generator how to package JavaScript generated from
mojom both as AMD modules as an HTML imports.

R=hansmuller@chromium.org

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

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

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

BUG=412547, 394895

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

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

NOTRY=true

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

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

BUG=419367
TBR=phajdan.jr@chromium.org
NOTRY=true

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/e5dbb1f..1772da1

TBR=caseq@chromium.org,apavlov@chromium.org,cbiesinger@chromium.org

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

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

This was previously done, but was lost in some of the churn. Bring it back.
BUG=421782

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

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

Add histogram to track
* which TLS extension (NPN or ALPN) is used for protocol negotiation,
* in case of NPN, is there overlap or do we fall back,
* which protocol is selected.

This CL is draft, I still do not know how to call set_protocol_negotiation() in
NSS.  I would love to do that in
SSLClientSocketNSS::Core::HandshakeSucceeded(), but that might not be the on
the same thread.

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

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

BUG=410400
TEST=-

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/194240f..e5dbb1f

TBR=caseq@chromium.org,apavlov@chromium.org,cbiesinger@chromium.org

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

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

BUG=422943
TBR=tdresser@chromium.org

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

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

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/0d76b95..ca55641

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

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

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

BUG=405566

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

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

BUG=318770
TBR=nkostylev@chromium.org

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

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

CL https://chromereviews.googleplex.com/90457013/ for pre-checks.

BUG=419007

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

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

BUG=413863
R=ppi@chromium.org,erg@chromium.org

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

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

This reverts commit 1056c8a4.

Reason for revert: Seems to have caused test flakiness with non-empty message
loop. See https://crbug.com/422884.

BUG=422884
TBR=rockot@chromium.org

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

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

This CHECK was originally added because retail mode was supposed to not be supported anymore in R38:
https://chromium.googlesource.com/chromium/src.git/+/0dfff001d347879953bbeaa4e128c24e4e9fcc94

Since too many crashes were reported for R38, this removes the CHECK to support retail mode again.

BUG=422095
TEST=Ran retail mode in R38 and verified that it correctly logs in.

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

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

A very unlikely scenario in which the peer is not synchronizing for a long
time (e.g. 300 ms) which results in dropping cached buffers and restarting.

Since we have no control of the endpoint synchronization, we use the best
effort approach by clearing the FIFO and trying to catch up with the peer.

BUG=408940

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

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

Replace histogram recording for devices where the chromium android linker
is enabled with the following:

  ChromiumAndroidLinker.BrowserStates
    Whether relro sharing was attempted for the browser process, and if
    attempted, whether it succeeded. (0=normal load, 1=low memory load
    with shared relro, 2=low memory load used backoff so no shared relro)

  ChromiumAndroidLinker.RendererStates
    Whether relro sharing was attempted for a renderer process, and if
    attempted, whether it succeeded. (0=load with shared relro, 1=load
    used backoff so no shared relro, 2=shared relro not attempted)

If the chromium android linker is not enabled, none of the above
histograms is recorded.

BUG=419010

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

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

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