- 27 Aug, 2020 40 commits
-
-
Garrett Beaty authored
Bug: 1109276 Change-Id: Ic6be3f297401bce87019ef398271769da515de4c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2380256 Auto-Submit: Garrett Beaty <gbeaty@chromium.org> Reviewed-by:
Erik Staab <estaab@chromium.org> Commit-Queue: Erik Staab <estaab@chromium.org> Cr-Commit-Position: refs/heads/master@{#802293}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/3d3b531b64fa..1f580a97e55f 2020-08-27 terelius@webrtc.org Revert "Make cricket::SctpTransportInternalFactory injectable through PeerConnectionFactory Deps" 2020-08-27 perkj@webrtc.org Make cricket::SctpTransportInternalFactory injectable through PeerConnectionFactory Deps 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/+doc/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I78080ff44ae3e518837b7458fed50c6112a6d879 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2380330Reviewed-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@{#802292}
-
Swapnil authored
We have several failure reasons that specify why the extension failed to install. We have classified some of the failures as misconfiguration from the admin side. We want to add a flag whether the current failure is misconfiguration or not to the existing event type INSTALLATION_FAILED for the event based reporting for force installed extensions. Bug: 1116398 Change-Id: I93b0e92fdf798a897e3033b5e348db90393432ca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352825Reviewed-by:
Oleg Davydov <burunduk@chromium.org> Reviewed-by:
Saurabh Nijhara <snijhara@google.com> Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Commit-Queue: Swapnil Gupta <swapnilgupta@google.com> Cr-Commit-Position: refs/heads/master@{#802291}
-
Justin Cohen authored
Bug: 1115121 Change-Id: I83cdd4e83a96b47c1cb5a5261487ebbf7245c5fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2376721 Auto-Submit: Justin Cohen <justincohen@chromium.org> Commit-Queue: Rohit Rao <rohitrao@chromium.org> Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Cr-Commit-Position: refs/heads/master@{#802290}
-
Anastasia Helfinstein authored
AX-Relnotes: n/a. Bug: 1122216 Change-Id: I971e5399d2122e76221c1b7e39f79fbb54c1b2a6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2376669 Commit-Queue: Akihiro Ota <akihiroota@chromium.org> Reviewed-by:
Akihiro Ota <akihiroota@chromium.org> Auto-Submit: Anastasia Helfinstein <anastasi@google.com> Cr-Commit-Position: refs/heads/master@{#802289}
-
Kristi Park authored
Used to track how many screenshots users are taking. Bug: 1109940 Change-Id: I78b0e24c35f87f2e6094a9be560bb1503d225709 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2372911Reviewed-by:
Ilya Sherman <isherman@chromium.org> Commit-Queue: Kristi Park <kristipark@chromium.org> Cr-Commit-Position: refs/heads/master@{#802288}
-
Hans Wennborg authored
Ran `tools/clang/scripts/upload_revision.py 33ce275fc156c8b015acfad918937028b2cc235c`. Bug: 1120645 Change-Id: I44b20217fb4468bd9d73e8a2ec83ec6f09840e2f Cq-Include-Trybots: chromium/try:chromeos-amd64-generic-cfi-thin-lto-rel Cq-Include-Trybots: chromium/try:dawn-win10-x86-deps-rel Cq-Include-Trybots: chromium/try:linux-chromeos-dbg Cq-Include-Trybots: chromium/try:linux_angle_deqp_rel_ng Cq-Include-Trybots: chromium/try:linux_chromium_cfi_rel_ng Cq-Include-Trybots: chromium/try:linux_chromium_chromeos_asan_rel_ng Cq-Include-Trybots: chromium/try:linux_chromium_chromeos_msan_rel_ng Cq-Include-Trybots: chromium/try:linux_chromium_compile_dbg_32_ng Cq-Include-Trybots: chromium/try:linux_chromium_msan_rel_ng Cq-Include-Trybots: chromium/try:mac-arm64-rel,mac_chromium_asan_rel_ng Cq-Include-Trybots: chromium/try:win-angle-deqp-rel-64 Cq-Include-Trybots: chromium/try:win-asan,win7-rel,win-angle-deqp-rel-32 Cq-Include-Trybots: chrome/try:iphone-device,ipad-device Cq-Include-Trybots: chrome/try:linux-chromeos-chrome Cq-Include-Trybots: chrome/try:win-chrome,win64-chrome,mac-chrome Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2377875Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#802287}
-
Mohamed Mansour authored
In RTL mode, this will render the focus ring in the right spot and allow it to be traversable via keyboard shortcuts in the correct direction. AX-Relnotes: Focus ring does not appear distorted and left / right arrow keys behave correctly in the Task Manager and other tables in Chromium's UI, when right-to-left languages are used. Bug: 1030617, 1121715 Change-Id: I303a55486205c25580d6985462949dc0b79bf4d3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375736Reviewed-by:
Peter Boström <pbos@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Nektarios Paisios <nektar@chromium.org> Commit-Queue: Mohamed Mansour <mmansour@microsoft.com> Cr-Commit-Position: refs/heads/master@{#802286}
-
Alex Chau authored
- container:btree, functional:bind_front and strings:str_format are added, none of them requires .def update - container:btree does not build due to extra colon when __cpp_inline_variables is undefined, added a patch to only include colon when the macro is defined Bug: 1046390 Change-Id: Id0f48966b185e582dbbce39de6f957ba6a534b8f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2379833Reviewed-by:
Mirko Bonadei <mbonadei@chromium.org> Commit-Queue: Alex Chau <alexchau@chromium.org> Cr-Commit-Position: refs/heads/master@{#802285}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/8e6246dafe61..cc61e5a98324 2020-08-27 fmayer@google.com Add Known Issue about 32-bit bugs. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Please CC perfetto-bugs@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:linux-perfetto-rel Bug: chromium:163551040 Tbr: perfetto-bugs@google.com Change-Id: Ie19585a25759f09a391a596279ec5fb693c9c359 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2380022Reviewed-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@{#802284}
-
ckitagawa authored
Only capture previews of http/https pages. Some people have been suprised when an FDT was shown on chrome://flags and capturing only really makes sense for http/https anyways. Change-Id: Idaaa44711abc6b2cf2cd029277f5bf23f4eae5cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2377558Reviewed-by:
Mehran Mahmoudi <mahmoudi@chromium.org> Commit-Queue: Calder Kitagawa <ckitagawa@chromium.org> Cr-Commit-Position: refs/heads/master@{#802283}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/aba6b93dfbc8..faa844b3686c 2020-08-27 mtklein@google.com collapse some unused type hierarchy 2020-08-27 johnstiles@google.com Use an unordered map for intrinsics in the IR generator. 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 mtklein@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-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 Cq-Do-Not-Cancel-Tryjobs: true Bug: None Tbr: mtklein@google.com Change-Id: Ibf9c66ae1c5927a81939c07fc9a5b79ff5105840 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2380018Reviewed-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@{#802282}
-
rbpotter authored
Proof of concept CL updating Print Preview to use the new grit_preprocess build rule to generate inputs for rollup, instead of generating a pak file and unpak folder from the grd file. Bug: 1071641 Change-Id: Ic9a15c6c546be979ce68ad4d90537c142163a024 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370162Reviewed-by:
dpapad <dpapad@chromium.org> Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#802281}
-
Omer Katz authored
See comments in the issue for explanation of the crash. Bug: 1114579 Change-Id: Ic8158b53f5de1b0239003202bafb654e6584fad6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2379757 Commit-Queue: Omer Katz <omerkatz@chromium.org> Auto-Submit: Omer Katz <omerkatz@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#802280}
-
Charlene Yan authored
Bug: 1080383, 10182301 Change-Id: I57a65bfeabfa0a854f0585b0f1571be48bc1a73d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2377233 Commit-Queue: Charlene Yan <cyan@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#802279}
-
Eric Willigers authored
Add feature use counters for calls of Navigator methods openTCPSocket, openUDPSocket Explainer: https://github.com/WICG/raw-sockets/blob/master/docs/explainer.md Bug: 1119681 Change-Id: I5570c87d73985429e0475cc9e97bea355c926176 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367253 Commit-Queue: Eric Willigers <ericwilligers@chromium.org> Reviewed-by:
Glen Robertson <glenrob@chromium.org> Cr-Commit-Position: refs/heads/master@{#802278}
-
Aaron Leventhal authored
Bug: 1091178 Change-Id: Ia6e82b1fcab8f08dbb3dff6186a8ab04e5a4f127 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2376307 Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#802277}
-
Guillaume Jenkins authored
The CloudReportingEnabled policy controls whether cloud reports are sent to the Admin Console. It is still an experimental policy on iOS. When testing the CBCM flow via experimental settings, that policy was never allowed in the list of experimental policies, so it was ignored. That prevented testing cloud reporting. This change simply adds the CloudReportingEnabled policy to the list of allowed experimental policies if a CBCM enrollment token is provided via the experimental settings. This change also clarifies comments and variable names around policy about:flags to make it easier to understand what's going on. Bug: 1122005 Change-Id: Iec6ecf7b4ef7a2a8bed60dbd82b73a474a70cd8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2377896Reviewed-by:
Mike Dougherty <michaeldo@chromium.org> Commit-Queue: Guillaume Jenkins <gujen@google.com> Cr-Commit-Position: refs/heads/master@{#802276}
-
Stepan Khapugin authored
Adds a blurred background, uses localized strings, supports dark mode. Bug: 1072408 Change-Id: I3806765e99ec6d93776bea7e932426a4cff238c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353256Reviewed-by:
Mark Cogan <marq@chromium.org> Commit-Queue: Stepan Khapugin <stkhapugin@chromium.org> Auto-Submit: Stepan Khapugin <stkhapugin@chromium.org> Cr-Commit-Position: refs/heads/master@{#802275}
-
Etienne Bergeron authored
This CL is boosting the thread priority to avoid loading the DLL at background priority. https://bugs.chromium.org/p/chromium/issues/detail?id=973868#c43 Noticed in crash/4f4d3d0215060b7e The following stackframe is the cause of the priority inversion: LoadLibraryExW [...] CDeviceMoniker::BindToObject media::VideoCaptureDeviceFactoryWin::CreateDeviceFilterDirectShow media::VideoCaptureDeviceFactoryWin::GetDevicesInfoDirectShow media::VideoCaptureDeviceFactoryWin::GetDevicesInfo media::VideoCaptureSystemImpl::GetDeviceInfosAsync video_capture::DeviceFactoryMediaToMojoAdapter::GetDeviceInfos video_capture::VirtualDeviceEnabledDeviceFactory::GetDeviceInfos bluetooth::Socket::Disconnect [...] base::internal::WorkerThread::RunWorker() base::internal::WorkerThread::RunBackgroundDedicatedCOMWorker() R=joenotcharles@chromium.org, Bug: 973868 Change-Id: I8f3d6b2cb8f94731148f827ffda4a201ebf9543e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2378395Reviewed-by:
Joe Mason <joenotcharles@chromium.org> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Commit-Queue: Etienne Bergeron <etienneb@chromium.org> Cr-Commit-Position: refs/heads/master@{#802274}
-
Himanshu Jaju authored
This is a reland of 48f89230 Original change's description: > Handle click on success notification. > > Handles action on success notification as follows: > - Copies text to clipboard > - Copies image to clipboard > - Opens downloads folder for multiple files > > Bug: 1085069 > Change-Id: Ie26712e0195a261cade102a74037611f11fa5dab > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375250 > Commit-Queue: Himanshu Jaju <himanshujaju@chromium.org> > Reviewed-by: Richard Knoll <knollr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#802213} Bug: 1085069 Change-Id: Icf6eeea97adb4aa2a03b27a53b9fd633c02115b3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2379778Reviewed-by:
Richard Knoll <knollr@chromium.org> Reviewed-by:
James Vecore <vecore@google.com> Commit-Queue: Himanshu Jaju <himanshujaju@chromium.org> Cr-Commit-Position: refs/heads/master@{#802273}
-
Ryan Hansberry authored
Change-Id: I475a14e26cf0a8ca60858b5d1388b1daad0dff1f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2380310Reviewed-by:
James Vecore <vecore@google.com> Commit-Queue: Ryan Hansberry <hansberry@chromium.org> Cr-Commit-Position: refs/heads/master@{#802272}
-
Dave Tapuska authored
Emil you will be sorely missed. Thanks for all your contributions, stories and mentoring fellow peers. Change-Id: I0b4fb622bf6038346c76cdf3c11fcb74c2474c75 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2379952 Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#802271}
-
Dirk Pranke authored
Apparently the 'chrome_sizes' step is only run on the internal official builders, and so we've only just now realized that one of my generic_wrappers changes {#799880} broke things on Windows. I didn't realize that code path was even running on Windows yet. This CL should fix it. Bug: 1122334, 816629 Change-Id: If564ac2db13402358f39849be26c050d7511b388 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2378458 Commit-Queue: Dirk Pranke <dpranke@google.com> Reviewed-by:
Haiyang Pan <hypan@google.com> Cr-Commit-Position: refs/heads/master@{#802270}
-
Klaus Weidner authored
In SurfaceControl mode on Android 11 (R), the transitions into and out of WebXR mode with DOM Overlay active were leaving unexpected stale ChromeNativeWindowSurface/ChromeChildSurface pairs in SurfaceFlinger. This change skips recreating the surface if it's transitioning from TRANSLUCENT to TRANSLUCENT where the same surface can be reused. Bug: 1122103 Change-Id: I65d2cf3b69467468824b2c03b554e94849032c4d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2378653Reviewed-by:
Khushal <khushalsagar@chromium.org> Reviewed-by:
Matthew Jones <mdjones@chromium.org> Commit-Queue: Klaus Weidner <klausw@chromium.org> Cr-Commit-Position: refs/heads/master@{#802269}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/1f48854dae26..ec3650f56ca2 2020-08-27 srisser@google.com Add getPhysicalDeviceFeatures2 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: I0ba22fe2ca4134e09cb5de865fc17644a23f8e50 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2380017Reviewed-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@{#802268}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/a3467211f5c0..ecf0d2c0f651 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 gogerald@google.com,hkamila@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: None Tbr: gogerald@google.com,hkamila@google.com Change-Id: I7cd5223c08589a42d13ad18a7d7affea95cfa16c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2380014Reviewed-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@{#802267}
-
Tom Anderson authored
This is needed after [1] changed the libwayland-client symbols file. [1] https://chromium-review.googlesource.com/c/chromium/src/+/2379674 R=msisov Change-Id: Iffada22847663b5a9ca3973d45f7a0a2c93fedd5 Bug: 1116384 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2380370 Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Commit-Queue: Maksim Sisov (GMT+3) <msisov@igalia.com> Auto-Submit: Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Maksim Sisov (GMT+3) <msisov@igalia.com> Cr-Commit-Position: refs/heads/master@{#802266}
-
Dean Michael Berris authored
This change updates the responsibilities for the performance regression sheriffs given the new automated process for triage and bisection. This removes the need to proactively poll the alerts page in the Chromperf Dashboard, and instead moves the sheriffing rotation to a reactive model handling Monorail issues. R=tdresser@chromium.org Change-Id: Icb6e58052bd1c7480b57c341438a23b560120000 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2378408 Auto-Submit: Dean Berris <dberris@chromium.org> Commit-Queue: Timothy Dresser <tdresser@chromium.org> Reviewed-by:
Timothy Dresser <tdresser@chromium.org> Cr-Commit-Position: refs/heads/master@{#802265}
-
Hongchan Choi authored
* Security Review (googler-only): https://groups.google.com/a/google.com/g/web-audio-team/c/Xlj3LL6ywPE/m/OlbhlGFLBgAJ * Platform Architecture Review: https://groups.google.com/a/chromium.org/g/platform-architecture-dev/c/sxpZizgpDFM/m/6X0jJTg9AwAJ This CL changes the threading model of AudioWorklet: 1. An AudioWorklet spawned from an AudioContext from a top-level document will run on a real-time priority thread. (RealtimeAudioWorkletThread backed by per-process singleton) 2. An AudioWorklet spawned from an AudioContext from a sub frame will run on a DISPLAY priority thread. (SemiRealtimeAudioWorkletThread backed by per-process singleton) Note that the RT thread flag can override the logic and will match the RealtimeAudioWorkletThread even for a sub frame. 3. An OfflineAudioContext will use a background priority thread for the worklet script processing. (OfflineAudioWorkletThread backed by per-process singleton) 4. In a frame, AudioWorklets with same thread type will share a single backing thread based on its RT constraint and the frame level. In other words, the maximum number of backing threads is 3. (Realtime:REALTIME_AUDIO, SemiRealtime:DISPLAY, Offline:BACKGROUND) Confirmed the repro case in 1051922 is fixed with the patch. Bug: 813825,1051992,1090245 Test: audio_worklet_thread_test.cc Change-Id: I6f5994a5114839d5a25ae99bc18474db44789bc9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353531 Commit-Queue: Hongchan Choi <hongchan@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by:
Raymond Toy <rtoy@chromium.org> Cr-Commit-Position: refs/heads/master@{#802264}
-
Rouslan Solomakhin authored
Before this patch, the secure payment confirmation UI was available only through a Chrome flag that unilaterally changed Chrome's Web Payment UI to be the secure payment confirmation dialog, regardless of which payment method the merchant requested. This patch makes the secure payment confirmation UI controller implement the existing PaymentRequestDialog interface, so it can be used interchangeably with the existing browser payment sheet. The controller also implements InitializationTask::Observer interface in order to observe when PaymentRequestState has found all payment apps on device and PaymentRequestSpec has the finalized total amount. Also in this patch: real values from PaymentRequest are displayed in the secure payment confirmation UI. Also in this patch: WebAuthn result is serialized into JSON stringified string, which is sent to the renderer process for the merchant. The byte arrays are base64-encoded into strings. After this patch, secure payment confirmation UI is used only when secure payment confirmation method was requested and it is the only payment method being requested. Bug: 1121745, 1121687, 1121689 Change-Id: I3e77f693513ef620a7c296d2744e609297703aec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2378271 Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org> Reviewed-by:
Nick Burris <nburris@chromium.org> Cr-Commit-Position: refs/heads/master@{#802263}
-
Ben Wagner authored
Move anchor search logic from ElementFragmentAnchor::TryCreate to TreeScope::FindAnchor. This changes 'FindAnchor' to take a URL fragment instead of a name and search for the anchor as was previously done in TryCreate. Moving the logic consolidates the lookup behavior which would otherwise need to be shared between all the callers of FindAnchor ElementFragmentAnchor::TryCreate AXNodeObject::InPageLinkTarget NGFragmentPainter::AddURLRectIfNeeded PrintContext::CollectLinkedDestinations ObjectPainter::AddURLRectIfNeeded The last three of which share additional logic which may need to be factored separately. Note that this also handles the special empty or "top" anchors (which have a destination at the top of the page). Tests are added for the parts of scrolling, printing, and accessibility which use FindAnchor to ensure that they work properly with codepoints outside 7 bit ASCII and the implicit "top" and "" anchors. Accessibility tests updated now that '#' is correctly an internal link. Bug: chromium:985254, chromium:1117212 AX-Relnotes: Anchors with non-ASCII characters now work as expected. AX-Relnotes: "#top" and "#" anchors link to the top of the document. Change-Id: I23830fa47f857cbc0f41f857748c8615cf5a63b2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2357250 Commit-Queue: Ben Wagner <bungeman@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Mason Freed <masonfreed@chromium.org> Reviewed-by:
David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#802262}
-
Mila Green authored
Since on macOS there is no meta installer, the flow to installing an updater is the following: 1. Chrome (or other app) is drag installed. 2. It tries to register itself with the updater. It does that by running its bundled updater, with the --register --app-id=... --version=... command. This is done over RPC, so if there is an updater on the system, it will get the call. If registration is successful, no other action is needed. 3. If no updater is present, the bundled updater will: 3.1. Install itself 3.2. "wake" itself, so that it is promoted. 3.3. Register itself for updates 3.4. Register the app (Chrome, etc.) for updates. Bug: 1109231 Change-Id: I6e3f31ffbb6eaa6334bd9caa708b3b37f883d674 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2350191 Commit-Queue: Mila Green <milagreen@chromium.org> Reviewed-by:
Joshua Pawlicki <waffles@chromium.org> Cr-Commit-Position: refs/heads/master@{#802261}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/7d194407e8b0..0c589cca4eff 2020-08-27 wolfi@chromium.org [Frametree] Add icons to links in FrameDetailsView 2020-08-27 tvanderlippe@chromium.org Typecheck bindings/DebuggerLanguagePlugins.js with TypeScript 2020-08-27 szuend@chromium.org [ts] Type-check sdk/CPUProfilerModel.js with TypeScript 2020-08-27 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS. 2020-08-27 tvanderlippe@chromium.org Typecheck services/ServiceManager.js with TypeScript 2020-08-27 changhaohan@chromium.org Add UMA for showing sidebar panes 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: chromium:1011811,chromium:1093247,chromium:1119895 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Iec721820c907d781b53acdd90d7b31225aaf599e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2379970Reviewed-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@{#802260}
-
Rouslan Solomakhin authored
Before this patch, payment credential was not being stored, so Web Payments could not invoke secure payment confirmation. This patch stores the payment credential in SQLite database. After this patch, Web Payments can invoke secure payment confirmation for the credential that is stored in the SQLite database. Bug: 1121336 Change-Id: Iffbb93a50095d961b5191b3b6c936ee052b5bf83 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375892 Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org> Reviewed-by:
Sahel Sharify <sahel@chromium.org> Cr-Commit-Position: refs/heads/master@{#802259}
-
nohe@chromium.org authored
This adds a private file api to handle copying images to the system clipboard. This is extended so when users click the copy button in the Chrome OS files app, the file is copied to the system clipboard and can then be pasted to different types of applications. This change will present a similar solution to that of copying an image in the browser to the system clipboard via the right click > copy image. This feature is currently experimental and will be added behind a flag in the frontend. Bug: 827333 Change-Id: I85b98b4f35151d0146a0c79b93976822c663651e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317029 Commit-Queue: Alexander Nohe <nohe@chromium.org> Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#802258}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/a8327d441549..3d3b531b64fa 2020-08-27 jonaso@webrtc.org Add WebRTC-IceFieldTrial send_ping_on_selected_ice_controlling 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/+doc/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: Ic1e6f8ba1445628fecea287d0da6d9078b622906 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2380013Reviewed-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@{#802257}
-
Benoit Lize authored
It is only used to get an estimate of the content area size. Move this to TabUtils, delete the rest. Change-Id: I97cb80556a318730d4bd3a0651eecb824b755614 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368358Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Commit-Queue: Benoit L <lizeb@chromium.org> Cr-Commit-Position: refs/heads/master@{#802256}
-
Peter Kasting authored
* Sets dialog margins correctly. * Sets body text context correctly. * Replaces Grid with Box since no one likes GridLayout; this fixes bug 1119305 as a side effect since BoxLayout lays out StyledLabel at times/widths more like what it wants. * Uses "v* = AddChildView(std::make_unique<V>(...));" idiom. * Lays out the "checkbox" contents more like a real checkbox: with the border around the outside of everything. This removes the need for a label vertical alignment hack and corrects the excessive spacing between checkbox and label. * Makes Checkbox overrides of public methods public; this was necessary anyway to do the above. Bug: 1119305 Change-Id: Ia7afa6ffeaeeab9ad407acbacaacc937f1fb842d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2377066 Commit-Queue: Peter Boström <pbos@chromium.org> Reviewed-by:
Peter Boström <pbos@chromium.org> Auto-Submit: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#802255}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/09ec5ae5729e..b90423b45298 2020-08-27 chrome-bot@chromium.org Update config settings by config-updater. 2020-08-26 bhanumaiya@google.com zork: add factory branch builder 2020-08-26 bhanumaiya@google.com Fix lint issues in config/chromeos_config.py 2020-08-26 vapier@chromium.org cros lint: disable old-division with --py3 2020-08-26 ahassani@chromium.org Revert "cros_update: Delete it." 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: Iac4f56a59ec9f1654feece31a2705a2d8dfe229a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2380016Reviewed-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@{#802254}
-