- 16 Sep, 2020 40 commits
-
-
Leonard Grey authored
No actual WebUI code added yet; this is just the layer that sets everything up and handles communication. Bug: 1014639 Change-Id: Ie121d6c02d4d92b84eb24d3412291f93b40de09f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2380670Reviewed-by:
dpapad <dpapad@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Leonard Grey <lgrey@chromium.org> Cr-Commit-Position: refs/heads/master@{#807610}
-
Christopher Cameron authored
Allow GpuMemoryBuffer handles to be provided even when they weren't requested. There is precedent for this already, for texture mailboxes. This becomes an "upgrade" of a shared memory buffer. Bug: 1125879 Change-Id: I2abdaf0d0331899d3463c0f9cb8afc2519cbeed2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2408880Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Commit-Queue: ccameron <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#807609}
-
zhaoyangli authored
This change makes DeviceTestRunner also run target as XCTest by checking xctest arg. Before this change, DeviceTestRunner uses solely the existence of ".xctest" to determine if the target should run as XCTest. This can cause trouble when targets build .xctest in but do not wish to run as it. The goal is to only use xctest arg to determine if it should run as XCTest. These follow up CLs are needed to achieve the goal: - Change device XCTest unit test configs in multiple repos. - Remove the logic of using xctest_path to determine if run with xctest, add a check to ensure xctest path is there when xctest is true. Bug: 1085603 Change-Id: I07e5f21467791295e8ecc5f6246e58fd696d5e4d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2412970 Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org> Reviewed-by:
Justin Cohen <justincohen@chromium.org> Cr-Commit-Position: refs/heads/master@{#807608}
-
David Gilhooley authored
Fuchsia threads will no longer be killable. Replace the death tests that kill threads with code that causes the thread to exit itself. Change-Id: I551dbbe454b4ca0b803f73c8295c55e9888f1ad9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413533 Commit-Queue: David Gilhooley <dgilhooley@google.com> Reviewed-by:
Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#807607}
-
Tom Anderson authored
BUG=1066670 R=sky Change-Id: I143ec40265e7b9787c948be67f3695fce79634d7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2412472 Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#807606}
-
David Bertoni authored
These tests were disabled for flakiness many years ago. They passed 3000 iterations on the bots without failures. Bug: 68287, 128412 Change-Id: I4196dbd345aebbacbe3d378fd76a21990234b930 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404406Reviewed-by:
Kelvin Jiang <kelvinjiang@chromium.org> Commit-Queue: David Bertoni <dbertoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#807605}
-
Matthias Körber authored
Currently the AutofillProfile::Compare() method ignores the new address tokens since those are not actively used by the profile. This results in sync updates containing the enhanced address tokens not being propagated to the local store. With this CL the new address tokens are checked by AutofillProfile::Compare(). For mergeabibility, the changes are entirely guarded by a finch flag. Change-Id: Id1fac25642d32bfca4c484aa54655c57a3e851fe Bug: 1129006 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414272 Auto-Submit: Matthias Körber <koerber@google.com> Commit-Queue: Christoph Schwering <schwering@google.com> Reviewed-by:
Christoph Schwering <schwering@google.com> Cr-Commit-Position: refs/heads/master@{#807604}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/1a6e1152b10b..cb190dce089b 2020-09-16 sadrul@chromium.org [rendering benchmark] Remove a noisy metric. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/catapult-autoroll Please CC oysteine@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:chromeos-kevin-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:894287 Tbr: oysteine@google.com Change-Id: Iddc3d08b3eb5b116dab46d3fefec83e55c1b4329 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414547Reviewed-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@{#807603}
-
David Bertoni authored
This test was disabled a long time ago and it's no longer flaky on Mac. Bug: 70511 Change-Id: I3590a976477cdd094973582b50d1f1df08dcca12 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2410617Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Commit-Queue: David Bertoni <dbertoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#807602}
-
Danan S authored
Bug: 1128446 Change-Id: I6f6616186fd2cb4bf5e6e7a5c422b3b2f052967b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2411653 Commit-Queue: Dan S <danan@chromium.org> Reviewed-by:
Yilkal Abe <yilkal@chromium.org> Reviewed-by:
Michael Giuffrida <michaelpg@chromium.org> Cr-Commit-Position: refs/heads/master@{#807601}
-
David Bertoni authored
These tests are no longer flaky. Bug: 238705 Change-Id: I1e0b84122a2cc7d2581a9dff8007a5f31d7b00f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2411470Reviewed-by:
Kelvin Jiang <kelvinjiang@chromium.org> Commit-Queue: David Bertoni <dbertoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#807600}
-
John Williams authored
This change also moves generation of the notification ID to the notification item itself. Bug: 1107164, b/161612881 Change-Id: Ie043c8810878ff357027076205f45b7f194da43c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414311Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: John Williams <jrw@chromium.org> Cr-Commit-Position: refs/heads/master@{#807599}
-
Bryan Bernhart authored
Call to RequestAdapterAsync() left the properties struct uninitialized, which leads to failure should the GPU not support ALL extensions. This fix ensures the device properties struct is always initialized to zero. Change-Id: I013df8e4434485d6ef79161fea3c81ed86260437 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2411407Reviewed-by:
Khushal <khushalsagar@chromium.org> Reviewed-by:
Juanmi Huertas <juanmihd@chromium.org> Commit-Queue: Bryan Bernhart <bryan.bernhart@intel.com> Cr-Commit-Position: refs/heads/master@{#807598}
-
Arnaud Mandy authored
Origin Trial feedback was that webNFC is better without filtering. NDEFScanOptions now does not need to carry information like recordType or mediaType as we are not matching them against active watchers anymore. Spec changes: https://github.com/w3c/web-nfc/issues/560 https://github.com/w3c/web-nfc/pull/565 Bug: 520391 Change-Id: I642cff9e72745728f41ad74e803d971a3126ddad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401020Reviewed-by:
Reilly Grant <reillyg@chromium.org> Reviewed-by:
Rijubrata Bhaumik <rijubrata.bhaumik@intel.com> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Arnaud Mandy <arnaud.mandy@intel.com> Cr-Commit-Position: refs/heads/master@{#807597}
-
Matthew Crabill authored
This change adds a MissedDeadlineFrames UMA that tracks frames that miss the vsync deadline during scroll/animations. Bug: 1092938 Change-Id: I044985583193d94c90485f1308be5645d553af7f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2343642 Commit-Queue: Matthew Crabill <macrabil@microsoft.com> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Reviewed-by:
Xida Chen <xidachen@chromium.org> Reviewed-by:
David Bokan <bokan@chromium.org> Reviewed-by:
Behdad Bakhshinategh <behdadb@chromium.org> Reviewed-by:
Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#807596}
-
Robert Liao authored
Change-Id: Id5e17a6efcfe809f18efc0c0346e939e45dc5993 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414620 Commit-Queue: Robert Liao <robliao@chromium.org> Commit-Queue: Peter Kasting <pkasting@chromium.org> Auto-Submit: Robert Liao <robliao@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#807595}
-
Darwin Huang authored
render_process_id is a much more common name for this process identifier variable. Refactoring change only. No functional changes intended. Change-Id: Iefe4ce12ab1583031a031d1789ceafff4204b9d4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413018 Commit-Queue: Darwin Huang <huangdarwin@chromium.org> Auto-Submit: Darwin Huang <huangdarwin@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#807594}
-
Rohit Agarwal authored
This CL adds unit tests for LocationBarModel#getProfile and revert the changes in javatests/*/LocationBarModelTest before crrev/c/2409298 Bug: 1128073 Change-Id: Ib41b443bd9d40ec2559aaff972bda642d999dcda Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2410482 Commit-Queue: Rohit Agarwal <roagarwal@chromium.org> Reviewed-by:
Filip Gorski <fgorski@chromium.org> Reviewed-by:
Peter Conn <peconn@chromium.org> Cr-Commit-Position: refs/heads/master@{#807593}
-
Li Lin authored
Expose ShowWidget through ParentAccessController interface. Bug: 1123722 Test: Manual Test Change-Id: Id1ba3232dfeb54977647389e0c03b086b4f9dbc2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391500Reviewed-by:
James Cook <jamescook@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Reviewed-by:
Aga Wronska <agawronska@chromium.org> Commit-Queue: Li Lin <llin@chromium.org> Cr-Commit-Position: refs/heads/master@{#807592}
-
danakj authored
The code has moved, so update the includes. TBR=avi@chromium.org Bug: 1091083 Change-Id: Idabdf8500519fd08befb76911b494f3a62ed350f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2412367 Commit-Queue: danakj <danakj@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#807591}
-
Miguel Casas authored
crrev.com/c/2268540 and crrev.com/c/2268600 started changing the names of the flag sent from ChromeOS command line builder to Chrome, namely from: --force-disable-new-accelerated-video-decoder to: --platform-disallows-chromeos-direct-video-decoder Previous CLs essentially made both be set or not at the same time [1], and this CL continues that refactoring chain by making Chrome aware of the new name. The next CL will finally remove the "old" name. This should have happened earlier but somehow I got sidetracked... [1] https://source.chromium.org/chromiumos/chromiumos/codesearch/+/master:src/platform2/libchromeos-ui/chromeos/ui/chromium_command_builder.cc;l=534-537 Bug: b/159825227 Change-Id: I2a9a8527fc66c114ccad37197c5cfdad39e21f37 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398905Reviewed-by:
Andres Calderon Jaramillo <andrescj@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Dale Curtis <dalecurtis@chromium.org> Auto-Submit: Miguel Casas <mcasas@chromium.org> Cr-Commit-Position: refs/heads/master@{#807590}
-
Charlie Hu authored
This CL splits font-display tests into smaller individual tests. The split has following benefits: - Clear obstable for implementation of violation report deduplication - Make the tests stricter. Before the test can verify there are 4 violation reports generated, but cannot tell which 4 cases generate violation reports. Previously there was an attempt on isolating tests into subframes (https://chromium-review.googlesource.com/c/chromium/src/+/2227863), but failed due to flaky crash in network cache (crbug.com/1087277). Bug: 1087277 Change-Id: Ifad35b40d112956fb00fd680b329e539a8762ed9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2405916 Commit-Queue: Charlie Hu <chenleihu@google.com> Reviewed-by:
Jason Chase <chasej@chromium.org> Cr-Commit-Position: refs/heads/master@{#807589}
-
Joshua Pawlicki authored
This script will be uploaded along with the updater artifacts to the signing infrastructure, where it will be run to produce signed builds of the updater. It is also possible to run it locally, provided the developer has all the necessary dependencies. Bug: 926234 Change-Id: I75ff5989b7e1fe3732b5ec43709ff13bfa67029e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2393063 Commit-Queue: Joshua Pawlicki <waffles@chromium.org> Reviewed-by:
Greg Thompson <grt@chromium.org> Reviewed-by:
Sorin Jianu <sorin@chromium.org> Cr-Commit-Position: refs/heads/master@{#807588}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/b33e0b36a08c..fe878dedd5ad 2020-09-16 hidehiko@google.com Expand is_linux to is_linux || is_chromeos. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Please CC swiftshader-team+autoroll@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_msan_rel_ng;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:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: chromium:1110266 Tbr: swiftshader-team+autoroll@google.com Change-Id: I9cb19f5a8b2125f3ab39df66d4fb09f56ca1735c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414532Reviewed-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@{#807587}
-
Ken MacKay authored
Fix a bug where the default volumes were not loaded correctly. Also add more logging. Bug: internal b/167692705 Change-Id: I0e580422d3473f05ca9f4939407138f1e57aea3c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414833 Commit-Queue: Kenneth MacKay <kmackay@chromium.org> Commit-Queue: Yuchen Liu <yucliu@chromium.org> Auto-Submit: Kenneth MacKay <kmackay@chromium.org> Reviewed-by:
Yuchen Liu <yucliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#807586}
-
Mark Yacoub authored
Zombie connectors could be disconnected but holding to an encoder, taking a CRTC that should be unused (potentially due to bios enabling it on for the warning screen). As the CRTC is being initialized, all connectors connected to it should be disabled. This is a workaround for a bug on Hatch where Puff enables a connector in dev mode before Chrome even starts. The kernel maps the HW state at initial modeset (with a dangling connector attached to a CRTC). When an Atomic Modeset is performed, it fails to modeset as the CRTC is already attached to another dead connector. BUG=1067121. TEST=Puff should be work fine with atomic modeset. All displays should be enabled with no problem. Change-Id: I68f554a4450c9384bdd2762d043f6f254d2365be Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2350359 Commit-Queue: Mark Yacoub <markyacoub@google.com> Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Cr-Commit-Position: refs/heads/master@{#807585}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/dbd34449af20..c23676954838 2020-09-16 cwallez@chromium.org Fix CMake build on Mac If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/dawn-chromium-autoroll Please CC cwallez@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel Bug: None Tbr: cwallez@google.com Change-Id: I7d50a103acdce10435bc60fc2333520beba663f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414612Reviewed-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@{#807584}
-
Michael Bai authored
- Add a new parameter default_local_memory in InstantiatePersistentHistograms() - Set it true for WebView. - Plan to merge this patch to M86. Bug: 1090682 Change-Id: I218c9960c9cb72e184e36f78e97096a8f6691759 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2411706 Commit-Queue: Michael Bai <michaelbai@chromium.org> Reviewed-by:
Brian White <bcwhite@chromium.org> Cr-Commit-Position: refs/heads/master@{#807583}
-
Adlai Holler authored
This method is no longer called by anyone, and it's removed from Skia in https://review.skia.org/317281. This unblocks that. Change-Id: I84657335f992cd23799a0718dc3734b45abce93a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413532 Auto-Submit: Adlai Holler <adlai@google.com> Commit-Queue: Khushal <khushalsagar@chromium.org> Reviewed-by:
Khushal <khushalsagar@chromium.org> Cr-Commit-Position: refs/heads/master@{#807582}
-
Dana Fried authored
Previously, we were creating a separate, smaller font for two-digit counter numbers based on the default font. This CL does two things: - makes the double-digit font the STYLE_SECONDARY version of the primary font for the tab counter - changes the secondary font to Roboto Condensed on ChromeOS, as per design spec By moving the size and face adjustment into chrome_typography_provider, we bring all of the font face specifications in Top Chrome into the standard, unified location, avoiding having to have extraneous font specification code in WebUITabCounterButton. Change-Id: I187a658d6ec321c883391bb860270fb401687379 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404944Reviewed-by:
Caroline Rising <corising@chromium.org> Commit-Queue: Dana Fried <dfried@chromium.org> Cr-Commit-Position: refs/heads/master@{#807581}
-
Curt Clemens authored
The Nearby Share pod button will need to make calls against code in //chrome/browser, but it lives in //ash, which cannot depend on //chrome. This delegate will provide the functionality needed for the pod button. Bug: 154866703 Test: unit_tests Change-Id: Id0a04e56f48590e1770389ad2433fccedae105e9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2405640 Commit-Queue: Curt Clemens <cclem@google.com> Reviewed-by:
James Cook <jamescook@chromium.org> Reviewed-by:
James Vecore <vecore@google.com> Cr-Commit-Position: refs/heads/master@{#807580}
-
Justin DeWitt authored
This reverts commit dd9ec5b7. Reason for revert: This was a temporary change to get some data. Original change's description: > Disable Feedv2 build flag on canary > > Bug: 1119406 > Change-Id: Ib6e64db692a264036d48ca168f434cfe38f534b6 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2412549 > Commit-Queue: Dan H <harringtond@chromium.org> > Auto-Submit: Dan H <harringtond@chromium.org> > Reviewed-by: Justin DeWitt <dewittj@chromium.org> > Cr-Commit-Position: refs/heads/master@{#807154} TBR=dewittj@chromium.org,harringtond@chromium.org Change-Id: I991b9fe55068363b667e087caf10b4c66233de54 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1119406 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414554Reviewed-by:
Justin DeWitt <dewittj@chromium.org> Commit-Queue: Justin DeWitt <dewittj@chromium.org> Cr-Commit-Position: refs/heads/master@{#807579}
-
Eric Roman authored
This is strictly a re-factor, however a follow-up CL uses the parameter for access the estimated transport RTT. Bug: 1123197 Change-Id: I0e697d59c87e9397f35f41222fb5399950c1ca41 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2382956Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Eric Roman <eroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#807578}
-
Lukasz Anforowicz authored
NonNetworkURLLoaderFactoryBase is needed outside of //content internals to support the following factories: ExternalFileURLLoaderFactory (CrOS), ContentDirectoryLoaderFactory (Fuchsia), ExtensionURLLoaderFactory, FileURLLoaderFactory (the one with ChildProcessSecurityPolicy-based access checks in //chrome/browser/chrome_content_browser_client.cc). Bug: 1106995 Change-Id: Iaac2693242b5daf3673fd8347a652e15757ca639 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2357431 Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#807577}
-
David Tseng authored
TBR=josiahk@chromium.org Bug: 1128926 Change-Id: Ib9c2ed0622b7b22dd94294ecd7aba8cb76b3478c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413534Reviewed-by:
David Tseng <dtseng@chromium.org> Commit-Queue: David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#807576}
-
Sharon Yang authored
This reverts commit 13c126e3. Reason for revert: This CL pulls in ui/base and increasing the size of CastRunner. The size increase is breaking the Chromium (into Fuchsia) roller. Original change's description: > [bindings] Define cross-platform NamedMessagePortConnector impl. > > Refactors NamedMessagePortConnector into a platform-agnostic component, > which can be reused across FIDL, in-process, and testing contexts. > It uses Blink messages and message ports as a common basis for > message and port transport. > > * Implements some missing portions of the Blink/FIDL MessagePort > conversion layer. > * Adds a Fuchsia implementation of NMPC. > > Bug: 1104369 > Change-Id: I01e86c38963bfb114a7466c6f73b143e5302ad1e > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2293110 > Commit-Queue: Kevin Marshall <kmarshall@chromium.org> > Reviewed-by: Jochen Eisinger <jochen@chromium.org> > Reviewed-by: David Dorwin <ddorwin@chromium.org> > Cr-Commit-Position: refs/heads/master@{#806684} TBR=ddorwin@chromium.org,kmarshall@chromium.org,jochen@chromium.org,lijiawei@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1104369 Change-Id: Ie5505f33dc2b29ce82fe5d44f8919e985da35102 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414651Reviewed-by:
Sharon Yang <yangsharon@chromium.org> Commit-Queue: Sharon Yang <yangsharon@chromium.org> Cr-Commit-Position: refs/heads/master@{#807575}
-
Abigail Klein authored
The Live Caption bubble shows title text "Live Caption" when it appears with fewer than the maximum number of lines of caption text. This behavior was introduced in an earlier CL and removed as the team explored some other designs. This CL does not introduce anything new that was not already submitted previously. Bug: 1055150 Change-Id: I679d38daba19d8874fa7d17591c668186a94bc7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414549Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Abigail Klein <abigailbklein@google.com> Cr-Commit-Position: refs/heads/master@{#807574}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/65fccf7b5f04..b82a1e239de5 2020-09-16 chrome-bot@chromium.org Update config settings by config-updater. 2020-09-16 saklein@chromium.org portage_testable: mask chromiumos and portage overlays 2020-09-16 saklein@chromium.org dependency service: Cache dependency data. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/chromite-chromium-autoroll Please CC chrome-os-gardeners@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:chromeos-betty-pi-arc-chrome;luci.chromium.try:chromeos-kevin-rel Tbr: chrome-os-gardeners@google.com Change-Id: I6d0dac6a482730ecd4f5ef8ef8091f1d39d1fbbc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414529Reviewed-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@{#807573}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/0f21b6caecea..5d45ebc33fa8 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC bcwhite@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: chromium:912681 Tbr: bcwhite@google.com Change-Id: I2c7e2867fff440add2a6551b2a861c9cdc54392e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414531Reviewed-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@{#807572}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/49c0daeb..69e49314 Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I7dfd0997decd7b2a5a57357276b2231c1c7997cc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414017Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#807571}
-