- 31 Mar, 2020 40 commits
-
-
Scott Violet authored
BUG=1066263 TEST=none, doc only change Change-Id: Id0ea73c1588601cf9fd29f68c62b14a3d28c75fd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2128977 Commit-Queue: Scott Violet <sky@chromium.org> Commit-Queue: Bo <boliu@chromium.org> Auto-Submit: Scott Violet <sky@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#754950}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/65d3ad953957..469046c09657 git log 65d3ad953957..469046c09657 --date=short --first-parent --format='%ad %ae %s' 2020-03-31 bsalomon@google.com Revert "Revert "Remove GrCaps::isFormatTexturableAndUploadable"" Created with: gclient setdep -r src/third_party/skia@469046c09657 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 Bug: None Tbr: michaelludwig@google.com Change-Id: I68c6b38e919677269e1beee5973faa8afa09dd97 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2129784Reviewed-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@{#754949}
-
Mohsen Izadi authored
Existing LatencyInfo-based event latency metrics measure the time between event creation timestamp and gpu-swap-end. To be able to verify new event latency metrics against them, we need add similar metrics for new EventLatency metrics. This is only added for scroll events as LatencyInfo-based metrics only exist for scroll events. Bug: 1057193 Change-Id: I73169330a4ffb0e4b5fd9506960a5737624867bc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2129215Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Mohsen Izadi <mohsen@chromium.org> Cr-Commit-Position: refs/heads/master@{#754948}
-
Gabriel Charette authored
R=altimin@chromium.org Bug: 1002654 Change-Id: Iaa1c7911326bb0280766b2df045f5401b1f5110c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1849127 Commit-Queue: Gabriel Charette <gab@chromium.org> Auto-Submit: Gabriel Charette <gab@chromium.org> Reviewed-by:
Alexander Timin <altimin@chromium.org> Cr-Commit-Position: refs/heads/master@{#754947}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/d2aa8f97f109..4b425aeef9cd git log d2aa8f97f109..4b425aeef9cd --date=short --first-parent --format='%ad %ae %s' 2020-03-31 peah@webrtc.org AEC3: Correct peak index at filter size reductions Created with: gclient setdep -r src/third_party/webrtc@4b425aeef9cd 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: chromium:1061933 Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I0105a85497772230ef18b6c440c1ea08eb78af4d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2129779Reviewed-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@{#754946}
-
Anatoliy Potapchuk authored
This CL updates the app launch screen, additionally surfacing app origin. This help users be aware of the app that is being launched. Bug: 1046260 Change-Id: Ibc525ddb50ba233dd6da1986a228e8b216719c5d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2127686 Commit-Queue: Anatoliy Potapchuk <apotapchuk@chromium.org> Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/master@{#754945}
-
Becca Hughes authored
For Media History we have a sessions table that records media sessions that we can resume. At the moment we are only interested in video with audio. This adds a MediaAudioVideoState enum that contains data about whether a media session is audio only or has both audio and video. For web sessions, this will follow the routed frame since that is where the metadata we are using for media history is coming from. BUG=1041662 Change-Id: I75d93e339de8e221d8798ee2508aacda0f120b11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036772Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Commit-Queue: Becca Hughes <beccahughes@chromium.org> Cr-Commit-Position: refs/heads/master@{#754944}
-
Benoit Lize authored
Blink doesn't have direct access to the filesystem, by design of its sandbox. As a consequence, all disk accesses must be brokered by a privileged process, typically the browser. However, there are cases where file access should be managed by the renderer. For instance, when synchronous access is required from the renderer process. To that end, we add a DiskDataAllocator, handling read/writes to disk that are fully managed from the renderer process, and multiplexed onto a single file descriptor. The single file descriptor model is selected to avoid bumping into file descriptor limits, and to reduce performance and space overhead in cases where many small pieces of data are written. The intended client for this allocator is ParkableString, see the linked bug for details. Concretely: 1. The browser process creates a writable file, and passes it to the renderer over mojo 2. The renderer can service reads and writes using this single file descriptor. It is the browser process' responsibility to make sure the file is properly deleted once the renderer dies. From the client perspective, reading and writing are synchronous operations. However writing must be done from a single background sequence. Space allocation in the file is done using a "exact, then worst" fit policy. This policy may be adjusted in the future. Bug: 1029320 Change-Id: Ie65bfd82dc0e702b4427d4e69858ab2ae4f4c06b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2107538 Commit-Queue: Benoit L <lizeb@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#754943}
-
Chris Dalton authored
Change-Id: I7e655df88153484783b2df5123054dc751307b59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2128453Reviewed-by:
Shrek Shao <shrekshao@google.com> Reviewed-by:
Jonathan Backer <backer@chromium.org> Commit-Queue: Chris Dalton <csmartdalton@chromium.org> Cr-Commit-Position: refs/heads/master@{#754942}
-
Avi Drissman authored
System-provided objects that implement MTLDevice should derive from NSObject. It would be silly if they didn't, given that the MTLDevice protocol inherits from the NSObject protocol. However, if for some reason this turns out to no longer be true in some future macOS, crash early so that it's obvious what's wrong. Bug: 1065146 Tbr: ccameron@chromium.org Change-Id: I9c59d57c9a4e18ad1b6860971bfb27a731eb9140 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2129031Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Mark Mentovai <mark@chromium.org> Commit-Queue: Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#754941}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/2dbeb5da18b1..68cc95ec121c git log 2dbeb5da18b1..68cc95ec121c --date=short --first-parent --format='%ad %ae %s' 2020-03-31 tvanderlippe@chromium.org Remove support for front_end fallback in unittests Created with: gclient setdep -r src/third_party/devtools-frontend/src@68cc95ec121c 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: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I7b3311d2dd3bf70e83b397bd24800ce57f36f46b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2129846Reviewed-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@{#754940}
-
Hailey Wang authored
Track PageNodes that are in to_load/initiated_load/loading states. Used to restrict maximum simultaneous load in future cl. Bug: 1059341 Change-Id: I76f02d2620fd2fb22c34358453750b20503bc921 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2118177 Commit-Queue: Hailey Wang <haileywang@google.com> Reviewed-by:
François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#754939}
-
Devlin Cronin authored
It was never used. Bug: None Change-Id: Ice77e73468d18ee795c9cf7152a88c3e27bf825e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2129048Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Devlin <rdevlin.cronin@chromium.org> Cr-Commit-Position: refs/heads/master@{#754938}
-
Dominique Fauteux-Chapleau authored
TBR=tiborg@chromium.org Bug: 1066459 Change-Id: I02debf69279f12752a92c16c98b5b3ce57a36726 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2128712Reviewed-by:
Dominique Fauteux-Chapleau <domfc@chromium.org> Commit-Queue: Dominique Fauteux-Chapleau <domfc@chromium.org> Cr-Commit-Position: refs/heads/master@{#754937}
-
David Tseng authored
- fixes one regression where the form controls list shortcut command no longer works - found root cause of panel test flakes. The panel does not immediately get focus, especially on slower builds, so we need to wait for focus prior to performing panel construction and menu bar/menu item focusing - added additional test as well as fixing / rebaselining current tests - simplified logic that sets the active item for node menus on ChromeVox's current range (see test) - simplify places where we set active item; caused a lot of focus events to be sent unnecessarily Fixed: 990229, 795840 RELNOTES: makes Search+Ctrl+F work again in ChromeVox (show form controls list) Change-Id: I7ed10a70b524da48b4d55f2a4e086dae09a9629d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124246 Commit-Queue: David Tseng <dtseng@chromium.org> Reviewed-by:
Akihiro Ota <akihiroota@chromium.org> Cr-Commit-Position: refs/heads/master@{#754936}
-
Sebastien Lalancette authored
Added code to add the generate QR code activity to the activity service controller behind its feature flag. Also added a simple unit test. Bug: 1064990 Change-Id: Ib386f3bb8fa85d27094197b2febbc1a4c1d66a5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2127891 Commit-Queue: Sebastien Lalancette <seblalancette@chromium.org> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#754935}
-
Alex Ilin authored
At the end of the remote consent flow, Gaia returns Chrome a gaia id of an account chosen by the user. This change makes Chrome reuse this account for the next getAuthToken() calls for the same extension. For now, accounts are stored in memory with a TODO to migrate them to the user preferences. Bug: 1026237 Change-Id: Ibe52424b7131fbe44324ecb7b1a0e54d04cdf747 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2119520 Commit-Queue: Alex Ilin <alexilin@chromium.org> Reviewed-by:
David Roger <droger@chromium.org> Cr-Commit-Position: refs/heads/master@{#754934}
-
Ulan Degenbaev authored
This reverts commit 2933aeba. Reason for revert: try enabling issue to see if the bug is still there. Original change's description: > [go/perfbot-sheriff] Disable v8 cnn story. > > NOTRY=true > R=ulan@chromium.org > TBR=ulan@chromium.org > > Bug: 1062438 > Change-Id: If81aed43750d93d5c61b02e22c8e40b9f2acec81 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2108060 > Reviewed-by: Caleb Rouleau <crouleau@chromium.org> > Commit-Queue: Caleb Rouleau <crouleau@chromium.org> > Cr-Commit-Position: refs/heads/master@{#751165} TBR=ulan@chromium.org,crouleau@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1062438 Change-Id: I6e6d19145fc535393499f2c54087f9a46a74cc6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2128512Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#754933}
-
Sadrul Habib Chowdhury authored
CompositorFrameReportingController::stage_history_ is never used, so it is removed. BUG=none R=behdadb@chromium.org Change-Id: I27a40a306c7a55d871900ec4fbcc64196ffbc454 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2129236 Auto-Submit: Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Behdad Bakhshinategh <behdadb@chromium.org> Reviewed-by:
Behdad Bakhshinategh <behdadb@chromium.org> Cr-Commit-Position: refs/heads/master@{#754932}
-
Mark Cogan authored
Renames AppUrlLoadingService to SceneURLLoadingService. Makes SceneController, which was already the owner of the service, also responsible for connecting the scene service to the general url loading browser agent. This means that browser coordinator no longer needs to be passed the app loader to install, and likewise the BVWrangler no longer needs to pass it into the browser coordinator. Since the SceneController configures itself as the scene loading service delegate, it can remove its public conformation to the delegate protocol. Bug: 1046373 Change-Id: I6c5f6e6a3e69d2bd5968b1021b5b556bdb8bf874 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2127366 Commit-Queue: Mark Cogan <marq@chromium.org> Reviewed-by:
Stepan Khapugin <stkhapugin@chromium.org> Cr-Commit-Position: refs/heads/master@{#754931}
-
Theresa Wellington authored
BUG=1065043 TBR=mdjones@chromium.org Change-Id: I9121719064ed24a3a0c66623f6a29f06e4f808e9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2129782Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Matthew Jones <mdjones@chromium.org> Commit-Queue: Theresa <twellington@chromium.org> Cr-Commit-Position: refs/heads/master@{#754930}
-
Kevin Ellis authored
Explicitly setting the keyframes via the KeyframeEffect API blocks subsequent updates via CSS keyframe rules. Bug: 1058731 Change-Id: Ie485cb908ef5a436df8b408250bbe50a61f65ecc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2122236Reviewed-by:
Robert Flack <flackr@chromium.org> Commit-Queue: Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/master@{#754929}
-
Stepan Khapugin authored
Creates an observer protocol for AppState and makes MainContorller an observer. Creates an observer method that is called when the first scene is activated, to drive one-time UI-related init. Makes MC run its one-time init from tihs callback. This prevents a crash where on backgrounding and reopening, the one time startup is performed again, leading to DCHECKs. Bug: 1045658 Change-Id: I608975e8690e9c874a1913f7458560a54429d611 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2128509 Commit-Queue: Stepan Khapugin <stkhapugin@chromium.org> Reviewed-by:
Mark Cogan <marq@chromium.org> Cr-Commit-Position: refs/heads/master@{#754928}
-
Rouslan Solomakhin authored
Before this patch, creating a Payment Request for "https://play.google.com/billing" on a device where an Android payment app with that payment method is installed would cause manifest lookups at https://play.google.com/billing. This patch removes "https://play.google.com/billing" from the list of payment methods for which Android payment apps should be looked up. After this patch, Chrome does not attempt to download manifests for the Google Play Billing payment method when a locally installed Android payment app provides support for it. Bug: 1062376 Change-Id: Ibfb2ae9d189aada2161552f2e80e0ed2be5d84b1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2125873 Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org> Reviewed-by:
Danyao Wang <danyao@chromium.org> Reviewed-by:
Liquan (Max) Gu <maxlg@chromium.org> Cr-Commit-Position: refs/heads/master@{#754927}
-
Gang Wu authored
This CL update ReadImage in clipboard to be asynchronous for all platform. This CL also implement getImage from android clipboard. Bug:1055924 Change-Id: Id969665aa612138ae96f9e7445cddc011ccc40f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2071287Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Darwin Huang <huangdarwin@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Commit-Queue: Gang Wu <gangwu@chromium.org> Cr-Commit-Position: refs/heads/master@{#754926}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/bb0867806ceb..e0bc6f033ff5 Created with: gclient setdep -r src-internal@e0bc6f033ff5 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 Bug: None Tbr: jbudorick@google.com Change-Id: I82b9bd598d4a3d00abdb7512f26dd6e34cdc379c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2129772Reviewed-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@{#754925}
-
Owen Min authored
The feature is rolled out 100% in M80 and enabled by default now. - Remove the feature and flag. - No longer install Cloud reporting extension. - In browser reporting is always used for enterprise reporting. With this CL, CloudReportingPolicy will no longer force-install the cloud reporting extension and report will be generated fully by Chrome. Any existed extension that is installed by this policy will be removed from the client automatically. User won't be able to switch back to the old behavior anymore. Bug: 1063083 Change-Id: I8238d742b85dfb5670f00120f6bbb587c9326a0d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2125035Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Reviewed-by:
Karan Bhatia <karandeepb@chromium.org> Commit-Queue: Owen Min <zmin@chromium.org> Cr-Commit-Position: refs/heads/master@{#754924}
-
Clemens Arbesser authored
Bug: b/152300352 Change-Id: Idf29c4edce98025f395a91fed76598335065970e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124607 Commit-Queue: Clemens Arbesser <arbesser@google.com> Reviewed-by:
Marian Fechete <marianfe@google.com> Cr-Commit-Position: refs/heads/master@{#754923}
-
Robert Ogden authored
Added test. Bug: 1042829 Change-Id: I51be6e4286a317dd612e91400895988302fe2bea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2125951 Commit-Queue: Robert Ogden <robertogden@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Cr-Commit-Position: refs/heads/master@{#754922}
-
Pavol Marko authored
If a key name has been configured in the TpmChallengeKey flow, use it for all calls. Bug: 1045895 Test: unit_tests --gtest_filter=*TpmChallenge* Change-Id: Ifccdf18eb692f1f635deeb81d4e59515b4e1d238 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2116195Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Reviewed-by:
Michael Ershov <miersh@google.com> Commit-Queue: Pavol Marko <pmarko@chromium.org> Cr-Commit-Position: refs/heads/master@{#754921}
-
Matt Jones authored
This patch attempts to deflake two of the TabsTest tests by ensuring they are on pages that have a toolbar to start with. A utility has been added to generate URLs for pages that only display a solid color to make visual debugging easier. This patch also asserts the tab count for the tests (if opening one failed, we wouldn't know about it until much later). Bug: 813584 Change-Id: Ica3bba33ac95cc16b24dde4e1d193c4b01e8b537 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2128790Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Matthew Jones <mdjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#754920}
-
danakj authored
We don't run web tests on Android anymore. R=fmalita@chromium.org, nasko@chromium.org Bug: 866140, 567947 Change-Id: I1bd93214f981bc7d544af3e6affefef4e89b83f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2122454 Commit-Queue: danakj <danakj@chromium.org> Reviewed-by:
Florin Malita <fmalita@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#754919}
-
danakj authored
content/shell/renderer/ can see test_runner::WebTestInterfaces, so it can also see test_runner::TestInterfaces. The former is just a shallow wrapper around the latter, so it is not needed at all. R=avi@chromium.org Bug: 866140 Change-Id: Ic9ad15d27aae6d0293e23cdfb007e9511ff296d3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2128450Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#754918}
-
Bo Liu authored
Read system setting on Android. Set to false on other platforms. Then check this state when the in fragment.onStart and send updates if there are changes. This matches chrome behavior. Bug: 1052496 Change-Id: Ib0d42949c0d6b8f57cd10f4781f0908ca3b34ec0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2127896Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#754917}
-
Dominique Fauteux-Chapleau authored
TBR=ellyjones@chromium.org Bug: 1066456 Change-Id: I362ca1266a31e57122402bd4d620db49a60c8e01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2128975Reviewed-by:
Dominique Fauteux-Chapleau <domfc@chromium.org> Commit-Queue: Dominique Fauteux-Chapleau <domfc@chromium.org> Cr-Commit-Position: refs/heads/master@{#754916}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/a65fa055496b..bc44331c334d git log a65fa055496b..bc44331c334d --date=short --first-parent --format='%ad %ae %s' 2020-03-31 rsavitski@google.com Merge "Ban PERFETTO_EINTR(close(...)), which is actively incorrect" Created with: gclient setdep -r src/third_party/perfetto@bc44331c334d 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/+/master/autoroll/README.md Bug: None Tbr: perfetto-bugs@google.com Change-Id: I921e38a720231f8bafc7fac44c6fb6447621cbeb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2129769Reviewed-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@{#754915}
-
Maksim Sisov authored
This CL enables more tests as was discussed with rjkroege@. Bug: 1029240 Change-Id: I96afe797dcf841e0012bd07485c13e62e642303d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2127027 Commit-Queue: Maksim Sisov <msisov@igalia.com> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#754914}
-
Hongchan Choi authored
This CL adds trace event in the following AudioNodes based on the popularity: - GaindNode - AudioBufferSourceNode - PannerNode - BiquadFilterNode It also adds trace event below to get the detailed tracing data from some problem areas. - AudioWorkletNode - MediaStreamAudioSourceNode - MediaStreamAudioDestinationNode Bug: 1065982 Change-Id: I0758786aa418ec3dc992333012f0da0f8867f636 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2127731Reviewed-by:
Raymond Toy <rtoy@chromium.org> Reviewed-by:
Sami Kyöstilä <skyostil@chromium.org> Commit-Queue: Hongchan Choi <hongchan@chromium.org> Cr-Commit-Position: refs/heads/master@{#754913}
-
Jeremie Boulic authored
A user in guest mode only has access to temporary storage, the downloaded files and other data coming from a guest user are stored in virtual memory. This is inconsistent with the way the "System" row is calculated, which takes into account data stored in a persistent storage space. We therefore hide the system row when the user is in guest mode. browser_tests --gtest_filter="*OSSettingsDevicePageTest.StorageTest" Test: Bug: 1061401 Change-Id: I5b7caafc9698f2853aacae3b043ea7ca6294387e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124276Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Commit-Queue: Jeremie Boulic <jboulic@chromium.org> Cr-Commit-Position: refs/heads/master@{#754912}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/d7f02588fc51..2dbeb5da18b1 git log d7f02588fc51..2dbeb5da18b1 --date=short --first-parent --format='%ad %ae %s' 2020-03-31 kimanh@chromium.org Update CDP and add string to reflect stack scope in scope view Created with: gclient setdep -r src/third_party/devtools-frontend/src@2dbeb5da18b1 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:1043034 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Ieb01d274453f09c79f878f360559ab7129005ca4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2129581Reviewed-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@{#754911}
-