- 22 Oct, 2019 40 commits
-
-
Jakob Gruber authored
The V8 natives blob (natives_blob.bin) is unused and will shortly be removed in V8. This CL removes all related infrastructure in chromium. Specifically, this means that natives_blob.bin is no longer 1. generated during the build process, 2. installed on the target system, 3. loaded by chrome at runtime, and 4. passed to V8. Tbr: oksamyt@chromium.org Bug: v8:7624 Change-Id: I535d4308a8aa539c354a212174d47ade411bc89d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1847217Reviewed-by:
Oksana Zhuravlova <oksamyt@chromium.org> Reviewed-by:
Jochen Eisinger <jochen@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Reviewed-by:
Greg Thompson <grt@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#708094}
-
Mirko Bonadei authored
No-Try: True Bug: 1006238 Change-Id: I20bc6b5ccb3d2d76bca741b4e4edc43a91f8a692 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872730Reviewed-by:
-
Lei Zhang authored
Also enforce modern Bind/Callback in device/udev_linux/. Also fix lint errors. Bug: 714018 Change-Id: Ic312e3a1df3ec63a4d2bc8bb5f2f52e7728f1006 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869286Reviewed-by:
Reilly Grant <reillyg@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#708092}
-
Jordan Taylor authored
This is part of an effort to remove any knowledge of what kind of timeline has been supplied to Animation and WorkletAnimation. This change eliminates a call to IsScrollTimeline() in WorkletAnimation. Bug: 1012073 Change-Id: Ia8d41cb22bea377230bb3c10e1d5a4d9fc19d30c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1846247 Commit-Queue: Jordan Taylor <jortaylo@microsoft.com> Reviewed-by:
Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#708091}
-
nancy authored
BUG=1009248 Change-Id: Icb801fae7334a9563e2209edb000d542f866653f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1842975 Commit-Queue: Nancy Wang <nancylingwang@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Cr-Commit-Position: refs/heads/master@{#708090}
-
dpapad authored
chrome_extensions.js: 8c8758d268411a685b187a9942077c604a8e11c3 -> 5a25bfc4e006f1a965d362e27938611242908acd - Delete third_party/closure_compiler/externs/web_animations.js and all references to it. No longer needed since a better version of these externs is distributed within compiler.jar itself. - Fix newly found JSC_HIDDEN_INTERFACE_PROPERTY_MISMATCH, as a result of the interface checking overhaul at [1] - Fix/suppress newly found JSC_CONSTANT_PROPERTY_REASSIGNED_VALUE errors. The latest version of chrome_extensions.js contains a fix needed by PDF Viewer. [1] https://github.com/google/closure-compiler/commit/86acbd5e3ec78f08a1804df5f1efbea129d29c0e Bug: 1011585 Change-Id: Ic7682834da9cfb75990d82fd8d34d3325d0a6bc3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1842626Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Reviewed-by:
Joel Hockey <joelhockey@chromium.org> Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Joel Hockey <joelhockey@chromium.org> Cr-Commit-Position: refs/heads/master@{#708089}
-
Ted Meyer authored
Change-Id: I7bc8a657876c645a61c9e019e2b9e13b9fcd0c33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872728Reviewed-by:
Xiaohan Wang <xhwang@chromium.org> Commit-Queue: Ted Meyer <tmathmeyer@chromium.org> Cr-Commit-Position: refs/heads/master@{#708088}
-
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: If85d41719f043e981e4adef3e7554b9869945152 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873091Reviewed-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@{#708087}
-
Lukasz Anforowicz authored
Bug: 827321 Change-Id: Id882e2582e4afb4fc91f3df2958864248cb42c3b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1863250 Auto-Submit: Łukasz Anforowicz <lukasza@chromium.org> Reviewed-by:
Tommy Nyquist <nyquist@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Cr-Commit-Position: refs/heads/master@{#708086}
-
chrome://flagsTed Meyer authored
Right now the only way to enable this is with command line flags which don't work so well for testing mobile. We also want to keep this separate from the devtools experiment flag so we can test it separately with finch, etc. Change-Id: I26de54af2c05bf40ce4a9583be763e5a34a2b24b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869484 Commit-Queue: Ted Meyer <tmathmeyer@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#708085}
-
Jay Harris authored
Some actions (such as file handler registration on Linux) can only be run after shortcuts have been created. This CL provides a way for those actions to be run at the appropriate time. Bug: 860581 Change-Id: Iea6a14c15c15c4ab39e8b0bbb71ac996dd9c0e81 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868566 Commit-Queue: Jay Harris <harrisjay@chromium.org> Reviewed-by:
Alexey Baskakov <loyso@chromium.org> Cr-Commit-Position: refs/heads/master@{#708084}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=benmason@chromium.org Change-Id: I92efd5b68f839b8190f0c7c5d5ee002f3f8b2594 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873346Reviewed-by:
Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#708083}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/0ce6d876771d..ca28b0ef0037 git log 0ce6d876771d..ca28b0ef0037 --date=short --no-merges --format='%ad %ae %s' 2019-10-22 vapier@chromium.org autotest_quickmerge: fix under Python 3 2019-10-22 manojgupta@google.com cros_fuzz: Install virtual/implicit-system only if needed. 2019-10-22 vapier@chromium.org cros_branch_unittest: encode captured output 2019-10-21 vapier@chromium.org trigger_cr50_signing: fix __call__ signature Created with: gclient setdep -r src/third_party/chromite@ca28b0ef0037 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/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel TBR=chrome-os-gardeners@google.com Bug: None Change-Id: Id53ce3d8ed196d4c29be413ba1a67cb498fdf143 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873325Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/8f5594ef1fc7..ea7ed55c01a4 Created with: gclient setdep -r src-internal@ea7ed55c01a4 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 jbudorick@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.chrome.try:linux-chromeos-chrome TBR=jbudorick@google.com Bug: chromium:None Change-Id: I0630c9723438ff1fc8f02b56230ecf5262b1d6a0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873326Reviewed-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@{#708081}
-
Darren Shen authored
There are some logic in JS that determines whether to send keys to Mojo or not. We need to move this code to C++. Original code: //chos/pk/rulebasedcontroller.js We decided to move this code to the IME service side, i.e. all keys are now sent via Mojo, but only some keys are processed by the rule-based engine. This shouldn't change behaviour, apart from performance, since we now send Ctrl keys etc. over Mojo where we didn't before. However, we'll need to send these keys for UIL-based IMEs anyway, since Mozc needs to handle shortcut keys. Once this CL lands, we will delete the corresponding code in JS. Bug: 1009903 Change-Id: I1cf9dc7bde47bf6f19d16d475e6380aaa6883439 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1837312 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by:
Shu Chen <shuchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#708080}
-
Evan Stade authored
Lazy creation meant that sometimes, at least in tests, UserScriptListener wasn't created early enough to do its job (profiles were added and user script update notifications were sent before UserScriptListener was created). Bug: none Change-Id: Id0a3c394da2d5bd2c58da5d26118f4448c68107d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1853912 Commit-Queue: Evan Stade <estade@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Cr-Commit-Position: refs/heads/master@{#708079}
-
Peter Kasting authored
Bug: 82078 Change-Id: I87af44296ebacdf71a0c80caa1899f8798d5f4fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872933 Commit-Queue: Peter Kasting <pkasting@chromium.org> Reviewed-by:
Alan Cutter <alancutter@chromium.org> Auto-Submit: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#708078}
-
Peter Kasting authored
Bug: 82078 Change-Id: I444a23b749667b59f6f33b36c76e00e2ff03ff6f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873274 Commit-Queue: Peter Kasting <pkasting@chromium.org> Commit-Queue: Eric Willigers <ericwilligers@chromium.org> Reviewed-by:
Eric Willigers <ericwilligers@chromium.org> Auto-Submit: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#708077}
-
siyua authored
The metrics for avatar highlight will be added later. Bug: 932818 Change-Id: I2bee343bd0b550897cfb3dc4cc4a2ca151840a18 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1860512 Commit-Queue: Siyu An <siyua@chromium.org> Reviewed-by:
Nik Bhagat <nikunjb@chromium.org> Reviewed-by:
Evan Stade <estade@chromium.org> Reviewed-by:
Jared Saul <jsaul@google.com> Reviewed-by:
Christos Froussios <cfroussios@chromium.org> Cr-Commit-Position: refs/heads/master@{#708076}
-
Daniel Hosseinian authored
Change-Id: Ib2a9cf2b39eb758d120cff562c385d17a6d5c526 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1861139 Commit-Queue: Daniel Hosseinian <dhoss@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#708075}
-
Jian Cai authored
While testing llvm-libunwind for unwinding, we ran into a build failure caused by nacl being built with --rtlib=libgcc, and requiring libgcc for unwinding. Force it with --unwindlib=libgcc. Bug:870480 Change-Id: I4a1b601cd254b6a77c2612342e783cc2e0b083fd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1836152Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Reviewed-by:
Derek Schuff <dschuff@chromium.org> Auto-Submit: Jian Cai <jiancai@google.com> Commit-Queue: Jian Cai <jiancai@google.com> Cr-Commit-Position: refs/heads/master@{#708074}
-
Fergal Daly authored
I'm not deleting them because the set up is a bit complex and we can just leave them empty and ready to use if needed for now. All tests pass when built with is_component_build=false. android_browsertests https://chromium-swarm.appspot.com/task?id=480617e093827910 content_shell_test_apk https://chromium-swarm.appspot.com/task?id=48062ebc37df7010 chrome_public_test_apk https://chromium-swarm.appspot.com/task?id=48059c46554c9d10 content_browsertests is more complex and will come in a later CL. Bug: 1016230 Change-Id: I7a2a0af9906589903dadf2fd0334fec9415497d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872071Reviewed-by:
Alexander Timin <altimin@chromium.org> Commit-Queue: Fergal Daly <fergal@chromium.org> Cr-Commit-Position: refs/heads/master@{#708073}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/f228038ddeb4..5335faaece2a git log f228038ddeb4..5335faaece2a --date=short --no-merges --format='%ad %ae %s' 2019-10-22 jonahr@google.com Robust validate_step_info in generate_stats.py Created with: gclient setdep -r src/third_party/angle@5335faaece2a 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/+/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_optional_gpu_tests_rel TBR=jonahr@google.com Bug: None Change-Id: I18ce91c1039c092637f39541662d9e9997eee629 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873089Reviewed-by:
-
Jordan Bayles authored
This patch adds a thread checker to the ChromePlatformClient class in the Open Screen platform code under media router. This thread checker ensures that the members on the ChromePlatformClient singleton are properly teared down on the right thread. Change-Id: I6e4dfcfbbece12b86329b1936224ae602b5d03bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869447 Commit-Queue: Jordan Bayles <jophba@chromium.org> Reviewed-by:
mark a. foltz <mfoltz@chromium.org> Cr-Commit-Position: refs/heads/master@{#708071}
-
Alexandre Courbot authored
On some devices (e.g. Cheza), the actual coded width of a buffer may differ from the macroblock-aligned width the driver works on. This can lead to the following DCHECK to be raised: FATAL:v4l2_video_decode_accelerator.cc(671)] Check failed: egl_image_size_.width() == adjusted_coded_width (320 vs. 384) Interestingly we already had code that fixed this by setting the EGL width to the actual buffer's width, but this code was only used in case an image processor was present. This CL generalizes the code to all cases. Bug: b:143049464 Test: video_decode_accelerator_tests passing on Cheza and Hana. Change-Id: I7c65ca469f637bd360259fb6b3d94a6eba8a73e8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871529 Auto-Submit: Alexandre Courbot <acourbot@chromium.org> Commit-Queue: Hirokazu Honda <hiroh@chromium.org> Reviewed-by:Hirokazu Honda <hiroh@chromium.org> Cr-Commit-Position: refs/heads/master@{#708070}
-
Alexandre Courbot authored
AllocatedSizeFromV4L2Format() returns the calculated size of a buffer, being given its V4L2 format. This method does not modify the format whatsoever ; thus, pass it as const reference in order to avoid an unneeded copy. Bug: None Test: video_decode_accelerator_tests passes on Kevin. Change-Id: Ifd0bf98022efe44a6b72f6c684a452c969add83d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871490 Auto-Submit: Alexandre Courbot <acourbot@chromium.org> Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/e9fd87c45f43..8f5594ef1fc7 Created with: gclient setdep -r src-internal@8f5594ef1fc7 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 jbudorick@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.chrome.try:linux-chromeos-chrome TBR=jbudorick@google.com Bug: chromium:None Change-Id: I75dbaa037a6ffe4564d99e18132582875fc8380d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873090Reviewed-by:
-
Reilly Grant authored
This is a follow-up to r707007 which enables the route for chrome://settings/content/serialPorts. Otherwise the "Serial ports" option is visible but clicking it does nothing. Bug: 967863 Change-Id: I53a04345cb63fe5045e0de2a475dc7b61945a676 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872738 Auto-Submit: Reilly Grant <reillyg@chromium.org> Commit-Queue: Dan Beam <dbeam@chromium.org> Reviewed-by:
Dan Beam <dbeam@chromium.org> Cr-Commit-Position: refs/heads/master@{#708067}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/94e1a5268692..81e8d3b29662 git log 94e1a5268692..81e8d3b29662 --date=short --no-merges --format='%ad %ae %s' 2019-10-21 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). 2019-10-21 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). Created with: gclient setdep -r src/third_party/skia@81e8d3b29662 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 michaelludwig@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 TBR=michaelludwig@google.com Bug: None Change-Id: I746b21b4f6355d1819b88572c8d7a778e7a7a10d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871647Reviewed-by:
-
Ken MacKay authored
Thereby making it more efficient. Merge-With: eureka-internal/326819 Bug: internal b/127963522 Change-Id: Idc7db2c86d54c3b14293f407744c51ac6e9d40e1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869128Reviewed-by:
Yuchen Liu <yucliu@chromium.org> Commit-Queue: Kenneth MacKay <kmackay@chromium.org> Cr-Commit-Position: refs/heads/master@{#708065}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/75c59424e3f1..53f9e0979a58 git log 75c59424e3f1..53f9e0979a58 --date=short --no-merges --format='%ad %ae %s' 2019-10-21 martiniss@google.com Roll led to latest version 2019-10-21 ehmaldonado@chromium.org depot_tools: Include httplib2 using vpython. Created with: gclient setdep -r src/third_party/depot_tools@53f9e0979a58 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 TBR=agable@chromium.org Bug: chromium:1015682,chromium:1002153 Change-Id: Ia7715d47c6389847d0c79059d63b1992ca21c87e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871645Reviewed-by:
-
Miguel Casas authored
This CL removes the 3 flags enable-webrtc-hw-{h264,vp8,vp9}-encoding because they were deprecated in M76 and will be hidden in M78. These flags are used in peerconnection/rtc_video_encoder_factory.cc to filter the supported codecs to be added to the SDP. The same filtering effect can be obtained by using the still existing flag --disable-webrtc-hw-encoding which is also surfaced to chrome:flags and used in peerconnection/video_codec_factory.cc [1], albeit at a coarser granularity: no codec-level enable/disable is available. [1] https://cs.chromium.org/chromium/src/third_party/blink/renderer/platform/peerconnection/video_codec_factory.cc?type=cs&q=IsWebRtcHWEncodingEnabled&g=0&l=180 Bug: 599650 Change-Id: I35bde6cd50c88ca8641dd9a6bd5a3e44394cde43 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1863153Reviewed-by:Dmitry Gozman <dgozman@chromium.org> Auto-Submit: Miguel Casas <mcasas@chromium.org> Commit-Queue: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#708063}
-
Nick Harper authored
TBR=rsleevi@chromium.org Change-Id: I3e63dc63920c2c23782c955f13f19b1a42c3bc56 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872159Reviewed-by:
Nick Harper <nharper@chromium.org> Reviewed-by:
Ryan Sleevi <rsleevi@chromium.org> Commit-Queue: Nick Harper <nharper@chromium.org> Cr-Commit-Position: refs/heads/master@{#708062}
-
Evan Stade authored
This re-lands f72a8099 "WebLayer: add tests for DownloadDelegate" Bug: none Change-Id: Ie18d955d2754baa9a91d742844ba42fdbc823d93 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872461 Commit-Queue: Evan Stade <estade@chromium.org> Reviewed-by:
Clark DuVall <cduvall@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#708061}
-
Dan Beam authored
Bug: none Change-Id: I796e54e6d92123dde787df0a674c4ba556fcf56a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869750 Commit-Queue: Dan Beam <dbeam@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Auto-Submit: Dan Beam <dbeam@chromium.org> Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#708060}
-
minch authored
Bug: 1002733 Change-Id: I9627f1c3208a0c0a8aaf1c1fe393266dfaa4bfd7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872755Reviewed-by:
Xiaoqian Dai <xdai@chromium.org> Commit-Queue: Min Chen <minch@chromium.org> Cr-Commit-Position: refs/heads/master@{#708059}
-
Regan Hsu authored
Currently, on Krane devices, the wallpaper preview header navbar is cut off awkwardly because there is a hardcoded length. This CL ensures that the navbar changes size based on the screensize, so the navbar doesn't cut off awkwardly. screenshots (both after): https://screenshot.googleplex.com/5wXNJCk2nww https://screenshot.googleplex.com/wprpDqdd7mP Bug: 997474 Change-Id: I99e89c57cf822c4e363313d2096aade2519f1101 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868595 Commit-Queue: Regan Hsu <hsuregan@chromium.org> Reviewed-by:
-
Eric Willigers authored
This initial implementation always displays the buttons in app windows when the new "DesktopMinimalUI" feature flag is enabled. For now, the buttons are shown in the top-right corner. Remaining work: - only show the buttons when minimal-ui is specified in the app manifest - move the buttons to the top left corner - decide on a color to use when "Back" is disabled Screen shots: https://bugs.chromium.org/p/chromium/issues/detail?id=1007151#c6 TBR: alemate@chromium.org Bug: 1007151 Change-Id: I1a6bf03823462f684326d34f019f201902a1589b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1863050 Commit-Queue: Eric Willigers <ericwilligers@chromium.org> Reviewed-by:
Bret Sepulveda <bsep@chromium.org> Reviewed-by:
-
tby authored
Bug: 959679 Change-Id: Ibe31eb89715b60313fef5b6772d9a1c5f2bd3c7b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866090Reviewed-by:
-
Daniel Hosseinian authored
The current base32 component only has an encoder. A decoder would be valuable, especially in testing situations where the input of the encoder can be compared to decoded output of the encoder. Change-Id: Ic675bb7dff405237d04f563f465a89966270bce4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865545Reviewed-by:
-
