- 21 Oct, 2020 40 commits
-
-
sauski authored
CL stops appending table names into queries and inlines them directly instead. Bug: 1117381 Change-Id: I4cb5adc389f1685606ffa519383493a594e6bfac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485061Reviewed-by:
Martin Šrámek <msramek@chromium.org> Commit-Queue: Theodore Olsauskas-Warren <sauski@google.com> Cr-Commit-Position: refs/heads/master@{#819261}
-
Joel Hockey authored
go/chrome-ss/b025494050650332c0d6964cb82b977199bd9fd0 go/chrome-ss/8d3b3f36cf84c787244001584e2b8425be3e7549 Bug: 953310 Change-Id: Ie6114823134d43026cdbaace7bc364e531884ad3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2489122 Commit-Queue: Joel Hockey <joelhockey@chromium.org> Commit-Queue: Noel Gordon <noel@chromium.org> Auto-Submit: Joel Hockey <joelhockey@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#819260}
-
Fergal Daly authored
This reverts commit a9b6d2bd. Reason for revert: Causing builder to fail. First fail was 8 changes after this. https://ci.chromium.org/p/chromium/builders/ci/Win7%20Tests%20%281%29 Original change's description: > Use set_fixed_width() in c/b/ui/views dialogs > > Does not address subfolders which will be done in separate chunks. > > Bug: 1128500 > Change-Id: Id3caa97d0d59b4700b888c5bca5f89f69d4c64d1 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485148 > Commit-Queue: Peter Boström <pbos@chromium.org> > Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org> > Auto-Submit: Peter Boström <pbos@chromium.org> > Cr-Commit-Position: refs/heads/master@{#819061} TBR=ellyjones@chromium.org,pbos@chromium.org Change-Id: I0d03cb731d03bf7ba11d836769bd2513c25f1366 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1128500,1140866 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2489380Reviewed-by:
Fergal Daly <fergal@chromium.org> Commit-Queue: Fergal Daly <fergal@chromium.org> Cr-Commit-Position: refs/heads/master@{#819259}
-
Chris Hamilton authored
This will be used in upcoming instrumentation logic. BUG=1080672 Change-Id: Ic465c9277e7c84c56183691554937f231fc6a340 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2487848 Auto-Submit: Chris Hamilton <chrisha@chromium.org> Commit-Queue: Kentaro Hara <haraken@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#819258}
-
jchen10 authored
ChromeOS only uses 1 mailbox for all yuv planes, while the current VideoFrameYUVConverter assumes 1 mailbox for each plane. So that's the cause of the bug. To fix that, we have to use CopySubTexture instead. This also adds ABGR video frame support for Android. Bug: 1137947, 1135073 Change-Id: I600df595cf849aeee01ed39e2e36b2297dfc2d33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2486568 Commit-Queue: Jie A Chen <jie.a.chen@intel.com> Reviewed-by:
Eugene Zemtsov <eugene@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#819257}
-
Manu Cornet authored
Bug: 1136145, 1056219 Change-Id: I3fe051a8bdb30224a8d20b0f404d4c03f2eac80d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2467940 Auto-Submit: Manu Cornet <manucornet@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Sam McNally <sammc@chromium.org> Reviewed-by:
Ken Rockot <rockot@google.com> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Sam McNally <sammc@chromium.org> Cr-Commit-Position: refs/heads/master@{#819256}
-
David authored
Doc: http://go/backlight-better-crash-report#heading=h.148xm9y8bm2q Note: Choosing to make this an optional field in JSErrorReport in case future non crashReportClients don't have access to the browser process. Bug: b/169635499, b/167109810 Change-Id: I3d351fe2cc797fecb45b03e3a359db1be66fda20 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2483945Reviewed-by:
Giovanni Ortuño Urquidi <ortuno@chromium.org> Reviewed-by:
Patti <patricialor@chromium.org> Reviewed-by:
Ian Barkley-Yeung <iby@chromium.org> Commit-Queue: David Lei <dlei@google.com> Cr-Commit-Position: refs/heads/master@{#819255}
-
Hoch Hochkeppel authored
Adding a class to represent the Windows RandomAccessStream class within tests, as well as basic unit tests to validate the test class behaviors. This class behaves similarly to the Windows equivalent, except it includes gtest validations for expected usage and schedules all async operations through a ThreadTaskRunner. Bug: 1035527 Change-Id: Id0ce1af8995260fdcb0c2a06c6408819afc4dfbb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2487818Reviewed-by:
Eric Willigers <ericwilligers@chromium.org> Commit-Queue: Hoch Hochkeppel <mhochk@microsoft.com> Cr-Commit-Position: refs/heads/master@{#819254}
-
Morten Stenshorne authored
It would be tricky to locate the right fragment in PositionForPoint(), in cases where a node generates more than one fragment. A much easier solution is to remember which fragment we hit. Move fragment item specific code out of LayoutNGBlockFlowMixin's PositionForPoint() into the new NGPhysicalBoxFragment method PositionForPoint(). Also call this method from HitTestResult::GetPosition() if we stored a fragment during hit testing. For now we'll only do that for inline formatting contexts, since NGPhysicalBoxFragment's PositionForPoint() doesn't support block children yeyet. Bug: 829028, 1043787 Change-Id: Ifc9f3245f832bdebd2a20dbd6ebe73ca3289d80b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485219Reviewed-by:
Koji Ishii <kojii@chromium.org> Reviewed-by:
Yoshifumi Inoue <yosin@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#819253}
-
Piotr Tworek authored
This class is used as and allocator passed to std::vector. In case of libstdc++ however the allocator is inherited by std::_Vector_impl which breaks chromium builds against libstdc++. Ref: https://github.com/gcc-mirror/gcc/blob/master/libstdc%2B%2B-v3/include/bits/stl_vector.h#L129 Bug: 957519 Change-Id: I85b6d8160d3be1dc11de28c4d58fbb1510398701 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485064Reviewed-by:
Anton Bikineev <bikineev@chromium.org> Reviewed-by:
Bartek Nowierski <bartekn@chromium.org> Reviewed-by:
Tom Sepez <tsepez@chromium.org> Reviewed-by:
-
Thomas Lukaszewicz authored
Bug: None Change-Id: I80a296b678ce5ad7577c937035cd45a9bf54b30c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488383Reviewed-by:
Tommy Nyquist <nyquist@chromium.org> Commit-Queue: Thomas Lukaszewicz <tluk@chromium.org> Cr-Commit-Position: refs/heads/master@{#819251}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/792630c498fc..f736cabba58b 2020-10-20 sokcevic@google.com Add retry on git push failure 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 apolito@google.com,ehmaldonado@google.com,sokcevic@google.com,ajp@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 Bug: None Tbr: apolito@google.com,ehmaldonado@google.com,sokcevic@google.com,ajp@google.com Change-Id: I3d1bc35dc47d11a35d87f6c9c1e4cb74a64c58d8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488922Reviewed-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@{#819250}
-
Oliver Chang authored
Bug: 1140770 Change-Id: I0c9877f5cb24bb66c86df3577caee71a9fdca102 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2487742 Commit-Queue: Oliver Chang <ochang@chromium.org> Auto-Submit: Oliver Chang <ochang@chromium.org> Reviewed-by:
Takuto Ikuta <tikuta@chromium.org> Cr-Commit-Position: refs/heads/master@{#819249}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/2fb0633adec8..7a0246ff177e 2020-10-21 abennetts@google.com Reduce the data serialized in _FormatAndPostBugCommentOnComplete tasks. 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 skyostil@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:1140309 Tbr: skyostil@google.com Change-Id: I4034b94fea0a19cae4bd767de0e2586737ef4f62 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488931Reviewed-by:
-
Morten Stenshorne authored
Only RootInlineFormattingContext() understood LayoutFlowThread, and only ContainingNGBlockFlow() checked if we actually found an NG block flow. We still require the object to be inline (non-inlines shouldn't need this anyway). This doesn't affect anything right now, but I'm working on some changes that will require flow-thread-awareness. Bug: 1061423 Change-Id: If7b490d8e872de67d7a74723228f3d72f73028ff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2487081Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/a87909398b71..e38a448746e8 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 fergal@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: fergal@google.com Change-Id: Iadd54a58e896f743402fc7c611f87aab7a638588 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2489220Reviewed-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@{#819246}
-
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/goldctl-win-chromium-autoroll Please CC bsheedy@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/+doc/master/autoroll/README.md Bug: None Tbr: bsheedy@chromium.org Change-Id: Ie7f8846b200a481729861602db724b10d1fc225b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488156Reviewed-by:
-
Yuke Liao authored
This CL ensures that all tests are run when changes are made to build/lacros to avoid accidental breakages. Change-Id: I8d4d056d3e551b7786249f2be43d6513c3422af9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488980Reviewed-by:
Erik Chen <erikchen@chromium.org> Commit-Queue: Yuke Liao <liaoyuke@chromium.org> Cr-Commit-Position: refs/heads/master@{#819244}
-
Yuke Liao authored
This CL starts using ToT ash-chrome on linux-lacros-rel to run tests. Bug: 1129223 Change-Id: Icc8c51ff0ae6863b999c81d153c5a5905f0961ff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2487872Reviewed-by:
Dirk Pranke <dpranke@google.com> Commit-Queue: Yuke Liao <liaoyuke@chromium.org> Cr-Commit-Position: refs/heads/master@{#819243}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/e9c99e93e75e..cca03ca6bfe9 2020-10-20 dawn-autoroll@skia-public.iam.gserviceaccount.com Roll Tint from 7156d3e3140b to 4f79c8405028 (1 revision) 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 dsinclair@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: dsinclair@google.com Change-Id: I69cd792b021cd3d47705766b6ed66f4af093b745 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488928Reviewed-by:
-
Darren Shen authored
Android API [1] allows it, so we should too. [1] https://developer.android.com/reference/android/view/inputmethod/InputConnection#setComposingRegion(int,%20int) Bug: b/170796179 Change-Id: Iabb31d34e56f46a3b05dd53324b19169af0a53fe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2483943Reviewed-by:
Keith Lee <keithlee@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#819241}
-
Edward Lesmes authored
Generate DIR_METADATA files and remove metadata from OWNERS files for //ui/base. R=thakis@chromium.org Bug: 1113033 Change-Id: Ic45fa9c79f34412f38dd2632123c2d819f1692f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2477442Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org> Auto-Submit: Edward Lesmes <ehmaldonado@chromium.org> Cr-Commit-Position: refs/heads/master@{#819240}
-
Andrey Kosyakov authored
... it's a WeakPtr after all. Bug: 1140263 Change-Id: I4bcc7890f67b1220b756d97c53c64de012c52756 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488988Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Andrey Kosyakov <caseq@chromium.org> Cr-Commit-Position: refs/heads/master@{#819239}
-
Tal Pressman authored
Currently, renderer-side objects (RenderFrame, RenderView, etc.) assume the AgentSchedulingGroup outlives them, but this is not the case if the disconnect handler is called before they are destroyed. After this CL, the ASG's lifetime will match the RenderThread's, and it will be destroyed when the RenderThread is destroyed. This is OK for now, since we currently only have a single ASG per process and the host's lifetime matches the RenderProcessHost's. In the meantime, kouhei@ is working on properly shutting down ASGs via an IPC, similar to other objects. Bug: 1137580, 1138942 Change-Id: Iab02cecf3cd828a0b84f2bc29e451d1a591422ad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2478622 Commit-Queue: Tal Pressman <talp@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
-
Arnaud Mandy authored
Test is not passing in upstream wpt due to insecure context error. https://wpt.fyi/results/screen_enumeration/screen_enumeration_permission.window.html?run_id=728120001 Renaming file with .https. extension to use secure context. Bug: 1075656 Change-Id: I5842a253d296b364bfc26130b7f0f0af23dc90de Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485503Reviewed-by:
Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> Reviewed-by:
Michael Wasserman <msw@chromium.org> Commit-Queue: Arnaud Mandy <arnaud.mandy@intel.com> Cr-Commit-Position: refs/heads/master@{#819237}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/bd66f2d95186..d2e6434aadb1 2020-10-21 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS. 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/+doc/master/autoroll/README.md Bug: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Iefd37357fea84f35f9564c4e76aa0e388bcbc2a1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2487771Reviewed-by:
-
Fergal Daly authored
This reverts commit b9d174e5. Reason for revert: I think this is causing tree closures https://ci.chromium.org/p/chromium/builders/ci/android-archive-dbg/6649? Original change's description: > Enable isolated splits in canary > > All known issues have been fixed so enabling this in canary to see if > there are any major problems. > > Bug: 1126301 > Change-Id: I0c3bc7443fcca8b81f7c2652d90b982872f7ea08 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2478144 > Commit-Queue: Clark DuVall <cduvall@chromium.org> > Reviewed-by: Andrew Grieve <agrieve@chromium.org> > Cr-Commit-Position: refs/heads/master@{#819200} TBR=agrieve@chromium.org,cduvall@chromium.org Change-Id: I6d4266c956c435cd21b0b0d9d36135def48a933b No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1126301 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488961Reviewed-by:
-
Alexey Baskakov authored
Drive-by: Use GetApps() iteration where `is_in_sync_install` flag was checked. This CL introduces no behavior changes. This is a follow up renaming for previous CL: https://chromium-review.googlesource.com/c/chromium/src/+/1295131 Bug: 891172 Change-Id: I3f187846c5d1732835da618293c5bd6d37cfbcc2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485417Reviewed-by:
Daniel Murphy <dmurph@chromium.org> Commit-Queue: Alexey Baskakov <loyso@chromium.org> Cr-Commit-Position: refs/heads/master@{#819234}
-
Timothy Loh authored
This CL fixes a crash that can occur when a USB device shared with a VM is shared with a different VM. If the device has not yet been attached, e.g. as the first VM is not yet started, we end up in a recursive loop between CrosUsbDetector::AttachUsbDeviceToVm(), DetachUsbDeviceFromVm() and AttachAfterDetach(), eventually getting a stack overflow. Bug: b/171265431 Change-Id: I0ecc28e55160c310473dce3a98f8ada0f99eb3a1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485660 Commit-Queue: Timothy Loh <timloh@chromium.org> Commit-Queue: Nicholas Verne <nverne@chromium.org> Reviewed-by:
Nicholas Verne <nverne@chromium.org> Cr-Commit-Position: refs/heads/master@{#819233}
-
Alex Kalugin authored
Download.DownloadManager.CreationDelay histogram description states > Records the delay of creating non-incognito download manager after the > download system is initialized. but currently histogram is reported only for incognito profiles. Change-Id: I48344f2b67af3cb1bf62b54d6b2b7fbb507b5e20 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485269Reviewed-by:
Min Qin <qinmin@chromium.org> Commit-Queue: Alexander Kalugin <akalugin@yandex-team.ru> Cr-Commit-Position: refs/heads/master@{#819232}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/85d9d5d4bbc6..84f5eeb6dd9b 2020-10-21 amaiorano@google.com Fix Android build 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: None Tbr: swiftshader-team+autoroll@google.com Change-Id: I97406f7996c9fc47ca7bae0ba77163e3704cd61b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488154Reviewed-by:
-
Nidhi Jaju authored
According to https://github.com/whatwg/streams/pull/1035, all methods and accessors are now enumerable, per Web IDL defaults, instead of non-enumerable, per ECMAScript defaults. Hence, 'NotEnumerable' can be removed from the Streams WebIDL files. This CL specifically removes them from transform streams. Bug: 1093862 Change-Id: I509b470722039ebad20b8caeaa7f34189c24b1ba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2486006 Commit-Queue: Nidhi Jaju <nidhijaju@google.com> Reviewed-by:
Adam Rice <ricea@chromium.org> Cr-Commit-Position: refs/heads/master@{#819230}
-
Andrew Grieve authored
All uses of it replaced with one of: * Arrays.asList() * Collections.emptyList() * Collections.singletonList() TBR=agrieve # Trivial .java refactor to //components Bug: 1056751 Change-Id: Ie70e425312da48058a098a512cbafa26bdfa5fec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2476839 Commit-Queue: Andrew Grieve <agrieve@chromium.org> Reviewed-by:
-
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/goldctl-linux-chromium-autoroll Please CC bsheedy@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/+doc/master/autoroll/README.md Bug: None Tbr: bsheedy@chromium.org Change-Id: Ie45833037473cdcbcf7e9112317f574a2c84c27a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488152Reviewed-by:
-
Sam Sebree authored
Controls This adds slight opacity to the dark mode audio control default background, and addresses some background color bugs for the dark mode video control overlay menu. Bug: 1111887 Change-Id: Ie677110b32b4588459038f820db713924f2e8e4e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2486033Reviewed-by:
Kent Tamura <tkent@chromium.org> Reviewed-by:
Mason Freed <masonfreed@chromium.org> Commit-Queue: Sam Sebree <sasebree@microsoft.com> Cr-Commit-Position: refs/heads/master@{#819227}
-
Kramer Ge authored
This is a reland of aa21781d Root-cause of previous issue was Gnome's interpretation of whether buffer.release should be triggered for buffers preempted from subsurface cache. Original change's description: > [ozone/wayland] Use 4x4 opaque background and stack underlay correctly > > Using a 4x4 sized opaque background will not regress performance in > underlay cases because the root surface is still opaque. The background > will be stretched out by wayland viewporter extension. > > This is 6/? CL for overlay forwarding using wl_subsurface. > > Change-Id: I59b0d4cdbfbb6727d578e286c9d19cf69a9bff32 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352523 > Commit-Queue: Kramer Ge <fangzhoug@chromium.org> > Reviewed-by: Robert Kroeger <rjkroege@chromium.org> > Reviewed-by: Maksim Sisov (GMT+3) <msisov@igalia.com> > Cr-Commit-Position: refs/heads/master@{#810527} Change-Id: I7ecbc27a82598479f7131b5645dfe96136d227a1 Bug: 1133195, 1063865 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2442137Reviewed-by:
Robert Kroeger <rjkroege@chromium.org> Commit-Queue: Kramer Ge <fangzhoug@chromium.org> Cr-Commit-Position: refs/heads/master@{#819226}
-
Adam Rice authored
This reverts commit a2505c5b. Reason for revert: Broken bots, possibly caused by CQ collision. See https://crbug.com/1140836 Original change's description: > Remove NotEnumerable from Writable Streams WebIDL > > According to https://github.com/whatwg/streams/pull/1035, all methods > and accessors are now enumerable, per Web IDL defaults, instead of > non-enumerable, per ECMAScript defaults. Hence, 'NotEnumerable' can > be removed from the Streams WebIDL files. This CL specifically > removes them from writable streams. > > Bug: 1093862 > Change-Id: I935a9f8726b3cb1dc4efb5b4d6db71384c8efe37 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485664 > Reviewed-by: Adam Rice <ricea@chromium.org> > Commit-Queue: Nidhi Jaju <nidhijaju@google.com> > Cr-Commit-Position: refs/heads/master@{#819181} TBR=ricea@chromium.org,nidhijaju@google.com Change-Id: I3f49640931f5968e1127664f6d755525dcdb9543 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1093862 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2489062Reviewed-by:
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=bindusuvarna@chromium.org Change-Id: Ia4b3dfc28460e388dcc85b67ca36ac56053564bd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488304Reviewed-by:
Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#819224}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/637786a9a862..9d160b0bba68 2020-10-20 cnorthrop@google.com Tests: Add Brawl Stars trace If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC jonahr@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_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: jonahr@google.com Test: Test: angle_perftests --gtest_filter="*brawl_stars*" Change-Id: Ie1ca382f65ea3133b29e0c7105fe86aaebe3fb0b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488924Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/fbc6250f7a85..a87909398b71 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 fergal@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:1117663,chromium:1138023,chromium:1140725 Tbr: fergal@google.com Change-Id: Ibd57a5193eeaa4629f193641f8f8f46fb06c1453 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488148Reviewed-by:
-
