- 24 Mar, 2020 40 commits
-
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/ae3586b5380f..2b2aec6506a8 git log ae3586b5380f..2b2aec6506a8 --date=short --first-parent --format='%ad %ae %s' 2020-03-24 pkasting@chromium.org Revert "depot_tools: Run using Python 3 by default." Created with: gclient setdep -r src/third_party/depot_tools@2b2aec6506a8 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Please CC agable@chromium.org 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/+/master/autoroll/README.md Bug: None Tbr: agable@chromium.org Change-Id: I44be14eb491467c1e809f6075bcb8d05cbe0732c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117080Reviewed-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@{#752709}
-
Noel Gordon authored
Add keyboard-specific CSS rules for the drop-down menu <button>s focus and hover so they render the same effects as mouse interaction. Hence, there is no visible difference in keyboard || mouse interaction and this to match all other files app menus and context menus. Bug: 1062902, 1035691 Change-Id: I9bf24464c28036fc82a3a07ce88d1fd76cac3778 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2112372 Commit-Queue: Noel Gordon <noel@chromium.org> Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Cr-Commit-Position: refs/heads/master@{#752708}
-
chromium-autoroll authored
https://chromium.googlesource.com/native_client/src/native_client.git/+log/35bcc9f6d5e8..ffed96d1528d git log 35bcc9f6d5e8..ffed96d1528d --date=short --first-parent --format='%ad %ae %s' 2020-03-24 dschuff@chromium.org Revert "Update revision for PNaCl" 2020-03-24 thakis@chromium.org Suppress a -Wunreachable-code warning in cros/arm builds. 2020-03-07 dschuff@chromium.org Disable cond_timedwait_test and debug_stub_test on Windows 2020-03-06 dschuff@chromium.org On Windows, always do a GN build so we can use tls_edit.exe with SCons 2020-03-06 dschuff@chromium.org Don't support clang/non-clang GN builds 2020-03-05 dschuff@chromium.org Ensure that MSVC is not required to be installed not building trusted code 2020-02-28 dschuff@chromium.org Update revision for PNaCl Created with: gclient setdep -r src/native_client@ffed96d1528d If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/nacl-autoroll Please CC mseaborn@chromium.org 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/+/master/autoroll/README.md Bug: chromium:346399 Tbr: mseaborn@chromium.org Change-Id: I8ffcb099a646064f57ad89a2bbddaab34d5d0509 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117241Reviewed-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@{#752707}
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC cr-fuchsia+bot@chromium.org 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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast Tbr: cr-fuchsia+bot@chromium.org Change-Id: I796e4af3c4821fa3167250866edf781cb4cdb014 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117243Reviewed-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@{#752706}
-
Sergey Ulanov authored
CastRunner redirects AudioCapturer to the parent agent. The AudioCapturer implementation in the agent uses 16kHz sample rate internally. Update default sample rate to 16kHz, so the agent won't need to resample the stream. Bug: 1059836 Change-Id: I7519485f8dfc7c56c527730cc3c90bbf689146c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117161 Auto-Submit: Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:
David Dorwin <ddorwin@chromium.org> Commit-Queue: David Dorwin <ddorwin@chromium.org> Cr-Commit-Position: refs/heads/master@{#752705}
-
Noel Gordon authored
Make make <button> and drop-down menu <button> :active color the same, ie., don't bother trying to match :active color with other menus. Bug: 1062902, 1035691 Change-Id: Icf6dc9d0ae5f68d48f1301ff8c7f44c949c8e404 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2114311 Commit-Queue: Noel Gordon <noel@chromium.org> Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Cr-Commit-Position: refs/heads/master@{#752704}
-
calamity authored
Bug: 1062668 TBR=ayui@chromium.org Change-Id: I51e4514af63bd318c2a933b10f4d4b3595168e81 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117410Reviewed-by:
calamity <calamity@chromium.org> Commit-Queue: calamity <calamity@chromium.org> Cr-Commit-Position: refs/heads/master@{#752703}
-
Ben Joyce authored
Updates design, annotations, and lifecycle_commons Bug: 1052460 Change-Id: I521d955abfe883868473d3b293854f2105ee8852 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2116594Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Commit-Queue: benjamin joyce <bjoyce@google.com> Cr-Commit-Position: refs/heads/master@{#752702}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/06a4dd62094e..ea6ae4a32307 git log 06a4dd62094e..ea6ae4a32307 --date=short --first-parent --format='%ad %ae %s' 2020-03-23 titovartem@google.com Add calculation of actual encode bitrate into DefaultVideoQualityAnalyzer Created with: gclient setdep -r src/third_party/webrtc@ea6ae4a32307 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@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/+/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I55871ad7488c6950887a6541917031965669d886 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117079Reviewed-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@{#752701}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/85201b613e63..032c78376792 git log 85201b613e63..032c78376792 --date=short --first-parent --format='%ad %ae %s' 2020-03-24 dberris@google.com Pinpoint: Update io equal to execution timeout Created with: gclient setdep -r src/third_party/catapult@032c78376792 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 sadrul@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/+/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:1023451 Tbr: sadrul@google.com Change-Id: Icb6ac3d617c79d70b978a8232f8052832d1b54ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117075Reviewed-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@{#752700}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/12e857a3bca2..4b8b07825641 git log 12e857a3bca2..4b8b07825641 --date=short --first-parent --format='%ad %ae %s' 2020-03-23 amaiorano@google.com CMake: make SWIFTSHADER_DCHECK_ALWAYS_ON work on Windows Created with: gclient setdep -r src/third_party/swiftshader@4b8b07825641 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/+/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 Bug: None Tbr: swiftshader-team+autoroll@google.com Change-Id: Ib852f6fd731927fc826e7f62c86de52e26b005cc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117076Reviewed-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@{#752699}
-
Noel Gordon authored
Breadcrumb <button>s show focus rings when the keyboard or the pointer device (mouse/pointer/touch) is used for <button> interaction. Change that: only show focus rings for keyboard interaction, using the global focus-outline-visible class provided by the cr.ui.focus_outline visibility manager. Note the main breadcrumb <button> are direct children of the :host, so a child selector is enough to control their :focus behaviors. The last breadcrumb <button> never gets :focus (it's always [disabled]) and any hidden <button> are display:none (can not have :focus). Drop-down menu <button> do not have focus rings (no change in behavior). Bug: 1062902, 1035691 Change-Id: Ic244310f2126a30e3896f5a1da45ffacbc35dd78 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2111516 Commit-Queue: Noel Gordon <noel@chromium.org> Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Cr-Commit-Position: refs/heads/master@{#752698}
-
spdonghao authored
Bug: 1058829 Change-Id: I775623b50f5de2ca4851198deaac6b133f424e1c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2115883Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Reviewed-by:
Xi Han <hanxi@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Hao Dong <spdonghao@chromium.org> Cr-Commit-Position: refs/heads/master@{#752697}
-
Meredith Lane authored
Previously, the close button was the first thing to receive focus. WAI-ARIA dictates that for a modal dialog, focus should move to the first focusable control in the dialog, in this case the font selector. The user can still close at any time by using the Esc key. Note that this causes no visual changes; it only changes focus order. Bug: 1015200 Change-Id: Ieee530095dc90a7befc30761ddcb45e8935a8121 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2114771 Commit-Queue: Meredith Lane <meredithl@chromium.org> Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Cr-Commit-Position: refs/heads/master@{#752696}
-
Meredith Lane authored
This change changes the *-left properties to *-inline-start to comply with RTL CSS style guides, as well as a minor change to alphabetize properties. Bug: 1024894 Change-Id: I73e0d3144af9a956f026da6ebf8b681341de8032 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2113602Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Commit-Queue: Meredith Lane <meredithl@chromium.org> Cr-Commit-Position: refs/heads/master@{#752695}
-
Bettina Dea authored
This CL was generated by running the export script after updating the internal repos. Change-Id: I81992e0615dc6d18789d7be4d0d55c9b2aee64dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117054Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Commit-Queue: Bettina Dea <bdea@chromium.org> Cr-Commit-Position: refs/heads/master@{#752694}
-
rajendrant authored
Adds a histogram that is recorded once at startup when save-data estimates are available in field trial. Bug: 923551 Change-Id: Ie0d57ab0d45a8261a1c612360754f50988d3f967 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2112193Reviewed-by:
Michael Crouse <mcrouse@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Reviewed-by:
Ryan Sturm <ryansturm@chromium.org> Commit-Queue: rajendrant <rajendrant@chromium.org> Cr-Commit-Position: refs/heads/master@{#752693}
-
Wei-Yin Chen (陳威尹) authored
Bug: 1063639 Change-Id: I57eda35f46e0adc508548182cd721de918ecc25c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2114398 Commit-Queue: Wei-Yin Chen (陳威尹) <wychen@chromium.org> Reviewed-by:
Yue Zhang <yuezhanggg@chromium.org> Cr-Commit-Position: refs/heads/master@{#752692}
-
Maggie Cai authored
Currently the replaced app map uses the wrong app id. Fix this issue and also add unit test for this. BUG=853604 Change-Id: Iabc05d87faa2bc08b2c0e2922bfd875207f577d2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2113603 Commit-Queue: Maggie Cai <mxcai@chromium.org> Reviewed-by:
Nancy Wang <nancylingwang@chromium.org> Cr-Commit-Position: refs/heads/master@{#752691}
-
Noel Gordon authored
When the pointer is down, anywhere in the app, a hover over breadcrumb <button> shows its :hover effect, even though the user cannot interact with the <button>, since the user has mousedown-ed on some other files app element or <button>. We should not show a :hover effect in this case, since it suggests the <button> is interactive even though it is not. Use the global pointer- active detector added in CL:2111810 to block the :hover effects on any :not(:active) breadcrumb <button>. Bug: 1062902, 1035691 Change-Id: I96d399d22f92d93ae2249027ad4ce9b70e97f802 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2112173Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Commit-Queue: Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#752690}
-
Jinsuk Kim authored
Removes all the occurrences of TabImpl.getActivity() in gesturenav/. Now the dependencies are passed through HistoryNavigationCoordinator.create() in the form of supplier, runnable, etc. Bug: 952703 Change-Id: I722acf5cbaa866556f2b953d7760ac7aa9630604 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2106045 Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org> Reviewed-by:
David Trainor <dtrainor@chromium.org> Cr-Commit-Position: refs/heads/master@{#752689}
-
Gyuyoung Kim authored
align-baseline.html can be migrated to WPT because it doesn't use Blink internal APIs as well as doesn't have an image baseline. Besides, the spec exists. Bug: 1063749 Change-Id: I99706d7929bc572d6fbc4b9ec0d217d7feca920d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2114477Reviewed-by:
David Grogan <dgrogan@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Robert Ma <robertma@chromium.org> Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com> Cr-Commit-Position: refs/heads/master@{#752688}
-
Stephen McGruer authored
Replaced with promise_rejects_js and promise_rejects_dom. Bug: 1051932 Change-Id: I9018db17d0a64e72b5234b631da5c1937364ffdb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2116552 Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#752687}
-
Andrew Xu authored
My previous CL (https://crrev.com/c/2106958) does not cover all of scenarios. For example, show the home launcher by back gesture in tablet mode or by toggling applist button in clamshell mode. In this CL, moving the code which hides the virtual keyboard to the function [1] which handles the visibility change of applist. [1] is called before the search box view within the applist is focused (which shows the virtual keyboard through transient-blur feature). In addition, in [2], this CL ensures that the last blur time recorded in virtual keyboard controller is reset by [3]. A ash unit test case is added to verify this scenario. [1] AppListControllerImpl::OnVisibilityChanged [2] KeyboardUIController::HideKeyboard [3] KeyboardUIController::HideKeyboardExplicitlyBySystem Change-Id: I9464e21854c9dfc90e974c2ea98c183419581ab5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2111877 Commit-Queue: Andrew Xu <andrewxu@chromium.org> Reviewed-by:
Darren Shen <shend@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#752686}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/c41827fa748d..0769db92d478 git log c41827fa748d..0769db92d478 --date=short --first-parent --format='%ad %ae %s' 2020-03-23 leese@chromium.org Revert "Deduplicate tabs with same URL" 2020-03-23 michael.liao@microsoft.com [Elements - Accessibility Pane]: Adding more intuitive keyboard navigation to Accessibility tree 2020-03-23 michael.liao@microsoft.com [Elements - Event Listeners]: Add context menu item to reveal nodes in DOM 2020-03-23 michael.liao@microsoft.com [Pie Chart]: Implementing Keyboard Nav and SR functionality to pie charts 2020-03-23 sigurds@chromium.org [issues] Start counting at 0 2020-03-23 pfaffe@chromium.org Asyncify the CXX DWARF language plugin 2020-03-23 szuend@chromium.org Emit real TypeScript enums for inline declared protocol enum types 2020-03-23 sigurds@chromium.org [issues] Improve UX for issue resources collapse/expansion 2020-03-23 szuend@chromium.org Emit TypeScript enums in protocol.d.ts for Protocol enums 2020-03-23 tvanderlippe@chromium.org Typecheck test/{perf,screenshots} with TypeScript 2020-03-23 tvanderlippe@chromium.org Typecheck all e2e tests with TypeScript 2020-03-23 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS. 2020-03-23 tvanderlippe@chromium.org Add ts_library for test/e2e/application 2020-03-23 tvanderlippe@chromium.org Fix presubmit check to always run when generated files change 2020-03-23 leese@chromium.org Deduplicate tabs with same URL Created with: gclient setdep -r src/third_party/devtools-frontend/src@0769db92d478 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.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/+/master/autoroll/README.md Bug: chromium:1011811,chromium:1032016,chromium:1057979,chromium:670180,chromium:963183 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Ib3080adace5b59cea4934c3105c43391ea6aae78 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117074Reviewed-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@{#752685}
-
Peter Kasting authored
Change function signatures. This is mostly using Optional to better convey "function returns a value or failure", but also uses a struct in one spot to change outparams to multiple return values. This change exposed what I think was previously a bug, where EnumMonitorForDisplayInfoCallback() would use GetDefaultMonitorPhysicalPixelsPerInch() if it could not get an appropriate pointer device, but would use an empty vector if GetPixelsPerInchForPointerDevice() failed. Using Optional for its helpers makes it easy to use the former in both cases, which seems more correct. Bug: none Change-Id: Ie9df3da798e1c5b448b57963929955193a2a255e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2109262 Commit-Queue: Peter Kasting <pkasting@chromium.org> Reviewed-by:
Robert Liao <robliao@chromium.org> Cr-Commit-Position: refs/heads/master@{#752684}
-
Xing Liu authored
Image fetcher service is an existing backend to support image download, decode, and provides a disk cache for faster image data access. This CL implements the image cache layer using image fetcher service. TBR=msramek@chromium.org Bug: 1058534 Change-Id: I4fc47fad176e13b0ac6545e7e79c8389204161bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2113819 Commit-Queue: Xing Liu <xingliu@chromium.org> Reviewed-by:
Martin Šrámek <msramek@chromium.org> Reviewed-by:
Shakti Sahu <shaktisahu@chromium.org> Reviewed-by:
Hesen Zhang <hesen@chromium.org> Reviewed-by:
David Trainor <dtrainor@chromium.org> Cr-Commit-Position: refs/heads/master@{#752683}
-
Peter Kasting authored
More simplifications, this time sometimes touching helper functions. Bug: none Change-Id: Idaaf4be6c4ec0e70a311333b9bfb8ccf817d99d7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2108987Reviewed-by:
ccameron <ccameron@chromium.org> Reviewed-by:
Robert Liao <robliao@chromium.org> Commit-Queue: Peter Kasting <pkasting@chromium.org> Auto-Submit: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#752682}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/f1df04b094fe..06a4dd62094e git log f1df04b094fe..06a4dd62094e --date=short --first-parent --format='%ad %ae %s' 2020-03-23 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 2a41e24b..8bddf9e4 (751948:752565) Created with: gclient setdep -r src/third_party/webrtc@06a4dd62094e If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@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/+/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I397bdcfa05b8e24589e177fed02bbbdefd91c217 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117072Reviewed-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@{#752681}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/e1cd685a..c17b5128 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: Ic9a032b4370650cdec195806ada4f2534871f944 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2115748Reviewed-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@{#752680}
-
Xianzhu Wang authored
The previous display item opaqueness detection was done during painting backgrounds. It was inaccurate in the following ways: - View background opaqueness detection was incomplete; - The opaqueness was wrong when the display item's visual rect was bigger than the background; - We miss some cases of opaque chunks that are not backgrounds. Now analyze the paint record to get more accurate opaqueness. Change-Id: I176161501f85b1d00b3bf22da82307b6aa77f48f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2113806Reviewed-by:
Stefan Zager <szager@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#752679}
-
Steven Bennetts authored
For network config WebUI we provide a set of default properties when calling networkConfig.mojom.setProperties() (e.g. to set auto connect). Currently those default properties provide a vpn.type property which turns out to be mutable. We need to be sure not to set that property when providing a subset of configuration properties. This also cleans up a few other properties that should be optional in the mojom (reflecting the dual use of ConfigProperties), relying on the ONC parsing to catch errors for missing properties for new configurations (which we already do for other properties). Bug: 1062305 Change-Id: I37827c57c1e7a7e3495a7ef637cd9908fbb3d987 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2109031Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Pavol Marko <pmarko@chromium.org> Commit-Queue: Steven Bennetts <stevenjb@chromium.org> Cr-Commit-Position: refs/heads/master@{#752678}
-
chrome://media-appDavid authored
In conjunction with cl/300461197 (bin icon) and cl/301465563 (zero state) this change adds deleteOriginalFile() as a method to `ReceivedFile` (chromium implementation of AbstractFile internally) to delete a file via the FileSystemDirectoryHandle Native File System API. The implementation assumes deleting a file is successful unless an error is thrown. This change also: * registers handler deleting a file to allow untrusted to trusted context communication * adds a js borwsertest to test the delete IPC * splits the base fake class FileSystemHandle from FileSystemFileHandle * adds a fake FileSystemDirectoryHandle Bug: b/151395631, 996088 Change-Id: I92381fa2161c9e97557e48c46cd74a77b079d95e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2094419 Commit-Queue: David Lei <dlei@google.com> Reviewed-by:
Trent Apted <tapted@chromium.org> Cr-Commit-Position: refs/heads/master@{#752677}
-
John Lee authored
The CSS for cropping overflowing text with an ellipsis is common standard and never-changing, so having it as a mixin isn't as necessary. So this CL just copies the CSS to the common classes and other specific classes. Bug: 973674 Change-Id: I1fdfbd4715cb6fcd31c82745edc6e0751bb181e0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2116595Reviewed-by:
Esmael Elmoslimany <aee@chromium.org> Commit-Queue: John Lee <johntlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#752676}
-
Tibor Goldschwendt authored
Shows Google logo on NTP if theme or background color is set or if doodle is not available. Draws the Google logo single-colored if theme requires it. Bug: 1039910 Change-Id: Ica63df7b1712f81141d54664db40c8d400846582 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2111764Reviewed-by:
Moe Ahmadi <mahmadi@chromium.org> Reviewed-by:
Alex Gough <ajgo@chromium.org> Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Cr-Commit-Position: refs/heads/master@{#752675}
-
Luciano Pacheco authored
This reverts commit 7545fd48. Reason for revert: We want to enable the flag by default on ToT, the revert was intended to disable the flag on M-82, on ToT it should be enabled. Original change's description: > Revert "Files app: Enable flag files-ng by default" > > This reverts commit ea497580. > > Reason for revert: Feature moved from M-82 to M-83. > > Original change's description: > > Files app: Enable flag files-ng by default > > > > Add files-ng classes and attribute to main.html so files-ng styles are > > applied during app startup (to avoid a FOUC flash of non-files-ng blue > > color). > > > > Enable file-ng by default in FilesApp and its browser test harness. > > > > Bug: 992818 > > Change-Id: If437271c5604d36b4b0908abb663a84e52b6ae35 > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2087308 > > Reviewed-by: Alex Danilo <adanilo@chromium.org> > > Commit-Queue: Alex Danilo <adanilo@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#747421} > > TBR=noel@chromium.org,lucmult@chromium.org,adanilo@chromium.org > > Bug: 992818 > Change-Id: I8b1c770e2c43823eff9a2a9aceae650fcb25a3f8 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103992 > Reviewed-by: Luciano Pacheco <lucmult@chromium.org> > Reviewed-by: Noel Gordon <noel@chromium.org> > Reviewed-by: Alex Danilo <adanilo@chromium.org> > Commit-Queue: Luciano Pacheco <lucmult@chromium.org> > Cr-Commit-Position: refs/heads/master@{#750448} TBR=noel@chromium.org,lucmult@chromium.org,adanilo@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 992818 Change-Id: I94e63a873d4e2970d201a32dca0944a4e8fa520f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2116152Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Commit-Queue: Luciano Pacheco <lucmult@chromium.org> Cr-Commit-Position: refs/heads/master@{#752674}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/3c358420df4a..d1988219065a git log 3c358420df4a..d1988219065a --date=short --first-parent --format='%ad %ae %s' 2020-03-23 bsalomon@google.com Revert "Drawing YUVA images does not flatten for bicubic." 2020-03-23 reed@google.com Add approx_pow/log2/pow2 to SkVM builder 2020-03-23 bsalomon@google.com Drawing YUVA images does not flatten for bicubic. Created with: gclient setdep -r src/third_party/skia@d1988219065a If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC robertphillips@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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-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 Bug: None Tbr: robertphillips@google.com Change-Id: I4ce05b05e0489d9a0b06da6d6aafd2bfadbcac66 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117071Reviewed-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@{#752673}
-
Ayu Ishii authored
Change-Id: I7b7e2c0717bc20f913fba1577d34839bdecc16e1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2116011 Commit-Queue: Victor Costan <pwnall@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#752672}
-
Gang Wu authored
Bug: 977402 Change-Id: Ic77cd4b54b5ee5d46ebcd1a7c55313cdccabc199 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2090293Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Justin Donnelly <jdonnelly@chromium.org> Commit-Queue: Gang Wu <gangwu@chromium.org> Cr-Commit-Position: refs/heads/master@{#752671}
-
Sammie Quon authored
Stack trace shows window destroying calling |animating_layer_| which is the one of the windows associated with the destroyed window. My guess is that it might be a dangling pointer, so when window is destroying, set it to null. I tried reproing with a test that destroys the windows at certain points of the animation, but no luck :(. Test: none Bug: 1028815 Change-Id: I5baa2d3784836296c2afe063e6861aa43fb68e5f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2111059 Commit-Queue: Sammie Quon <sammiequon@chromium.org> Reviewed-by:
Xiaoqian Dai <xdai@chromium.org> Cr-Commit-Position: refs/heads/master@{#752670}
-