GitLab

This is a reland of 04b716f7

Original change's description:
> ChromeOS OOBE: Add Welcome screen animations.
> 
> This Cl replaces static images with animations.
> 
> Bug: 852038
> Change-Id: I8185420aed0ed23c080ac0bc7a2270d3ac4c5b7b
> Reviewed-on: https://chromium-review.googlesource.com/1166590
> Commit-Queue: Alexander Alekseev <alemate@chromium.org>
> Reviewed-by: Wenzhao (Colin) Zang <wzang@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#581735}

Bug: 852038
Change-Id: I50659b137bc2e4c1facb7a3b3b734e1a1d3a6500
Reviewed-on: https://chromium-review.googlesource.com/1168328Reviewed-by: Wenzhao (Colin) Zang <wzang@chromium.org>
Commit-Queue: Alexander Alekseev <alemate@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581970}

Bug: 872052
Test: SplitViewTabDraggingTest.ShowNewWindowItemWhenDragStarts
Change-Id: Ib7a563d350fb5d789495518b414f7a319bc9063b
Reviewed-on: https://chromium-review.googlesource.com/1168592
Commit-Queue: Min Chen <minch@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581969}

Shipped in M64, this feature allows developers to selectively enable
and disable use of autoplay through the feature policy HTTP header
or the <iframe> "allow" attribute.

https://chromium-review.googlesource.com/831520
https://www.chromestatus.com/features/5100524789563392

BUG=788390

Change-Id: I0f4346bc75dc922c8004f0008921d68a5a3beede
Reviewed-on: https://chromium-review.googlesource.com/1166614
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Reviewed-by: Becca Hughes <beccahughes@chromium.org>
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581968}

This is used to ensure that ExternalBeginFrameSources have a unique
|source_id| after the GPU process is restarted.

Bug: 871755
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel
Change-Id: Ic5d6066fa2bcdee3c796f9f56967ffcd51e230f1
Reviewed-on: https://chromium-review.googlesource.com/1165888Reviewed-by: ccameron <ccameron@chromium.org>
Reviewed-by: Saman Sami <samans@chromium.org>
Commit-Queue: kylechar <kylechar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581967}

Bug: none
Change-Id: Icf7f6223f2f3e9c652d5d3dcacf7f652869490a5
Reviewed-on: https://chromium-review.googlesource.com/1169767
Commit-Queue: Peter Kasting <pkasting@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581966}

The full list of isolated origins might include sensitive info in
upcoming field trials, so show the number of isolated origins instead
of actual list.

Bug: 872375
Change-Id: I944919cc9ce2afa953bbca77a489c9df62105ab8
Reviewed-on: https://chromium-review.googlesource.com/1167962Reviewed-by: Nasko Oskov <nasko@chromium.org>
Commit-Queue: Alex Moshchuk <alexmos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581965}

When AddOrReplaceEntry() posts a UpdateDownloadDB task, RemoveEntry()
could be called before the posted task to get a executed.
This will cause the DCHECK to fail.

BUG=872279

Change-Id: I90c19a66814b050ef4cded72ee35380790d16d4c
Reviewed-on: https://chromium-review.googlesource.com/1169979Reviewed-by: Xing Liu <xingliu@chromium.org>
Commit-Queue: Min Qin <qinmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581964}

Also move the function and its helpers to ModuleCache.

BUG=803276
TBR=dcheng@chromium.org
TBR=wittman@chromium.org

Reviewed-on: https://chromium-review.googlesource.com/1166206Reviewed-by: Mike Wittman <wittman@chromium.org>
Change-Id: I28ad62df7a3f2f597f1a4f36069c51b541e7dc29
Reviewed-on: https://chromium-review.googlesource.com/1169533Reviewed-by: Alexei Filippov <alph@chromium.org>
Commit-Queue: Alexei Filippov <alph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581963}

Bug: b/112431554
Test: Manual
Change-Id: I10e52dad59b2989fe9ba223b3c8cf130143ea9b8
Reviewed-on: https://chromium-review.googlesource.com/1170031
Commit-Queue: Muyuan Li <muyuanli@chromium.org>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581962}

Targets like ui/file_manager/file_manager/foreground/js:closure_compile
were causing js_compile.py to spend upwards of one minute of CPU time
in Python before even invoking the closure compiler.

Caching dependency subtrees takes the python CPU time down to about 50
milliseconds. That is, a 1000x performance boost.

Note the _set_ of arguments passed to closure is identical. However, the
order can change slightly without violating dependencies specified. This
shuffling exposed a couple of errors due to underspecified dependencies.
(Fix them):

ui/file_manager/file_manager/background/js/test_util_base.js:589:
  ERROR - Property args never defined on request

chrome/browser/resources/settings/site_settings/site_data_entry.js:15:
  ERROR - Variable referenced before declaration: I18nBehavior

TBR=hcarmona@chromium.org

Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: I10c27bb76b404bb40828dfd54f99be059adf0fdb
Reviewed-on: https://chromium-review.googlesource.com/1166775
Commit-Queue: Trent Apted <tapted@chromium.org>
Reviewed-by: Naoki Fukino <fukino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581961}

In BridgedContentView, change most calls that refer to the views::View
hostedView_ to be routed through the BridgedNativeWidgetHost interface.

Leave keyboard events, text input, and a11y unchanged for now.

Add a BridgedNativeWidgetHostImpl::SetRootLayer method which now calls
through to BridgedNativeWidget::SetRootLayer. Once the remaining uses
of hostedView_ are removed, the BridgedNativeWidget::SetRootLayer method
will be removed.

Bug: 859152
Change-Id: I2a010b3149357af4f9aeaec0088eb9fcde53db13
Reviewed-on: https://chromium-review.googlesource.com/1168459
Commit-Queue: ccameron <ccameron@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581960}

This reverts commit f6c63d90d7b8a6f689b135fefc181a8e539debf9.

Reason for revert: Commit queue is working now.

Original change's description:
> Revert "Changed STDMETHODIMP to IFACEMETHODIMP and long to LONG where appropriate"
> 
> This reverts commit 641067d28a56deb5b2432a3f603eae029f461170.
> 
> Reason for revert: Due to Gerrit outage http://crbug.com/872722, we are reverting this CL. Please, re-land it after all clear is given. If you have questions, please ask on the bug. Sorry for the inconvenience.
> 
> Original change's description:
> > Changed STDMETHODIMP to IFACEMETHODIMP and long to LONG where appropriate
> > 
> > 1. STDMETHODIMP is defined as
> > HRESULT STDCALL
> > but the new macro IFACEMETHODIMP is defined as having an additional override modifier which
> > checks that the method we are defining or declaring is indeed an override of a method in a superclass.
> > 2. long is the same as LONG on Windows, but in order to avoid any confusion or any linter errors, I changed all uses to the capitalized version LONG.
> > 
> > Advantages:
> > A) This sends the message to developers that this is not the standard long type. It is actually an int.
> > B) It is the same as the type used in most of the MS documentation.
> > TBR=dtseng@chromium.org, dmazzoni@chromium.org, aleventhal@chromium.org
> > Change-Id: Ib73dc3b362c0297f7a9038f289710d66fa5c698c
> > Reviewed-on: https://chromium-review.googlesource.com/1169305
> > Reviewed-by: Nektarios Paisios <nektar@chromium.org>
> 
> TBR=dmazzoni@chromium.org,dtseng@chromium.org,nektar@chromium.org,aleventhal@chromium.org
> 
> Change-Id: Ia0655ece63c2dea8819130c0041e3cc4fd24a345
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Reviewed-on: https://chromium-review.googlesource.com/1169848
> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>

TBR=dmazzoni@chromium.org,dtseng@chromium.org,nektar@chromium.org,tandrii@chromium.org,aleventhal@chromium.org

Change-Id: I997abd90e3da0f4424d4e61853fdbb17cbae0cd2
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/1169883Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Commit-Queue: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581959}

WebGL conformance suppressions:
  conformance2/textures/misc/tex-mipmap-levels.html
  conformance2/textures/misc/tex-base-level-bug.html

Pixel test suppressions:
  Pixel_CSSFilterEffects
  Pixel_WebGLSadCanvas

Tbr: ynovikov@chromium.org
Bug: 870856, 872423
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
Change-Id: I1420fe20b7a64bb40f3ba0209fd9bb08b3213b14
Reviewed-on: https://chromium-review.googlesource.com/1168470Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581958}

When Chrome is killed in the background while VR mode is on, we can't
turn VR mode off (the platform doesn't respect VR mode changes for
backgrounded apps).

We also can't check whether VR mode is currently on on Android N, so
instead this CL records whether we were in VR mode when killed using
saved instance state, and turns VR mode off on startup when restoring.

Test/Repro steps:
1. Turn on "Don't keep activities" in developer settings
2. Launch Chrome in VR
3. Press the Daydream controller Home button
4. Exit VR
5. Use task switcher to return to Chrome.

> Chrome should resume without VR mode on (the display will flicker
if it's on)

Bug: 854740
Change-Id: I4fc8e9c076a8cb31ca2bdb74be1124bec3826193
Reviewed-on: https://chromium-review.googlesource.com/1167116
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581957}

This reverts commit 4af14ca3c99bd7edbf100e05db93564b7107cc62.

Reason for revert: relanding once the outage is over.

Original change's description:
> Revert "Deflake inspector-protocol/input/dispatchKeyEvent-focus.js"
> 
> This reverts commit 27378e0364b705643275c861f4ba64b70572dff1.
> 
> Reason for revert: Due to Gerrit outage http://crbug.com/872722, we are reverting this CL. Please, re-land it after all clear is given. If you have questions, please ask on the bug. Sorry for the inconvenience.
> 
> Original change's description:
> > Deflake inspector-protocol/input/dispatchKeyEvent-focus.js
> > 
> > The keystrokes injected via Input.dispatchKeyEvent through the browser are
> > racing against Runtime.evaluate in the renderer, so we need to wait for
> > the async completion of the last dispatchKeyEvent before validating the
> > tests results with evaluate.
> > 
> > Bug: 872081
> > Change-Id: Ic5ef41feba6a877c76c05de2e09e019a826756a1
> > Reviewed-on: https://chromium-review.googlesource.com/1168200
> > Reviewed-by: Andrey Lushnikov <lushnikov@chromium.org>
> 
> TBR=dgozman@chromium.org,lushnikov@chromium.org,caseq@chromium.org
> 
> Change-Id: I6f7e8e41eab2c756875103cae24576c37784baf3
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 872081
> Reviewed-on: https://chromium-review.googlesource.com/1169789
> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>

TBR=dgozman@chromium.org,lushnikov@chromium.org,caseq@chromium.org,tandrii@chromium.org

Change-Id: Ia8e5d3e56d923c31451474969afad7450e8e734d
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 872081
Reviewed-on: https://chromium-review.googlesource.com/1170007Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Commit-Queue: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581956}

This will help debug the linked bug, by comparing S13nServiceWorker on
vs off.

Bug: 866335
Change-Id: Idd1d027971cb9fd5122cda4f1cf383b55119fa83
Reviewed-on: https://chromium-review.googlesource.com/1168952Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Commit-Queue: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581955}

DecoderSelector provides an InitCB that destroys the VideoDecoder
immeidately when initialization fails. This means that |this| is
invalidated immedately upon calling |init_cb_| in MojoVideoDecoder.

This CL adds a WeakPtr-based test for |this| destruction to the
potentially problematic callbacks in MojoVideoDecoder::Stop().

Bug: 839881
Change-Id: I9b1302ad3007a834c95ed1d3845e24b0d07158f8
Reviewed-on: https://chromium-review.googlesource.com/1169907Reviewed-by: Frank Liberato <liberato@chromium.org>
Commit-Queue: Dan Sanders <sandersd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581954}

This CL moves the picker UI triggered from extensions into
DesktopMediaPickerFactoryImpl which lives under
/chrome/browser/media. We are planning to use this common
implementation to trigger the same picker UI for getDisplayMedia().

Bug: 326740
Change-Id: Idb8b9d094ce55ecc8281c3db1f1acb0f5e3a24f1
Reviewed-on: https://chromium-review.googlesource.com/1169594
Commit-Queue: Emircan Uysaler <emircan@chromium.org>
Reviewed-by: Weiyong Yao <braveyao@chromium.org>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581953}

While migrating some classes from URLFetcher to SimpleURLLoader,
it is useful to have the size of the resulting decompressed body.

In case of DownloadToString* calls, this is straightfoward:
the length to the string is the size.
However, in the case of DownloadTo{Temp}File calls, where only the
resulting file path is passed to the completion callback, having
an API to get the decompressed body size is useful. It also avoids
sync calls to access the file data.

This CL adds a SimpleURLLoader::GetContentSize API that provides such
value. When used with SimpleURLLloader::SetAllowPartialResults(true),
the API returns the total decompressed body size even in the case of
errors.

BUG=773295,844972

Cq-Include-Trybots: luci.chromium.try:linux_mojo
Change-Id: Ia8cdb3326b5d5c74276e384f966a7e98f61a8c46
Reviewed-on: https://chromium-review.googlesource.com/1167683Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581952}

This differs from the first version in that SetFocus(null) now returns
true. As you suggested in the last patch, returning false caused the
client to attempt to revert, which lead to some oddities. So, it seems
safer to return true.

views_mus_unittests no longer fails with this version, and
https://chromium-review.googlesource.com/c/chromium/src/+/1169525 fixs the
issue with the browser_test NavigatingExtensionPopupBrowserTest.Webpage.

Here's my comment as to why this is ignored:

  // The client is asking to remove focus from a window. This is typically a
  // side effect of the window becoming, or about to become, an unfocusable
  // Window (for example, the Window is hiding). Windows becoming unfocusable is
  // handled locally. Assume the request is for such a scenario and return
  // true. Returning false means the client will attempt to revert to the
  // previously focused window, which may cause unexpected activation changes.
  //
  // To process null requests conflicts with top-level activation changes. For
  // example, the typical sequence when a window is hidden is to first remove
  // focus, and then hide the window. FocusController keys off window hiding to
  // move activation. If this code were to set focus to null, FocusController
  // would not see the window hiding (because the active window was set to null)
  // and not automatically activate the next window.
  //
  // Another possibility for this code is to handle null as a signal to move
  // focus to the active window (if there is one). I'm going with the simpler
  // approach for now.

BUG=867654, 871652
TEST=covered by tests

Change-Id: Iff2ddb31c2b99b977bca8e56fb653b6ce4eb6813
Reviewed-on: https://chromium-review.googlesource.com/1165692
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581951}

Should be a good number of teensy layout test diffs.

Change-Id: I3dc74252fab7ec8ee4aa38d95ba1f60ed3e96b01
Reviewed-on: https://chromium-review.googlesource.com/1169313
Commit-Queue: Mike Klein <mtklein@chromium.org>
Reviewed-by: Florin Malita <fmalita@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581950}

Bug: internal b/112331554
Test: manual
Change-Id: Ib7670d56a1d8444ac895cae7117365ccda0ef9e4
Reviewed-on: https://chromium-review.googlesource.com/1168507Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Commit-Queue: James West <jameswest@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581949}

This CL removes some obselete sizing-* CSS rules that were
inadvertently causing a scrollbar to appear in the overflow menu at
certain zoom levels.

Bug: 851492
Change-Id: Ibafa0b74312d3f18b5ca5c3ee1050f1710c1e810
Reviewed-on: https://chromium-review.googlesource.com/1168394Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Commit-Queue: Tommy Steimel <steimel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581948}

This is needed to make content_browsertests happy under mash.

Bug: 866942
Change-Id: I21885e4328706f83bb57805abe4cff581551120a
Reviewed-on: https://chromium-review.googlesource.com/1168143Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581947}

TabGridMediator relies on VisibleURL to determine if the title of a
tab should be hidden. During session restore, the restore_session.html
item is briefly the only visible item in the web view until the other
entries are restored, and it has chrome://newtab as the virtual URL.
This incorrectly causes the CreateItem() in TabGridMediator to set
|hidesTitle| to true for the grid item.

Previously visible item title was cached in WebStateImpl for a similar
reason (http://crbug.com/819606). This change combines the two use cases.


Bug: 869351
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I5391eda466ad9de26087d2d8a1e2a97a7a83f27a
Reviewed-on: https://chromium-review.googlesource.com/1157866
Commit-Queue: Danyao Wang <danyao@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581946}

ChromeDriver built in Chrome release branches now embeds Chrome version
number (e.g., 69.0.3497.23) instead of ChromeDriver version (e.g., 2.41).

Bug: chromedriver:2080
Change-Id: I8727b0c42ad3d59a0833345a596a4bdbce83b282
Reviewed-on: https://chromium-review.googlesource.com/1166229
Commit-Queue: John Chen <johnchen@chromium.org>
Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Reviewed-by: Jonathon Kereliuk <kereliuk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581945}

Using wpt-import in Chromium 78fe025a.
With Chromium commits locally applied on WPT:
7dad0f17 "Added new Sec-Metadata Web Platform Tests."


Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/22578

Note to sheriffs: This CL imports external tests and adds
expectations for those tests; if this CL is large and causes
a few new failures, please fix the failures by adding new
lines to TestExpectations rather than reverting. See:
https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md

Directory owners for changes in this CL:
jsbell@chromium.org:
  external/wpt/resources
mkwst@chromium.org:
  external/wpt/cookies
mkwst@chromium.org, andypaicu@chromium.org:
  external/wpt/content-security-policy

NOAUTOREVERT=true
TBR=kereliuk

No-Export: true
Change-Id: Ic353a494c2b6fc7d49be2aa32313b8e04b7014d8
Reviewed-on: https://chromium-review.googlesource.com/1169943
Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Reviewed-by: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581944}

Bug: 516866
Change-Id: I2a460de83529e88058054d2407da6a6d8f6e9357
Reviewed-on: https://chromium-review.googlesource.com/1169053
Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org>
Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581943}

This uses the strategy suggested in crbug.com/842445#c10 to map the
renderer request IDs to global request IDs so PageLoadMetrics can
associate ResourceLoadComplete events with the correct PageLoadTracker.

The LoadingMetricsFailed test is still failing because
DidFinishNavigation is called before ResourceLoadComplete, which means
the PageLoadTracker has already been destroyed before we can track the
failed request. From the discussion in crbug.com/842445, this doesn't
seem like a big deal.

Bug: 842445, 816684
Cq-Include-Trybots: luci.chromium.try:linux_mojo
Change-Id: Ifb1c0d689840f626c0612ddab26a10d8ea9eb078
Reviewed-on: https://chromium-review.googlesource.com/1155800
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Reviewed-by: Bryan McQuade <bmcquade@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581942}

Also update a TODO.

Bug: 809249
Change-Id: I80bb4cc046c765de6b1bc5e519cb22628af6bf9e
Reviewed-on: https://chromium-review.googlesource.com/1169875Reviewed-by: Takumi Fujimoto <takumif@chromium.org>
Commit-Queue: Derek Cheng <imcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581941}

https://skia.googlesource.com/skia.git/+log/8af4c40014e3..644d8e7175ae


git log 8af4c40014e3..644d8e7175ae --date=short --no-merges --format='%ad %ae %s'
2018-08-09 kjlubick@google.com [PathKit] Add PathOps Op and Simplify tests imported from the C++ tests.
2018-08-09 brianosman@google.com Remove old sRGB config support from backend render target tool utilities
2018-08-09 bungeman@google.com Move Views into Sample and Viewer.
2018-08-09 benjaminwagner@google.com Add jobs for GTX1050 eGPU.
2018-08-09 timliang@google.com Revert "implemented GrMtlSampler for metal gpu backend"
2018-08-09 brianosman@google.com Stop treating 2.2 gamma as sRGB
2018-08-09 caryclark@skia.org make some textblob builders private for now
2018-08-09 fmalita@chromium.org [skottie] Optimize opacity layerization
2018-08-09 herb@google.com Remove use of RunPaint from regenerateGlyphRunList
2018-08-09 mtklein@google.com clean up SK_LEGACY_COLORSPACE_XFORMER_IMPL
2018-08-09 brianosman@google.com Remove CachedFormat remnants
2018-08-09 kjlubick@google.com [Pathkit] Add recipe for running JS tests using Docker
2018-08-09 brianosman@google.com Remove picture_utils
2018-08-09 timliang@google.com implemented GrMtlSampler for metal gpu backend
2018-08-09 brianosman@google.com Cleanup and simplify some skiaserve and utility code
2018-08-09 brianosman@google.com Remove dead code from Benchmark


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

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

Change-Id: Ib16bfce3717cbfc71ab37fdbb68ae3a80a956246
Reviewed-on: https://chromium-review.googlesource.com/1169722
Commit-Queue: Mike Klein <mtklein@chromium.org>
Reviewed-by: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#581940}

We are preloading the favicon cache for bookmarks created by this
onboarding flow. The icons that we preload are overdidden when the
user navigates to the site.

Bug: 832938
Change-Id: I3866ca4fdbc1044f7492f85f7f52c6d119a2a227
Reviewed-on: https://chromium-review.googlesource.com/1168397Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Commit-Queue: Hector Carmona <hcarmona@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581939}

Observe RenderFrameCreated, so that when a subframe is created, we
can add an InputEventObserver to that frame as well as the main frame.

Bug: 869062
Change-Id: I24cd1f20f46375ec37963ecc72e69f255e756d87
Reviewed-on: https://chromium-review.googlesource.com/1163824
Commit-Queue: Daniel Rubery <drubery@chromium.org>
Reviewed-by: Vadym Doroshenko <dvadym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581938}

It is a valid use case for a daemon to have multiple ObjectProxies of
different services with the exact same object path and interface name.
Currently, this may cause log pollution of "rejecting a message from a
wrong sender" because one ObjectProxy receives signals intended for
another ObjectProxy. Since it's actually a valid case and not a bug, it
shouldn't be logged as error but it may still be logged with VLOG.

Currently this is discovered in Bluetooth daemon (btdispatch) because it
listens to both BlueZ's and Newblue's objects which have identical
object paths and interfaces.

Bug: 866704
Change-Id: I25b6437ec6081e244a47c635c0adedf281530967
Reviewed-on: https://chromium-review.googlesource.com/1164474Reviewed-by: Ryo Hashimoto <hashimoto@chromium.org>
Commit-Queue: Sonny Sasaka <sonnysasaka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581937}

Minor touch radius was incorrectly scaled using major scale factor.

BUG=None

Change-Id: Ib14976a85b5457c1ed52de79e3008b2a425eea7a
Reviewed-on: https://chromium-review.googlesource.com/1168504Reviewed-by: Michael Spang <spang@chromium.org>
Commit-Queue: Sean O'Brien <seobrien@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581936}

Bug: crashpad:30
Change-Id: Iff2d508ae265882e6187cdc418a8074b7b6203fd
Reviewed-on: https://chromium-review.googlesource.com/1118910
Commit-Queue: Joshua Peraza <jperaza@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Peter Wen <wnwen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581935}

UX and PM think it's better to say "This tab is sharing your screen.".
Also fixed a typo in desc.

Bug:859981

TBR=rockot@chromium.org

Change-Id: I503ab2ce47190ed1069e99a58eaa01c001558a8e
Reviewed-on: https://chromium-review.googlesource.com/1169540Reviewed-by: Weiyong Yao <braveyao@chromium.org>
Commit-Queue: Weiyong Yao <braveyao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581934}

Adds support for setting and adjusting volume.  Supported queries:

"set volume to 20%"
"set volume to max"
"set volume to minimum"
"increase the volume"
"decrease the volume"
"increase the volume by 15%"

Also works with "step" values:
"set volume to 20"
"increase the volume by 20"

The backend treats these separately, but the client still treats them
as percentages.

Bug:b/111133529
Bug:b/78189672

Change-Id: I1e02ca2f15c46dc847206dfef93ee340f901f7e0
Reviewed-on: https://chromium-review.googlesource.com/1168511Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Commit-Queue: Ryan Cui <rcui@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581933}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/5570c88a3dce..aba1649cfb98


git log 5570c88a3dce..aba1649cfb98 --date=short --no-merges --format='%ad %ae %s'
2018-08-09 lannm@chromium.org Remove git retry constants
2018-08-09 tikuta@chromium.org Use gomacc for host compiler in simple chrome build
2018-08-09 lannm@chromium.org Create chromite.lib.repo_util and migrate autotest_evaluator to it


Created with:
  gclient setdep -r src/third_party/chromite@aba1649cfb98

The AutoRoll server is located here: https://chromite-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.


TBR=chrome-os-gardeners@chromium.org

Change-Id: Ie4fe2bd6346284734bfe9e9f64d19778df2d3157
Reviewed-on: https://chromium-review.googlesource.com/1168416Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#581932}

Replaced Stub with parent implementation stubs to make it easier
to add sounds; made the proxy explicit; renamed things for clarity.
Follow-up CL will remove accessibility_sound_delegate.h.

Bug: internal b/73383411
Test: manual
Change-Id: I95d6619f373024f66aed6204ee667585c7db0f76
Reviewed-on: https://chromium-review.googlesource.com/1166029Reviewed-by: Alex Sakhartchouk <alexst@chromium.org>
Commit-Queue: Kevin Schoedel <kpschoedel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581931}