GitLab

Adding some missing manifest and permission features that
ChromeVox needs on chromecast.

Bug: b/73383411
Test: None
Change-Id: I2d85e18fcec6dceb02dccec551838ebca418aaab
Reviewed-on: https://chromium-review.googlesource.com/1093272Reviewed-by: Alex Sakhartchouk <alexst@chromium.org>
Commit-Queue: Randy Rossi <rmrossi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567270}

This is a follow-up from
https://chromium-review.googlesource.com/c/chromium/src/+/1089633

This CL adds a helper function which wraps UCKeyTranslate along with
some param conversions needed to call into it in a new helper function.
I've also updated all of the callsites which used UCKeyTranslate
directly to use the new helper function.

During the original CR, there was a suggestion to put the helper
method in ui/base/cocoa.  I've kept it in ui/events as referring
to ui/base from within ui/events was problematic.  Also ui/base
seemed like the wrong place given that this helper does work with
low level key event data and not higher level constructs.

BUG=832811

Change-Id: Iba6c78c846637afd74eb0256ac7e65dc3508d97a
Reviewed-on: https://chromium-review.googlesource.com/1097976
Commit-Queue: Joe Downing <joedow@chromium.org>
Reviewed-by: Shuotao Gao <stgao@chromium.org>
Reviewed-by: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567269}

In libaom CMake configuration:
-Wenum-conversion and -Wparentheses-equality are enabled by default
in clang and not explicitly disabled.
-Wunused-function is from CMake defaults and no longer disabled.
-Wsign-compare is explicitly enabled.

The symbol "_vpx_scaled_2d" is no longer present, so the bug that
required "-fno-common" should be resolved.

Bug: 783519
Change-Id: I099b89c3b418fb2cd50bc19af167deaf71f12a6c
Reviewed-on: https://chromium-review.googlesource.com/1100370Reviewed-by: Johann Koenig <johannkoenig@google.com>
Commit-Queue: Johann Koenig <johannkoenig@google.com>
Cr-Commit-Position: refs/heads/master@{#567268}

TBR=dsinclair@chromium.org

Bug: 808152
Change-Id: I006300209602701c98a5ce35e9d504c1347d8915
Reviewed-on: https://chromium-review.googlesource.com/1101059Reviewed-by: François Doray <fdoray@chromium.org>
Commit-Queue: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567267}

- Add explanatory text to each one
- Make the manual test path accessible to color blind testers
- Bring headers up to date
- Create a consistent style for :focus-visible and :focus:not(:focus-visible) for easier understanding of test results

Bug: 817199
Change-Id: I97191d5c8395576a42c923a025d05d2d61e79552
Reviewed-on: https://chromium-review.googlesource.com/1093697
Commit-Queue: Alice Boxhall <aboxhall@chromium.org>
Reviewed-by: Jonathon Kereliuk <kereliuk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567266}

TBR=pkotwicz

Bug: 852648
Change-Id: I2799a73ecec82d9ceef99f0280655096ed2d3bdd
Reviewed-on: https://chromium-review.googlesource.com/1100890Reviewed-by: Jan Wilken Dörrie <jdoerrie@chromium.org>
Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567265}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/d791a8f5..4b7910b8

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org

Change-Id: I9087463c2cf16263098c3eba993719eb62086453
Reviewed-on: https://chromium-review.googlesource.com/1100741Reviewed-by: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#567264}

Bug: 841735
Change-Id: I86007d80dd719cd00c4b224d9f88479daa1bb422
Reviewed-on: https://chromium-review.googlesource.com/1101019Reviewed-by: Alexander Timin <altimin@chromium.org>
Commit-Queue: Greg Kraynov <kraynov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567263}

Change-Id: Ideafaf71a790c28f88a7f514c3d0d4384bcd9f21
Reviewed-on: https://chromium-review.googlesource.com/1099608
Commit-Queue: Eric Stevenson <estevenson@chromium.org>
Reviewed-by: Christopher Grant <cjgrant@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567262}

All annotation tests are activated for windows FYI bot,
win-annotator-rel.

Bug: 844014
Change-Id: I1b9762be6dcf759a74f4b7602b0ceae6b2873126
TBR: georgesak@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/1100829
Commit-Queue: Ramin Halavati <rhalavati@chromium.org>
Reviewed-by: Ramin Halavati <rhalavati@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567261}

The Device Service needs to clean up parts of its internal state as part
of browser shutdown. However, it also needs to run on the UI thread,
and embedded services that run on the UI thread are not guaranteed to
be destroyed as part of browser shutdown (tasks to destroy these
services are posted from the IO thread by
ServiceManagerConnectionImpl::ShutDownOnIOThread, but the UI thread is
typically shut down before these posted tasks are run).

To solve this issue we discussed adding plumbing wherein embedded
services could inform //content that they wanted to be notified when
shutdown was occurring on the main thread. However, on investigation
this plumbing would be painful to implement: it is only
EmbeddedInstanceManager that has direct information of these service
instances, and that object lives far away from //content's
ServiceManagerContext, the object that knows when shutdown is occurring
on the main thread.

This CL takes an alternative approach of having the Device Service
implementation observe the destruction of its MessageLoop. I have
verified that the observation is triggered on shutdown of Chrome.

Bug: 794105
Change-Id: I3b383871679d42f544812be4bcb13c872cf276ff
Reviewed-on: https://chromium-review.googlesource.com/1099245
Commit-Queue: Colin Blundell <blundell@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567260}

Tests for counting features are removed from the blink side because
there are browser side testing them, please see:
chrome/browser/page_load_metrics/page_load_metrics_browsertest.cc

Tests for frame fetch context is removed, but there's still test
coverage in
chromium/src/chrome/browser/client_hints/client_hints_browsertest.cc

Tests for blink side use counter dropping ntp activities is no longer
needed as blink side use counter is being removed.

TBR: nhiroki@chromium.org
Bug: 849695, 790957
Change-Id: I32b0d01b768c7043fb01f2329cc089049126ed2b
Reviewed-on: https://chromium-review.googlesource.com/1087045
Commit-Queue: Luna Lu <loonybear@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Rick Byers <rbyers@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567259}

Don't call into |fling_controller_| if it's destroyed.

Bug: 852264
Change-Id: I71081588f0b7e5bf882c28231e3d6b20026e4611
Reviewed-on: https://chromium-review.googlesource.com/1099145Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: Saman Sami <samans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567258}

In case of range request, if server send unexpectedly
extra data, ignore it.

BUG=825829

Steps to reproduce:
1) Clear browser cache.
2) Open PDF:
http://www.major-landrover.ru/upload/attachments/f/9/f96aab07dab04ae89c8a509ec1ef2b31.pdf#page=55
3) Wait until document finish loading

Expected:
 The loading of document is finished
Actual:
 Some times the loading of document is never finished.

Change-Id: I46fc8001bea5701e1e93d26d1ea6527d4736ff05
Reviewed-on: https://chromium-review.googlesource.com/1094634Reviewed-by: dsinclair <dsinclair@chromium.org>
Commit-Queue: Art Snake <art-snake@yandex-team.ru>
Cr-Commit-Position: refs/heads/master@{#567257}

Drive-by: minor lint/include fixes.

Bug: 852423
Change-Id: I7ae9b3d0bb74caaee133600eb9a88c93ff74d2ea
Reviewed-on: https://chromium-review.googlesource.com/1099166Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567256}

This fixes a bug that was introduced with 13ef1e88
While the first patch properly distinguished between the two when processing
local changes it failed doing so when processing remote changes (either
incremental or initial sync changes).

The issue surfaced when a preference got moved between regular and priority
sync preferences. In that scenario, sync has values for that pref in each
flavour and one can overwrite the other.

Bug: 849523, 840332
Change-Id: Ib458c5863bc036dbb2a735ccacd52c6df2c118bb
Reviewed-on: https://chromium-review.googlesource.com/1099381Reviewed-by: Dominic Battré <battre@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Commit-Queue: Tim Schumann <tschumann@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567255}

Bug: 843511
Change-Id: I946798560e0ba54d22123d86c90507e0d9c9c7da
Reviewed-on: https://chromium-review.googlesource.com/1099430Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567254}

There are several places where we query the keyboard bounds by
grabbing the keyboard container window and calling |bounds|. However,
it's unclear whether they mean the bounds relative to parent or bounds
relative to the screen, since both are currently the same for the
keyboard container.

This patch changes several callers to use |GetBoundsInScreen| since
they actually want the screen bounds. Note we don't change any behaviour
since currently keyboard container |bounds| == |GetBoundsInScreen|, but
this will change in future when we get rid of keyboard container.

Bug: 849980
Change-Id: I7211073a7697f168824c127319dfc40e6888195a
Reviewed-on: https://chromium-review.googlesource.com/1098417
Commit-Queue: James Cook <jamescook@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Yuichiro Hanada <yhanada@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567253}

It passes on other versions, so keep running the test there.

Follow-up to https://chromium-review.googlesource.com/c/1099715/ and
https://chromium-review.googlesource.com/1098621

Bug: 852536
Change-Id: I42ffe80b4876ccc95be5f45d431d6c441fe11e73
Reviewed-on: https://chromium-review.googlesource.com/1100902Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567252}

TBR=charliea@chromium.org
NOTRY=true

Bug: 848900
Change-Id: I8fa3a3cad3515ec16ba19f558875be13910c902b
Reviewed-on: https://chromium-review.googlesource.com/1100960Reviewed-by: Emily Hanley <eyaich@chromium.org>
Commit-Queue: Emily Hanley <eyaich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567251}

Its semantics were a bit weird: It got set on initial sign-in (i.e. not
during a Chrome restart), and cleared again once we updated the auth
error state: Either to an error, if we failed to get an access token or
got an error from the sync server, or to "no error", if we successfully
connected to the sync server.
It had only a single call site, which only used it to suppress auth
errors while waiting_for_auth was true. However, according to the
above, that's an impossible state: Sync can not be in an auth error
state *before* being signed in, and the waiting_for_auth bit is cleared
when actually entering an auth error state.

Bug: 839834
Change-Id: Iefbf54a93ede54aabb2a244b3e429b5591bb9934
Reviewed-on: https://chromium-review.googlesource.com/1099162Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Commit-Queue: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567250}

After this CL, the focus checks performed by navigator.credentials.create()
requests will now succeed when called from the foreground tab in a browser
window, even if the window is not currently the active window. Invocations
from minimized windows and background tabs are still rejected. On platforms
with Visibility::OCCLUDED support, occluded windows are also considered to
be unfocused.

Furthermore, the CL has two side effects:
 -- Foreground WebContents that are currently showing a permission bubble
    or a web-modal dialog are now considered to be "focused" on all
    desktop platforms. The special handling in AuthenticatorImpl is no
    longer needed.
 -- On Linux, the foreground tab in a browser window on an inactive virtual
    screen is still considered to be focused.

While this may very well not be the right approach going forwards, it will
allow consistent behavior regardless of whether the WebAuthn UI is enabled
or disabled. (With UI enabled, focus checks are replaced by checking if the
WebAuthn dialog is currently shown.)

Bug: 849323
Change-Id: I3afc542bed3765be1e43c2fa348fc5b67a8b2aef
Reviewed-on: https://chromium-review.googlesource.com/1092859Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Reviewed-by: Mike Wittman <wittman@chromium.org>
Reviewed-by: Adam Langley <agl@chromium.org>
Commit-Queue: Balazs Engedy <engedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567249}

The first line of answers contains text and bolding that's calculated
server-side. That calculation is nearly identical to what we do Chrome-
side for non-answers. This change makes it so that we use the Chrome
calculation to avoid the problem were an old-but-still-matching answer
could be copied to the what-you-typed match and have the wrong bolding.

Because the first line of answers can have some additional text besides
the query, that additional text is added in a separate step.

Because we're no longer using the server-provided bolding, which used
HTML <b> tags, we no longer need the parsing of those tags that we were
previously using.

Finally, since there was code moving around in omnibox_text_view.cc
anyway, I made some simplifications based on the fact that this class
only ever has one render text.

Bug: 721820
Change-Id: I816c55cf9ff680dd922a18ef4cb9301543e1de25
Reviewed-on: https://chromium-review.googlesource.com/1070506Reviewed-by: Dave Schuyler <dschuyler@chromium.org>
Commit-Queue: Justin Donnelly <jdonnelly@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567248}

and "web_socket_scope". Since WebSocket is one word, these should be
"websocket" and "websocket_scope". Fix them.

blink: :DOMWebSocket and its tests contained variables name "web_socket"
Change-Id: I0d75c7a45a2a2dc85253be1387a80af78eda2c3a
Reviewed-on: https://chromium-review.googlesource.com/1098747Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567247}

https://webrtc.googlesource.com/src.git/+log/aeb0a6475bcc..d1f970dc435a


git log aeb0a6475bcc..d1f970dc435a --date=short --no-merges --format='%ad %ae %s'
2018-06-14 ivoc@webrtc.org Change echo detector to scoped_refptr
2018-06-14 jonasolsson@webrtc.org Remove unused WavFile::FormatAsString method.
2018-06-14 jonasolsson@webrtc.org Handle FileRotatingStreams with long file names
2018-06-14 qingsi@google.com Reland "Refactor the regathering of candidates in P2PTransportChannel."
2018-06-14 qingsi@google.com Add a DCHECK for null port in FakePortAllocator.
2018-06-14 steveanton@webrtc.org [Unified Plan] Clear RtpSender "SSRC" when the SDP has no send streams
2018-06-13 titovartem@webrtc.org Replace std:remove on vector::erase in streamparams_unittest.cc


Created with:
  gclient setdep -r src/third_party/webrtc@d1f970dc435a

The AutoRoll server is located here: https://webrtc-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng

BUG=chromium:None
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: If63cb57df482cacee75d2b81797ffc613384648a
Reviewed-on: https://chromium-review.googlesource.com/1100698Reviewed-by: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#567246}

An XHR must not be canceled if an history navigation happens in an
iframe.

Bug: 260144
Change-Id: Ia379eff010165f690c72834ae59eb90f19aece7a
Reviewed-on: https://chromium-review.googlesource.com/1087050Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Camille Lamy <clamy@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567245}

When ServiceManager starts, it needs to post sequence tasks.
Therefore, we need to create a TaskScheduler and setup the
MessageLoop for the main thread.

Pariculaly for mac, the Mac registaration of NSApp now happens before
EarlyInitialization. The registration has been moved from
BrowserMainParts::PreMainMessageLoopStart() to ContentMainDelegate's
subclasses which implement ContentMainDelegate::PreMainMessageLoopStart().

This is required by a follow up CL:
https://chromium-review.googlesource.com/c/chromium/src/+/1058131/

Change-Id: Ic67dace05b82fc44d6ab6d480ba0fecffe58fbf8
Reviewed-on: https://chromium-review.googlesource.com/1072387Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Commit-Queue: Xi Han <hanxi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567244}

The maximum compressed size of each MSZIP block is 32k + 12 bytes.
So that means the size can be 32k + 12 bytes.
However, the assert checks as follows.

assert compressed_size < chunk_size + 12

Reference : https://msdn.microsoft.com/en-us/library/ee178063(v=exchg.80).aspx

Bug: None
Change-Id: I0d991be2909f4447144fccad83155c5967382557
Reviewed-on: https://chromium-review.googlesource.com/1074768
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567243}

This is a reland of 66d17ca7

Original change's description:
> Make the ThirdPartyModulesBlocking feature work on all Windows versions
> 
> Change-Id: I0118d26fe9b7f11f2608dd66c10418e210393733
> Reviewed-on: https://chromium-review.googlesource.com/1083842
> Commit-Queue: Patrick Monette <pmonette@chromium.org>
> Reviewed-by: Greg Thompson <grt@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#566516}

Change-Id: Ie4c6c3767af38efe50e42012aa5f65fb480fac56
Reviewed-on: https://chromium-review.googlesource.com/1099976Reviewed-by: Greg Thompson <grt@chromium.org>
Commit-Queue: Patrick Monette <pmonette@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567242}

Change-Id: I9695d4c554ce45c339282dcd2c70adc1e83da557
Reviewed-on: https://chromium-review.googlesource.com/1099257
Commit-Queue: Sigurður Ásgeirsson <siggi@chromium.org>
Reviewed-by: Chris Hamilton <chrisha@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567241}

# This is an automated release commit.
# Do not revert without consulting chrome-pmo@google.com.
NOAUTOREVERT=true
TBR=mmoss@chromium.org

Change-Id: I847557277cd65eb48dd9d9ae5b5b27dc7e56d110
Reviewed-on: https://chromium-review.googlesource.com/1100898Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567240}

Sample failure:

[ RUN      ] ExtensionCrashRecoveryTest.ReloadIndependently
...
../../chrome/browser/extensions/extension_crash_recovery_browsertest.cc(92): error: Value of: extension
  Actual: false
Expected: true
Stack trace:
Backtrace:
  StackTraceGetter::CurrentStackTrace [0x00007FF7EE199480+80]
  testing::internal::UnitTestImpl::CurrentOsStackTraceExceptTop [0x00007FF7EE1B2BAA+90]
  testing::internal::AssertHelper::operator= [0x00007FF7EE1B26AA+90]
  ExtensionCrashRecoveryTest::CheckExtensionConsistency [0x00007FF7EDDE8C20+304]
  ExtensionCrashRecoveryTest::LoadTestExtension [0x00007FF7EDDE8204+692]
  ExtensionCrashRecoveryTest_ReloadIndependently_Test::RunTestOnMainThread [0x00007FF7EDDE9D37+103]

https://logs.chromium.org/v/?s=chromium%2Fbuildbucket%2Fcr-buildbucket.appspot.com%2F8943749196042516896%2F%2B%2Fsteps%2Finteractive_ui_tests__experimental__on_Windows-10-15063%2F0%2Fstdout

TBR=karandeepb@chromium.org

Bug: 846172
Change-Id: I56a0318d765f9a2b36a4a52e46f59e60ac9afd30
Reviewed-on: https://chromium-review.googlesource.com/1100352Reviewed-by: François Doray <fdoray@chromium.org>
Commit-Queue: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567239}

This CL implements filling based on WebForm and WebFormControlElement
unique renderer ids instead of complicated heuristics that are used
currently.

This CL contains:
1.Adding renderer ids to PasswordForm and PasswordFormFillData classes
2.Adding MOJO for PasswordFormFillData
3.Setting renderer ids in FormParser
4.Setting renderer ids in password_form_fill_data.cc
5.Filling using renderer ids in PasswordAutofillAgent
  - extracting to separate methods common code between new and old
filling
  - implementing finding username/password elements by renderer ids.

Bug: 831123
Change-Id: Ie29964db51014b140e806a6e3f78c9c854a8df34
Reviewed-on: https://chromium-review.googlesource.com/1090729Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Vaclav Brozek <vabr@chromium.org>
Commit-Queue: Vadym Doroshenko <dvadym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567238}

Reduces the max shard duration of net_unittest on the asan/tsan builders by about 50%.

https://chromium.googlesource.com/external/github.com/google/googletest.git/+log/9077ec7efe5b..ce468a17c434

$ git log 9077ec7ef..ce468a17c --date=short --no-merges --format='%ad %ae %s'
2018-06-13 misterg Docs sync/internal
2018-06-13 misterg Doc sync/internal
2018-06-12 tikuta Reduce the number of strcmp calling while initialization
2018-06-11 misterg Sync with internal docs
2018-06-11 misterg Sync with internal docs

Created with:
  roll-dep src/third_party/googletest/src
R=dpranke@chromium.org,thakis@chromium.org
BUG=794372

Change-Id: I704490e983697784fcc73c6fa7462bfb35a0694e
Reviewed-on: https://chromium-review.googlesource.com/1100670
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567237}

https://skia.googlesource.com/skia.git/+log/b57a861f183b..f018b7d607a0


git log b57a861f183b..f018b7d607a0 --date=short --no-merges --format='%ad %ae %s'
2018-06-14 brianosman@google.com SkColorSpaceXformSteps improvements and tests


Created with:
  gclient setdep -r src/third_party/skia@f018b7d607a0

The AutoRoll server is located here: https://autoroll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=csmartdalton@chromium.org

Change-Id: I61f2b001fcce3b2d58ffd49d61400e2ba4185bf4
Reviewed-on: https://chromium-review.googlesource.com/1100699Reviewed-by: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#567236}

https://crrev.com/8f14a9d0b7c593e0 enabled opt-in [[nodiscard]] on STL
on Windows build, however, it's unavailable on cl.exe in C++14 mode.
https://ci.chromium.org/buildbot/chromium.fyi/WinMSVC64%20Goma%20Canary/7727

This CL disables it back on cl.exe.

Bug: 852240
Change-Id: Ibfda257eadd6e188f7baa0472785bd3092e76600
Reviewed-on: https://chromium-review.googlesource.com/1100602Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567235}

Previously if the scroll source was not initially composited then the cc-side
ScrollTimeline would never get a valid ElementId. This CL fixes that; we now
update the cc side ScrollTimeline every time the scroll source changes
compositing state.

Bug: 776533
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I0e8e37d867c4a4708fee6f4d0adf6e6e86ecfaff
Reviewed-on: https://chromium-review.googlesource.com/1055881
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567234}

Files directly under platform/ (not in platform/*/) should find
the right home.  In case of decimal.h, the right home should be
platform/wtf/.

No-Presubmit: true
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I798c61809332b09bf428297d31b0a757177876be
Reviewed-on: https://chromium-review.googlesource.com/1100730Reviewed-by: Yuta Kitamura <yutak@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567233}

The FormData -> PasswordForm password needs to distinguish three levels
of interactability of fields: fields already interacted with, fields
likely to be interacted with, and those which are unlikely.

This is what the old parser in password_form_conversion_utils.cc called
filtering levels.

The interactability is useful when identifying whether an obtained
result is potentially useful. Also, the structural analysis only
should consider the fields with best interactability.

This CL introduces the concept of interactability and restricts the
structural analysis ("base heuristics") to fields with best
interactability.

The CL does not introduce interactability-based penalties yet, because
the confidence rating is not implemented yet. (See details in the design
doc linked from the bug description.)

Bug: 845426
Change-Id: Ib0dd2f9837c537e4d64432a35b7ba2f5f8e72403
Reviewed-on: https://chromium-review.googlesource.com/1099060Reviewed-by: Vadym Doroshenko <dvadym@chromium.org>
Commit-Queue: Vaclav Brozek <vabr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567232}

Bug: 851320
Change-Id: I562fe492be73b0ad8929d8ae8be158230103157f
Reviewed-on: https://chromium-review.googlesource.com/1095640Reviewed-by: Raymond Toy <rtoy@chromium.org>
Commit-Queue: Luke Bj <lukebjerring@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567231}