GitLab

In order to turn OOP FontConfig queries from Sandbox IPC filedescriptor
based messages to Mojo messages, we need FontService to handle
additional queries for font fallback, retrieving render style and
performing font matching in a PPAPI context. These methods are moving
from sandbox_ipc_linux.cc as well as font_utils_linux.h and will be
temporarily duplicated until the methods will be removed from
where they were duplicated from.

For the design doc, please refer to crbug.com/839344.

Bug: 849923
Change-Id: If0197eae2c9bba8495c065d641b3fef39e403a83
Reviewed-on: https://chromium-review.googlesource.com/1087951
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Reviewed-by: Bill Budge <bbudge@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569974}

The page flip code mixes two error handling styles and in many cases
returns the same status (or in some cases, inconsistent statuses) through
the return value and also via the SwapCompletionCallback.

The page flip code also supports two modes: real page flips and test page
flips, which are used to validate configurations before use. Real page
flips crash the GPU process if the return value indicates failure, but
obviously this is not expected to occur so in practice those always
return success, and pass status information through the
SwapCompletionCallback. Test page flips are the opposite: they must
return their status in the return value, and pass a dummy completion
callback which ignores its arguments.

There are actually no asynchronous failure cases, despite a fair amount
of code trying to account for that possibility such as the coalescing of
SwapResults in PageFlipRequest. We can take advantage of this to avoid
passing the SwapCompletionCallback into most functions, and simply use
the return value as the only status return. The only complication is that
successful completion is always asynchronous, and may even require
tracking multiple underlying page flip events, as in hardware mirroring
scenarios.

This patch handles that issue by registering PageFlipCallbacks for all of
the individual page flip events as usual, but only passing ownership of
the SwapCompletionCallback into the PageFlipRequest at the last minute,
after all of the individual page flips have been submitted succesfully.

After hiding the SwapCompletionCallback from most of the DRM internals,
test page flips no longer need to construct a dummy
SwapCompletionCallback. They also don't need to construct any
PageFlipCallbacks, since they don't generate any page flip events - this
simplifies that logic as well by moving construction of each
PageFlipCallback to immediately after a successful page flip request.
Moving creation of those callbacks later also removes any requirement to
make manual calls to PageFlipRequest::Signal to fixup failure cases.

Since failures of real page flips triggered by SchedulePageFlip() simply
crash the process, there is no need for a return value. This patch moves
the CHECK() which cause these crashes inside of SchedulePageFlip(), and
removes the return value.

As a result, TestPageFlip() and all of the internal methods called via
ActualSchedulePageFlip() use return values exclusively for status
information, and never see the SwapCompletionCallback.
SchedulePageFlip(), on the other hand, receives the SwapCompletionCallack
and uses it exclusively for its status, and returns void.

Bug: 851997
Test: unit tests, various display configurations on cros

Change-Id: I87408275b0958281ef79a6b5086a38b2c3c08ee1
Reviewed-on: https://chromium-review.googlesource.com/1104859
Commit-Queue: Michael Spang <spang@chromium.org>
Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569973}

This CL is a pure refacotring.

Bug: 846618
Change-Id: Ia858ad02d5ae14db59eb5bc947d6463e08f98ae8
Reviewed-on: https://chromium-review.googlesource.com/1113090Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569972}

Display configurator will not configure mirror pairs between devices (see
AllDisplaysOnSameDevice() in ui/display), so remove code attempting to
support this.

Bug: 851997
Test: hardware mirroring on cros

Change-Id: Ie2fdc9f42423be1cd8efe7c59d43001e6096e935
Reviewed-on: https://chromium-review.googlesource.com/1104858
Commit-Queue: Michael Spang <spang@chromium.org>
Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569971}

RefPtr is now scoped_refptr.

Change-Id: Ifdf5832c631254671a664beb185e001476cb9cb5
Reviewed-on: https://chromium-review.googlesource.com/1111900
Commit-Queue: Yuta Kitamura <yutak@chromium.org>
Reviewed-by: Yuta Kitamura <yutak@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569970}

Flaky on mac and win7.

TBR=adithyas@chromium.org

Bug: 855873
Change-Id: I0d55390244a7e96e478a01bd5be254d958a41147
Reviewed-on: https://chromium-review.googlesource.com/1113082Reviewed-by: Darren Shen <shend@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569969}

Flaky on Windows

TBR=tangltom@chromium.org

Bug: 855867
Change-Id: I32be5fa7473203dea8ab3dc25fbb9b5b68edd737
Reviewed-on: https://chromium-review.googlesource.com/1113087Reviewed-by: Darren Shen <shend@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569968}

This CL fixes ReferrerPolicy handling in module script loading. Before this CL,
FetchClientSettingsObjectSnapshot's referrer policy is used, but this is wrong.
The spec requires to use ScriptFetchOptions' referrer policy.

  // The "set up the module script request" algorithm:
  "Set request's cryptographic nonce metadata to options's cryptographic nonce,
  ..., and its referrer policy to options's referrer policy."
  https://html.spec.whatwg.org/multipage/webappapis.html#set-up-the-module-script-request

Specifically, this CL introduces |referrer_policy_| field in ScriptFetchOptions
class as spec'ed and propagates it to the entire path of module script loading.

ScriptFetchOptions's referrer policy can be set to following values:

- <script>'s "referrerpolicy" attribute is used for <script type='module'>. This
  hasn't been implemented yet (see https://crbug.com/841673), so the current
  document's referrer policy is used to keep the backward compatibility.

  // The "prepare a script" algorithm:
  "20. Let referrer policy be the current state of the element's referrerpolicy
  content attribute."
  "22. Let options be a script fetch options whose cryptographic nonce is
  cryptographic nonce, ..., and referrer policy is referrer policy."
  https://html.spec.whatwg.org/multipage/scripting.html#prepare-a-script

- <link>'s "referrerpolicy" attribute is used for modulepreload.

  // The "Link type "modulepreload"" algorithm:
  "9. Let referrer policy be the current state of the element's referrerpolicy
  attribute."
  "10. Let options be a script fetch options whose cryptographic nonce is
  cryptographic nonce, ..., and referrer policy is referrer policy."
  https://html.spec.whatwg.org/multipage/links.html#link-type-modulepreload

- The default referrer policy is used for module workers and worklets. This is
  the reason why this CL changes test expectations of workers and worklets.

  // The "fetch a module worker script graph" algorithm:
  "2. Let options be a script fetch options whose cryptographic nonce is the
  empty string, ..., and referrer policy is the empty string."
  https://html.spec.whatwg.org/multipage/webappapis.html#fetch-a-module-worker-script-tree

Change-Id: Ic0f9e6667cd1b84f74d86fcc948451c1d2f8191f
Bug: 842553, 855963
Reviewed-on: https://chromium-review.googlesource.com/1111743
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569967}

Bug: 852075
Change-Id: Ibdd7001d62b9adc0f3d2c74b12f77e904cf27d06
Reviewed-on: https://chromium-review.googlesource.com/1112706
Commit-Queue: Cathy Li <chili@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569966}

There's a number of places that overlay stacks are copied inside the DRM
code. Previously this was safe because overlay plane stacks were
self-contained, but now they include unowned pointers to fences. Those
fences are freed immediately after submitting a frame and left dangling
in any copies of the overlay plane stack.

Fix the code to duplicate the fences when copying planes. We should
reduce the number of places we are copying overlay stacks, but that is
not done here; this patch only makes copying safe again. It also
makes copying an explicit call; the copy constructor is gone.

TBR: dcastagna@chromium.org
Bug: 851997
Test: Ran chrome & ozone_demo --use-gpu-fences on eve
Change-Id: Ib21033aaf43a6765c3c46fce60991ada941ef343
Reviewed-on: https://chromium-review.googlesource.com/1097209
Commit-Queue: Michael Spang <spang@chromium.org>
Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569965}

Bug: 855117

Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I730e489bf6880252ce5474551e4c624d9baa18d7
Reviewed-on: https://chromium-review.googlesource.com/1112704Reviewed-by: Tien-Ren Chen <trchen@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569964}

|HandleLocalTime| uses |localtime| in the assumption that sandbox
handler process is single-threaded. This assumption is not correct
anymore. See |SandboxHostLinux::Init| and |ipc_thread_|.

The proposed fix is to replace unsafe |localtime| function call with
threadsafe |localtime_r| posix equivalent.

Change-Id: I20c9576557df414b19c30c51ba233f62cfb8be28
Reviewed-on: https://chromium-review.googlesource.com/1111704Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org>
Commit-Queue: Иван Афанасьев <ivafanas@yandex-team.ru>
Cr-Commit-Position: refs/heads/master@{#569963}

Allow a SourceId to be obtained and the url set to
app://[chrome|play]/id.

Add a new SourceType to govern the creation of urls
with scheme "app".

Bug: 841671
Change-Id: I1ed98722cdeb78ffd9944548901089e28f64181a
Reviewed-on: https://chromium-review.googlesource.com/1058736Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Paul Dyson <pdyson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569962}

https://chromium.googlesource.com/angle/angle.git/+log/f5fd5c6c6a21..a75aa3b2c314


git log f5fd5c6c6a21..a75aa3b2c314 --date=short --no-merges --format='%ad %ae %s'
2018-06-25 jiawei.shao@intel.com ES31: Support compute shader shared variables in HLSL


Created with:
  gclient setdep -r src/third_party/angle@a75aa3b2c314

The AutoRoll server is located here: https://angle-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=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=cwallez@chromium.org

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

Change-Id: I7bc5d61879ad726029b2cb8f59ab00af2b8f5c4a
Reviewed-on: https://chromium-review.googlesource.com/1112655
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Reviewed-by: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569960}

Reduce flakiness in layout test http/tests/misc/resource-timing-sizes-tags.html
by:
* Using the PerformanceObserver interface to reliably detect when a performance
  entry is available.
* Removing the invisible objects before completion to reduce the risk that it
  will be misdetected as a DOM test.

Other miscellaneous cleanups have been applied.

BUG=786235

Change-Id: Iaefbd5ee6adecad23ef39035091ba454523413f8
Reviewed-on: https://chromium-review.googlesource.com/1111893Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Commit-Queue: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569959}

DriveTestVolume::CreateEntry calls CreateFile|Directory and then calls
CheckForUpdates. CreateFile|Directory also call CheckForUpdates: seems
redundant given that the caller does it for them.

Bug: 836254
Change-Id: Ia778a64d0195925a827c40dc6dfdf3877a6611d3
Reviewed-on: https://chromium-review.googlesource.com/1110077
Commit-Queue: Noel Gordon <noel@chromium.org>
Reviewed-by: Stuart Langley <slangley@chromium.org>
Reviewed-by: Sam McNally <sammc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569958}

Flaky on linux and mac.

TBR=fdoray@chromium.org

Bug: 855874
Change-Id: If2699ad034204225497ed2d9e01f5082a3e0dd17
Reviewed-on: https://chromium-review.googlesource.com/1112895Reviewed-by: Darren Shen <shend@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569957}

Bug: 855859
Change-Id: Iaa0733f8c897d13323cf88c88e77d28f7892e3e2
Reviewed-on: https://chromium-review.googlesource.com/1113028Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569956}

https://skia.googlesource.com/skia.git/+log/ebf160f308b6..a2b5b6467f34


git log ebf160f308b6..a2b5b6467f34 --date=short --no-merges --format='%ad %ae %s'
2018-06-25 csmartdalton@google.com ccpr: Enable ccpr by default


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

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=jcgregorio@chromium.org

Change-Id: I17aca234f3c390cf0e31e6ce41b5b84a609ff984
Reviewed-on: https://chromium-review.googlesource.com/1112956Reviewed-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@{#569955}

This patch changes NGInlineNode::ComputeMinMaxSize to use
NGLineInfo::Width() instead of accumulating the list of
NGInlineItemResult.

This fixes min-/max-content size to include the width of
hyphens.

During the fix, an uninitialized variable was found when
NGLineInfo was re-used across different NextLine(). Re-using
NGLineInfo isn't much gain, this was prohibited to avoid rare
code path. Also a few DCHECK were added to ensure accumulated
with is in sync.

A test for min-content of hyphened line was added. There are
two tests, but both use table to compute it, and that they
may fail to test if table sizing is broken. The new test uses
'min-content' directly.

Bug: 636993
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: Ibc7a3a2dcbf6a70a06bc974eb69dd47b23ad72fe
Reviewed-on: https://chromium-review.googlesource.com/1111895
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569954}

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

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

Add the scheme "app" for logging apps.

Bug: 841671
Change-Id: I05af14327dba5ad422b9784205229f914641aa1a
Reviewed-on: https://chromium-review.googlesource.com/1053342
Commit-Queue: Paul Dyson <pdyson@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569952}

Bug: 845079
Test: unit_tests
Change-Id: I5634751508c852e63f5f0de91ae1be0933ee4bd3
Reviewed-on: https://chromium-review.googlesource.com/1109604
Commit-Queue: Yuichiro Hanada <yhanada@chromium.org>
Reviewed-by: Shu Chen <shuchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569951}

This patch implements Certificate Transparency verification for signed
exchanges. The logic in SignedExchangeHandler::VerifyCT() is basically
the same as SSLClientSocketImpl::VerifyCT(), but uses OCSP and SCT
extracted from CBOR cert chain.

Bug: 815025
Change-Id: I2b35c460bb69509419e80767ae35ed2b16c2a4ee
Reviewed-on: https://chromium-review.googlesource.com/1056776Reviewed-by: Ryan Sleevi <rsleevi@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569950}

Enable views_mus_unittests on both lsan/asan and on msan, it should pass now.

Enable ozone_unittests and wayland_client_perftests on just msan
(they don't pass on lsan/asan yet).

With this, linux_chromeos_rel_specific_gtests_asan_bringup is identical to
linux_chromeos_rel_specific_gtests and can be removed, and because of _that_,
chromium_memory_chromiumos_asan_gtests is identical to linux_chromeos_rel_gtests
and can also be removed.

As a consequence, tests added to the cros rel bots will be added to the
memory bots automatically going forward.

TBR=kbr

Bug: 843511
Bug: 855580,855588,855584,855585,855583
Change-Id: I6a28ebae4c9005ce508f8caef07679a1bb50285c
Reviewed-on: https://chromium-review.googlesource.com/1112957Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569949}

history_item.h is used in 1900+ compilation units, and this CL reduces
estimated pre-processed size of history_item.h from 5.78MB to 2.03MB.

Bug: 242216
Change-Id: I1db28440031fd826349278febd2ffa79af58f1ca
Reviewed-on: https://chromium-review.googlesource.com/1111774Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569948}

Now matching go/crostini-strings.

Bug: 849900
Change-Id: I019c4888b4e54df177158a0c566a6477088aca74
Reviewed-on: https://chromium-review.googlesource.com/1111742Reviewed-by: Ben Wells <benwells@chromium.org>
Commit-Queue: Nicholas Verne <nverne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569947}

Disabling flaky test on mac

TBR=bbudge@chromium.org

BUG=707068

Change-Id: Ib401bfa6ef15e336fdcbe6ae231b97ec7c6cfdd9
Reviewed-on: https://chromium-review.googlesource.com/1112890Reviewed-by: Darren Shen <shend@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569946}

When --ipc-dump-directory=DIR is passed, outgoing Mojo messages from
the renderer are written to:

DIR/INTERFACE_NAME/CONNECTOR_ID/NUM.METHOD_NAME.mojomsg

Where INTERFACE_NAME is the interface name of the message,
CONNECTOR_ID is a random number unique to each instance of a Connector,
METHOD_NAME is the the name of the method being called, and
NUM is a number used for ordering messages for a single connector.

Bug: 607649

Change-Id: I5b8735d3ca94707c6033563cb8dcc21e0f815ac3
Reviewed-on: https://chromium-review.googlesource.com/1070550Reviewed-by: Martin Barbella <mbarbella@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Oliver Chang <ochang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569945}

VisibleContentRect() and VisibleContentSize() are based on
scroll_offset_ (which is always (0, 0)), and Size() with scrollbars
possible excluded -- but there are no scrollbars any more. Replace
all of the calls with Size().

BUG=823365
TBR=dmazzoni@chromium.org

Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ieb41515bf53e20762aca9f81df413ebb397c9f5d
Reviewed-on: https://chromium-review.googlesource.com/1112067
Commit-Queue: Stefan Zager <szager@chromium.org>
Reviewed-by: Steve Kobes <skobes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569944}

The AutoRoll server is located here: https://fuchsia-sdk-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=luci.chromium.try:fuchsia_arm64_cast_audio;luci.chromium.try:fuchsia_x64_cast_audio
TBR=cr-fuchsia+bot@chromium.org

Change-Id: Ie51e83301a9a31d16193d0c20d4f37ba5b25c664
Reviewed-on: https://chromium-review.googlesource.com/1113024
Commit-Queue: Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#569943}

According to spec[1], when document object doesn't have browsing
context, it should throw a "SecurityError" DOMException.

[1] https://html.spec.whatwg.org/multipage/origin.html#dom-document-domain

BUG=850432

Change-Id: Ibc12decadb2405bb5f3b190d60ad65e1ee21303b
Reviewed-on: https://chromium-review.googlesource.com/1112937Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569942}

This creates safer code overall.
If start and end AXPositions are invalid for any reason we didn't contemplate, the browser doesn't crash but returns an AXRange that is explicitly marked invalid.
It's also a nice workaround until CSS decorations are supported in AXPosition.

TBR=dmazzoni@chromium.org, aleventhal@chromium.org

Bug: 852266
Change-Id: I94db8aeda296690a842b674ea27743dc573205d7
Reviewed-on: https://chromium-review.googlesource.com/1112968Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Commit-Queue: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569941}

These updated strings were provided by UX.

This CL is almost identical to jordynass@'s CL here:
https://chromium-review.googlesource.com/c/chromium/src/+/1112899

I copied it and am submitting it as a separate CL since all strings
are supposed to be landed before the week starting 6/25.

TBR=dpapad@chromium.org

Bug: 824568
Change-Id: I2eed76d0ace964947974eb7399354cb8a08bda9a
Reviewed-on: https://chromium-review.googlesource.com/1113017Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569940}

Also moves it's coordinator to history and creates HistoryClearBrowsingDataLocalCommands delegate.

Bug: 854882
Change-Id: Ia408681d5d559b1ae2da38315436fc93a7591489
Reviewed-on: https://chromium-review.googlesource.com/1111077
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Reviewed-by: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569939}

This reverts commit 3bcc71d8.

Reason for revert: appears to break official builds due to how the cipd variable is flattened.

Original change's description:
> Add luci-go tool to be fetched via CIPD
>
> Do not remove the adhoc mechanism on GCS that predates CIPD yet, as the recipes
> need to be updated.
>
> Change analyze to not ignore changes to isolate.
>
> R=​tandrii@chromium.org
>
> Bug: 851596
> Change-Id: Ic068db83dea4c3a0f17b55181de523b16c9838a5
> Reviewed-on: https://chromium-review.googlesource.com/1097623
> Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
> Reviewed-by: John Budorick <jbudorick@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#569688}

TBR=maruel@chromium.org,tandrii@chromium.org,ehmaldonado@chromium.org,jbudorick@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

No-Presubmit: true
Bug: 851596
Change-Id: I3717c6b0ebf68b08908037850d122727e41bf192
Reviewed-on: https://chromium-review.googlesource.com/1112823
Commit-Queue: John Budorick <jbudorick@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569938}

On Win, ARIA switches are equivalent to toggle buttons.
We need to expose both the pressed and checked states instead of only checked.
This fixes NVDA's announcement of the toggling of switches to on, whilst minimally affecting Jaws.
Jaws now reads "<switch name> on pressed" instead of "<switche name> on".
R=aleventhal@chromium.org, suproteem@chromium.org
Bug: 844021
Tested: manually with Jaws and NVDA, browser tests


Change-Id: I9ce4936002bf1a3cf0b99c73a73385c0a32ff3fc
Reviewed-on: https://chromium-review.googlesource.com/1101849
Commit-Queue: Nektarios Paisios <nektar@chromium.org>
Reviewed-by: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569937}

Bug: 855588
Test: ozone_unittests
Change-Id: I29ca5cc777d1e835bb2279959d9a390e2475025d
Reviewed-on: https://chromium-review.googlesource.com/1112961
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Antonio Gomes <tonikitoo@igalia.com>
Cr-Commit-Position: refs/heads/master@{#569936}

Change-Id: I5bfa51b5f9d16c1580febab4542be6aac3ccec5a
Reviewed-on: https://chromium-review.googlesource.com/1104898
Commit-Queue: Rob Buis <rbuis@igalia.com>
Reviewed-by: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569935}