GitLab

For Chromecast, Content Shell, and non-monochrome Clank/Webview:

The Crashpad handler is a standalone executable, packaged like a
loadable module and named libcrashpad_handler.so in order to not be
ignored by Android's APK installer.

For Monochrome:

The Crashpad handler is linked into libmonochrome.so. At crash-time
/system/bin/app_process{32,64} is exec-ed, running CrashpadMain.java
which loads libmonochrome.so and runs the native HandlerMain().

This strategy is not used for non-monochrome APKs (i.e. pre-N) because
on L, Android's loader is not yet capable of loading native libraries
from the APK. This is normally performed by the Chromium linker which
can't be used by CrashpadMain.java because /system/bin/app_process
doesn't initialize the process like a normal Android application
(specifically, no ContextImpl has been created, so any calls to e.g.
appContext.getApplicationInfo() will segfault).

Binary-Size: MonochromePublic.apk increases in size by 100 KB.
ChromeModernPublic.apk increases in size by 203KB (587 KB
increase in install size because libcrashpad_handler.so is extracted
from the APK). Possible mitigations for this increase are TODO:

For J, K: We could link the handler directly into libchrome.so and let
that be our handler executable. This would de-dup portions of libbase
that are currently linked into both libchrome.so and
libcrashpad_handler.so.

For L, M: It might be possible to get the chromium linker (or Bionic's
linker on M) to dlopen libchrome.so from the APK for a trampoline
libcrashpad_handler.so to de-dup libbase.

Bug: crashpad:30
Change-Id: If5b3752f26455e5c7aef3278b4bd2076ef1b7b65
Reviewed-on: https://chromium-review.googlesource.com/1150774Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: agrieve <agrieve@chromium.org>
Reviewed-by: Mark Mentovai <mark@chromium.org>
Reviewed-by: Richard Coles <torne@chromium.org>
Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Commit-Queue: Joshua Peraza <jperaza@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594853}

Bug: 885274
Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: Iead2e9e13997d6d12987c4a40e02876d55108523
Reviewed-on: https://chromium-review.googlesource.com/1244596
Commit-Queue: Danyao Wang <danyao@chromium.org>
Reviewed-by: Mike Dougherty <michaeldo@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594852}

The feature "use invalid data" for possible type uploads should
always be on, meaning that the client will send up votes regardless
of the validity states. This is because we are uploading the validity
states of each possible type, and we can evaluate the relevance of
invalid data on the server side.

Also, the validity of UNKNOWN types should be set to UNVALIDATED for
the consistency.

Change-Id: Ia7234a128b04b975f6fb1bfd4d4dc131547530a8
Reviewed-on: https://chromium-review.googlesource.com/1249907Reviewed-by: Roger McFarlane <rogerm@chromium.org>
Reviewed-by: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Commit-Queue: Parastoo Geranmayeh <parastoog@google.com>
Cr-Commit-Position: refs/heads/master@{#594851}

BUG=860827

Change-Id: I403f2b4ada07242cc035ebb12ec1d1f6145ac42d
Reviewed-on: https://chromium-review.googlesource.com/1249838Reviewed-by: Gabriel Charette <gab@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594850}

Change-Id: I138c4e57f47af2750dc66cea9981a455e5d5b60f
Reviewed-on: https://chromium-review.googlesource.com/1246786
Commit-Queue: apacible <apacible@chromium.org>
Reviewed-by: CJ DiMeglio <lethalantidote@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594849}

This is a first step toward mash support for multiple remote mojo apps
supplying AX node trees.

* Let AXHostService generate the AXTreeID as a side-effect of being
  an AXHostDelegate
* Inform the remote app of its AXTreeID when it connects
* Push the ID into ash so it can be used for views focus support.
  This won't work for multi-process mash, but is fine for today's
  shortcut viewer app and probably for SingleProcessMash. Longer
  term we should probably use aura::Window properties for this.

See go/mash-ax-node-tree for notes

Bug: 888147
Test: updated views_mus_unittests, unit_tests, etc.
Change-Id: I2400ab02d8c504a0a041646bc694976458b3228b
Reviewed-on: https://chromium-review.googlesource.com/1246595
Commit-Queue: James Cook <jamescook@chromium.org>
Reviewed-by: Sam McNally <sammc@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594848}

views_mus_unittests was calling mojo::core::Init() multiple times, which
leaks. The fix is to move the Init() call to the TestSuite as well as
setting up the ipc thread.

BUG=888533
TEST=test only changes

Change-Id: I852ca0ab4736aa7a4a18d3c650fa6122b320eb9d
Reviewed-on: https://chromium-review.googlesource.com/1249810Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594847}

This CL is adding the stack sampling tracing category to the GPU scenario.
Slow-reports will now get the stack sampling on the GPU main thread when
the user is running the "BENCHMARK_GPU" scenario.

R=piman@chromium.org, ssid@chromium.org, oysteine@chromium.org

Bug: 888580
Change-Id: Ib6d6e6c98a77a11a1ee24d6223e6358115467a84
Reviewed-on: https://chromium-review.googlesource.com/1249909Reviewed-by: oysteine <oysteine@chromium.org>
Reviewed-by: Siddhartha S <ssid@chromium.org>
Commit-Queue: Etienne Bergeron <etienneb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594846}

The RTCQuicTransport web API needs to use the underlying core QUIC
library. In order to use this API we need to create a shim of the
library that subclasses the QuicSession and QuicStream. This change
subclasses the QuicSession and has some basic implementation for
establishing a connection.

Bug: 874296
Change-Id: I63acd4913abc23733521157bd1aca4a3d1301c65
Reviewed-on: https://chromium-review.googlesource.com/1170125Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Seth Hampson <shampson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594845}

X events have a timestamp which is only well defined relative to the X11 Server
time. The previous computation for timestamp for X11 events was making the
assumption that Server time and Chrome time were the same. This assumption is
not always true -- this is likely the root cause of "bad" timestamps observed in
https://bugs.chromium.org/p/chromium/issues/detail?id=650338#c1

This CL changes event timestamp computation to make a roundtrip to the X11
Server to get an accurate base::TimeTicks. This logic was lifted out of the
responsiveness calculator, which was already doing this computation. The latter
will subsequently be changed to use the computation in this CL.

Change-Id: I963019cd8bfb8ce14e06b3743a159c9c85f2cb82
Bug: 859155
Reviewed-on: https://chromium-review.googlesource.com/1249383Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594844}

BUG=790343

Change-Id: Ifb62914414b09eed794387ab5073fc973532f162
Reviewed-on: https://chromium-review.googlesource.com/1249807Reviewed-by: Ryan Tseng <hinoka@chromium.org>
Commit-Queue: Jao-ke Chin-Lee <jchinlee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594843}

Bug: 888188
Change-Id: I9056c918ceda50d5c50d7dfbadef5c22f7e80d34
Reviewed-on: https://chromium-review.googlesource.com/1246948Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Ryan Cui <rcui@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594842}

When Contextual Search selects a word in response to tap there's
a potential race condition between two messages in the SelectionClient
interface: onSelectionChanged and selectWordAroundCaretAck.  In cases
where the Ack is called first the selection controller doesn't have a
valid word and asserts.

This change extracts the word from the surrounding text and updates
the selection controller to ensure that it knows about the selected
word.

BUG=889657

Change-Id: Ifbc65d199b179df31fed65ae4b0b06dc13cf6213
Reviewed-on: https://chromium-review.googlesource.com/1248021Reviewed-by: Shimi Zhang <ctzsm@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Donn Denman <donnd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594841}

Since we can't rely on no_sanitize attributes on Windows, use the gn
configs to ensure LF isn't instrumented with ASAN.
This fix is hopefully temporary, ideally we can get clang-cl to respect
the no_sanitize attribute.

Bug: 883948
Change-Id: Ia4854d5f5b9148d175fa2f5f90bd9b34f064e064
Reviewed-on: https://chromium-review.googlesource.com/1249150Reviewed-by: Max Moroz <mmoroz@chromium.org>
Commit-Queue: Jonathan Metzman <metzman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594840}

Add a separate asynchronous loading view for downloads and integrate it
into the image class.  This includes
the following view classes for downloads home:

- AsyncImageView
- SquareAsyncImageView
- ForegroundRoundedCornerImageView

Each of these will be used for different components in the future
downloads home UI.

BUG=868554

Change-Id: I1b5afbaba85be701e607f1f97ae705b4ae83095d
Reviewed-on: https://chromium-review.googlesource.com/1240507Reviewed-by: Theresa <twellington@chromium.org>
Reviewed-by: Shakti Sahu <shaktisahu@chromium.org>
Commit-Queue: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594839}

Add a unittest to verify that permissions.contains() and
permissions.getAll() correctly return the current permissions for an
extension, even if it's affected by the runtime host permissions
feature.

Bug: 889654
Change-Id: I1ec42ed12208647cbee5784e4908a196e4b69994
Reviewed-on: https://chromium-review.googlesource.com/1247226Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594838}

This improves BGPT testing, and slims GraphicsLayer a bit.

Bug: 883949
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I77d5108dd2309de33a52ca90e3592c2d22ea28a0
Reviewed-on: https://chromium-review.googlesource.com/1247037
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594837}

Added histograms for:
- Assistant Service start time
- Get settings request time
- Count number of timout triggers

Also update the timeout to 15s.

Bug: b/116466382
Test: Manual Test
Change-Id: I0bf23962e28b61cb08970d11e47b702eb1c721f9
Reviewed-on: https://chromium-review.googlesource.com/1246664Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Yue Li <updowndota@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594836}

The issue here was the autocomplete feature, not autofill.
Autocomplete is disabled when the attribute is set to off.

Bug: 869516
Change-Id: Ib18953ed5e147cf6bab87b2c389ac75e83be13cd
Reviewed-on: https://chromium-review.googlesource.com/1249506
Commit-Queue: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594835}

This CL moves common logic between chrome & chromecast into a
common ui/views class.  Chrome/Chromecast specific logic differences
are handled in a delegate class.  Name/scope of this delegate may
change as we refactor move duplicate code out. Part of an on going
effort to eliminate duplicate code introduced when automation API
was added to Chromecast.

Test: Manual verification on chromecast (estelle) and chromeos (tidus)
Bug: 837773
Change-Id: Ia73513b09550d089daf09c89dd1fdda11bcacd4a
Reviewed-on: https://chromium-review.googlesource.com/1234363Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: David Tseng <dtseng@chromium.org>
Reviewed-by: Alex Sakhartchouk <alexst@chromium.org>
Commit-Queue: Randy Rossi <rmrossi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594834}

Getting size of full screen window now works correctly on all desktop
platforms. Re-enable Python-based ChromeDriverTest.testWindowFullScreen.

Bug: chromedriver:1945
Change-Id: I57a4b4003b37d174a8a9a5573453fd861845b948
Reviewed-on: https://chromium-review.googlesource.com/1249831Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Commit-Queue: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594833}

Switch stability proto's renderer crash count to include all renderer
crashes that result in a minidump rather than just foreground.

Pros:
- Align renderer crash counting with GPU crash counting
- Closer alignment with crashes that are uploaded
  - Every crash resulting in a minidump is a candidate to be uploaded
- Background renderer crashes are real crashes and should be fixed

Cons:
- Foreground renderer crashes are certain to cause a bad user experience
  while background crashes do not necessarily do so.

We are testing this out and keeping the rest of the crash pipeline the
same so that we can continue to compare old vs new metrics. If it does
not result in poor prioritization, this change will stick.

Full context: http://g/clank-crash/hZJyq3PJC3g

Bug: 839017
Change-Id: Iab8d6bdae993fbe3d41932719b9cecc5a6c450b8
Reviewed-on: https://chromium-review.googlesource.com/1246462Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Commit-Queue: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594832}

This CL adds logic to dismiss the heavy page capping InfoBar after 8
seconds of no requests being finished on the page. The actual time is
field trial configurable. This also adds a browser test to check this
behavior.

Bug: 888817
Change-Id: I7332918b4590f2f8cd70db365af8dce60f26956c
Reviewed-on: https://chromium-review.googlesource.com/1242173Reviewed-by: Evan Stade <estade@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Commit-Queue: Ryan Sturm <ryansturm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594831}

https://chromium.googlesource.com/catapult.git/+log/4e651334d46b..7a4e890f252c


git log 4e651334d46b..7a4e890f252c --date=short --no-merges --format='%ad %ae %s'
2018-09-27 simonhatch@chromium.org Re-enable symbolize_trace_end_to_end_test_slow.SymbolizeTraceEndToEndTest.testMacv2


Created with:
  gclient setdep -r src/third_party/catapult@7a4e890f252c

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

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

BUG=chromium:888947
TBR=sullivan@chromium.org

Change-Id: I122717fbc2aebcff1d1d190b2a75049b420c2d07
Reviewed-on: https://chromium-review.googlesource.com/1249634Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#594830}

Change-Id: I6b5262ccf903b69dbf3e0a5c937e38a0c9b2e886
Reviewed-on: https://chromium-review.googlesource.com/1244879Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594829}

According to manual, it must be either NULL or pointer to an
extension-specific structure. Also GCC barks on skipping fields in
initialisers (8 times as 8 fields follow skipped pNext):

../../gpu/vulkan/vulkan_swap_chain.cc:94:3: sorry, unimplemented: non-trivial designated initializers not supported

Change-Id: I744b9dc84c24b927ec1172f4044f9ca7fbf64029
Reviewed-on: https://chromium-review.googlesource.com/1226600Reviewed-by: Peng Huang <penghuang@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594828}

This is a source of webkit_layout_test flakiness on Windows.

Bug: 889608
Change-Id: Ib31cd068620d0c1917aaa85ce2ec7038ccd4236e
Reviewed-on: https://chromium-review.googlesource.com/1249385
Commit-Queue: Erik Chen <erikchen@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594827}

This CL introduces a few improvements to HttpCredentialCleaner:
(1) A fix in removing the protocol from signon_realm,
(2) refactoring the unittest to use parameters,
(3) minor style fixes.

More details about (1):
HttpCredentialCleaner removes the protocol (HTTP or HTTPS) form
the signon_realm in order to compare the signon_realm of HTTP
credentials with the signon_realm of HTTPS credentials. Until now,
a GURL was created from the signon_realm of the form and then the
protocol was extracted from that GURL, resulting the signon_realm
excluding protocol. This can cause problems when the auth realm contains
characters that are forbidden in an url. This will lead in creating an
invalid url, and the resulting signon_realm with protocol exluded will
be an empty string.
This CL will avoid conversion from the signon_realm string to the GURL
and use other way to remove the protocol from the signon_realm.

More details about (2):
Unitests for this class were changed from one single test into a
bunch of parametrised tests in order to make debug easier in case
of failing test in the future.

Bug: 871140
Change-Id: Ic606d250f50806ae3a3fa07a480fcb01f5551c97
Reviewed-on: https://chromium-review.googlesource.com/1249104
Commit-Queue: Narcis Gemene <gemene@google.com>
Reviewed-by: Vaclav Brozek <vabr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594826}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/74a2dc070e4e..b15eae0a955c


Created with:
  gclient setdep -r src-internal@b15eae0a955c

The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll

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.


TBR=mmoss@chromium.org

Change-Id: I0df584d7e8c24ef676c34f8573b2bb6ff688eb65
Reviewed-on: https://chromium-review.googlesource.com/1249635Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#594825}

Partial revert of https://codereview.chromium.org/1918183003
PointerWatcher is no longer needed with Ash hosting the Window Service.

Bug: 872450
Test: No regressions with clicks inside/outside system tray bubbles.
Change-Id: I987ee0aab77cd2c0efcd1106c7c30e0663349654
Reviewed-on: https://chromium-review.googlesource.com/1249902Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594824}

This CL renames the HostBrowserLauncherParams getter methods to have the
HostBrowserLauncherParams#getStartUrl() format instead of the
HostBrowserLauncherParams#startUrl() format.

BUG=None

Change-Id: I29f76346bfe80198711488a047e41833655595cf
Reviewed-on: https://chromium-review.googlesource.com/1244363
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Reviewed-by: Xi Han <hanxi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594823}

Splitting this off from the implementation so we can submit strings
earlier.

Bug: 879548
Change-Id: I180391d203f1fcd98a04f42a89373eb42b33341f
Reviewed-on: https://chromium-review.googlesource.com/1246821
Commit-Queue: Martin Kreichgauer <martinkr@google.com>
Reviewed-by: Christian Dullweber <dullweber@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594822}

https://skia.googlesource.com/skia.git/+log/227d4e10276c..dbdd151b1cb9


git log 227d4e10276c..dbdd151b1cb9 --date=short --no-merges --format='%ad %ae %s'
2018-09-27 benjaminwagner@google.com Revert "bump NDK packages to r18"
2018-09-27 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader 4241ad731a8a..40a6005e7a14 (3 commits)
2018-09-27 brianosman@google.com Remove redundant SkImage virtuals
2018-09-27 brianosman@google.com Revert "Reland "Implement an explicit binary search-based analytic gradient colorizer""
2018-09-27 bsalomon@google.com Revert "Change how GrTextureOp computes outset vertices."
2018-09-27 mtklein@google.com only build stats bar chart when it'll be printed
2018-09-27 fmalita@chromium.org [skottie] External font loader tweaks
2018-09-27 michaelludwig@google.com Reland "Implement an explicit binary search-based analytic gradient colorizer"
2018-09-27 mtklein@google.com bump NDK packages to r18
2018-09-27 mtklein@google.com add test that setLastPt() invalidates path bounds
2018-09-27 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/angle2 115e8a2625f5..122919bddd98 (1 commits)
2018-09-27 mtklein@google.com invalidate pathref bounds when we attach an editor
2018-09-27 mtklein@google.com update SkPathRef bounds validation
2018-09-27 ethannicholas@google.com fixed SPIR-V interface variable declarations
2018-09-27 bsalomon@google.com Change how GrTextureOp computes outset vertices.


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

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

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-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel

BUG=chromium:796479,chromium:729727,chromium:696603,chromium:543625,chromium:414254,chromium:796479,chromium:729727,chromium:696603,chromium:543625,chromium:414254
TBR=bsalomon@chromium.org

Change-Id: I01c18efde9921a36f3185d80d3950f46ff3e73ce
Reviewed-on: https://chromium-review.googlesource.com/1249507Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#594821}

[about-omnibox] Performance refactoring of omnibox.js: split refresh method, extract inlined dom elements, and improved html output clearing.

1. Split `refresh` into `refreshAllResults` and `refreshNewResult` for performance reasons as explained in the comments (tldr, refreshing entire output is unnecessary when we only need to add to the output).
2. Extract variables for inlined expressions to retrieve document elements.
3. Use `Element.removeChild` instead of `Element.innerHTML = ` to clear output

Change-Id: Ia7085d97537c5f445c950ecb50f35e5880b6124a
Reviewed-on: https://chromium-review.googlesource.com/1246295
Commit-Queue: manuk hovanesian <manukh@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594820}

The text of the accept button on the welcome page
is changed from "Sign in" to "Turn on sync...".

Screenshot:
https://drive.google.com/file/d/1dFMRqbKazetzouP8MzScMG_lTk5vrd2G/view?usp=sharing

Bug: 889949
Change-Id: I5053b940af365da5a59d434227fa54468919187e
Reviewed-on: https://chromium-review.googlesource.com/1249272Reviewed-by: Scott Chen <scottchen@chromium.org>
Commit-Queue: Thomas Tangl <tangltom@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594819}

Change-Id: Ie364d434a3b4976ba74251c453e117d1e65c3d98
Reviewed-on: https://chromium-review.googlesource.com/1246864Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594818}

https://chromium.googlesource.com/angle/angle.git/+log/122919bddd98..beb0c946de6d


git log 122919bddd98..beb0c946de6d --date=short --no-merges --format='%ad %ae %s'
2018-09-27 geofflang@chromium.org Vulkan: Make sure the default uniform info arrays match indices.


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

The AutoRoll server is located here: https://autoroll.skia.org/r/angle-chromium-autoroll

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

Change-Id: I8f18ddc41d556ba4f90e3cd7a4da02ed79445934
Reviewed-on: https://chromium-review.googlesource.com/1249508Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#594817}

We can not replace it with our regular void (a = ...) here, so let's
just ignore it.

R=lushnikov@chromium.org

Bug: chromium:805249
Change-Id: I859ca107a15a0284a7c6a2ed0e32fe0c11d4734f
Reviewed-on: https://chromium-review.googlesource.com/1249539
Commit-Queue: Andrey Lushnikov <lushnikov@chromium.org>
Reviewed-by: Andrey Lushnikov <lushnikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594816}

ChromeVox's expectations with regard to tab switch recovery have changed. Namely:
- selection events appear to be fired unexpectedly on tabs at various points
- ChromeVox range is no longer over the root web area when a hit test result comes back even when we do want to recover

This change adjusts accordingly to TOT and adds tests for both tab switching and refresh recovery to ensure we don't regress again.

Bug: 887185
Change-Id: I3081830457fb62c14456368a819b00765659a824
Reviewed-on: https://chromium-review.googlesource.com/1246366Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594815}

Bug: 872438
Change-Id: I72790fccc75bc4ac0bdf457cbb960a53019ab974
Reviewed-on: https://chromium-review.googlesource.com/1182614Reviewed-by: Erik Luo <luoe@chromium.org>
Commit-Queue: Joel Einbinder <einbinder@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594814}