- 13 Aug, 2020 40 commits
-
-
Himanshu Jaju authored
Implements the key verification module that to verify remote device before requesting introduction and beginning the transfer flow. Bug: 1085068 Change-Id: I4bb75dce474042ef43ca86199db3456d63406874 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346325 Commit-Queue: Himanshu Jaju <himanshujaju@chromium.org> Reviewed-by:
Alex Chau <alexchau@chromium.org> Cr-Commit-Position: refs/heads/master@{#797868}
-
Zach Trudo authored
SharedQueue was missing Swap from the possible queue commands. Added it. Bug: chromium:1078512 Change-Id: I507027bf3d77eebe0369050cbf46f58a088df03f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353404Reviewed-by:
Leonid Baraz <lbaraz@chromium.org> Commit-Queue: Zach Trudo <zatrudo@google.com> Cr-Commit-Position: refs/heads/master@{#797867}
-
Dominique Fauteux-Chapleau authored
Bug: 1100902 Change-Id: Ibf7537f2ec2084a3e4a03c33ab4c45ad5835e046 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346914Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Dominique Fauteux-Chapleau <domfc@chromium.org> Cr-Commit-Position: refs/heads/master@{#797866}
-
Chris Hamilton authored
This moves the implementation of RendererResourceCoordinator to controller, leaving behind only the interface definition and singleton accessor in platform. Change-Id: Ibdf23280e53b48df897ec341d27fe366efb04f5d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354534 Commit-Queue: Chris Hamilton <chrisha@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Joe Mason <joenotcharles@chromium.org> Cr-Commit-Position: refs/heads/master@{#797865}
-
Annie Sullivan authored
Follow up to https://chromium-review.googlesource.com/c/chromium/src/+/2348694 Bug: 1114793 Change-Id: I869e238afadd01268456b783da8a848332c3418b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354495Reviewed-by:
Philip Rogers <pdr@chromium.org> Reviewed-by:
Nicolás Peña Moreno <npm@chromium.org> Commit-Queue: Annie Sullivan <sullivan@chromium.org> Cr-Commit-Position: refs/heads/master@{#797864}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/2b1c0b0e92e7..13f3340173aa 2020-08-13 cwallez@chromium.org Remove wgpu::Buffer::SetSubData 2020-08-13 cwallez@chromium.org Remove deprecated array layer descriptor members 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 cwallez@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: cwallez@google.com Change-Id: Iaa1710d458cd6cd5552c22a2afe81bd44de88d7b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354806Reviewed-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@{#797863}
-
Mike Jackson authored
Ensure that we log the winning display mode from the manifest accounting for display_override. To test the change use: chrome --enable-features=WebAppManifestDisplayOverride Example websites: https://mwjacksonmsft.github.io/pwa/display-override-custom/index.html (display == browser, display_override == [standard]) Image of chrome://histograms https://imgur.com/a/aVzadhf Explainer: https://github.com/WICG/display-override/blob/master/explainer.m Design document: https://docs.google.com/document/d/1hEmbGVHMN38q1YTaaGccQ-Y5CHr7xIURYPRWXTuvZLo/edit?usp=sharing I2P: https://groups.google.com/a/chromium.org/d/topic/blink-dev/WvIeZT8uSzw/discussion Bug: 1109520 Change-Id: Ie401fd770eae262c9ad6d7e76e3d7e21d6a285c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354531Reviewed-by:
Daniel Murphy <dmurph@chromium.org> Commit-Queue: Mike Jackson <mjackson@microsoft.com> Cr-Commit-Position: refs/heads/master@{#797862}
-
Chris Palmer authored
https://chromium.googlesource.com/linux-syscall-support.git/+log/f70e2f1641e2..29f7c7e018f4 $ git log f70e2f164..29f7c7e01 --date=short --no-merges --format='%ad %ae %s' 2020-08-12 palmer Add support for `getrandom`. 2020-05-21 palmer Revert "Add support for `getrandom`." 2020-05-20 palmer Add support for `getrandom`. 2020-04-15 jperaza Don't clobber esp 2020-03-10 mforney Avoid conflict with getdents64 defined by libc 2019-01-26 vapier futex: change to 6 args Created with: roll-dep src/third_party/lss Bug: linux-syscall-support:31, chromium:995996 Change-Id: I347f10acab9e1c0d9e6570c79afb09f8ac292c0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354678Reviewed-by:
Mike Frysinger <vapier@chromium.org> Commit-Queue: Chris Palmer <palmer@chromium.org> Cr-Commit-Position: refs/heads/master@{#797861}
-
Gavin Williams authored
This changes adds metrics to record the success rate of printer status queries. This metric coincides with the addition of printer availability icons to the Print Preview destination dropdown (go/printer-status-design-doc). Bug: 1059607 Change-Id: Ia69ecdd6616a4efaf60b150df4b00838173648a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2350120 Commit-Queue: Gavin Williams <gavinwill@chromium.org> Reviewed-by:
Zentaro Kavanagh <zentaro@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Bailey Berro <baileyberro@chromium.org> Cr-Commit-Position: refs/heads/master@{#797860}
-
Ankit Kumar 🌪️ authored
The flag guards PDF highlight accessibility. The flag has been enabled by default since M84. Bug: 1008775 Change-Id: I35e2b15378319914277515d6f1a3c6a7b5eae4f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352966Reviewed-by:
🌪 ️ <ankk@microsoft.com> Cr-Commit-Position: refs/heads/master@{#797859} -
Sean Topping authored
We prefer to eagerly delete all expiring CastWebViews, to prevent UAF errors if a CastWebView is attempting to use deleted browser objects very late in the browser lifecycle. Bug: internal b/150630037 Test: Build/run cast_shell Change-Id: I9b301c7e76157bb60176dca2588f4bfdff0545c0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2295937Reviewed-by:
Yuchen Liu <yucliu@chromium.org> Commit-Queue: Sean Topping <seantopping@chromium.org> Cr-Commit-Position: refs/heads/master@{#797858}
-
Toni Barzic authored
BUG=1114825 Change-Id: I6ea30ae392c10ecba2cb5d265829ddfe07f30b72 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352527Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Toni Baržić <tbarzic@chromium.org> Cr-Commit-Position: refs/heads/master@{#797857}
-
Carlos IL authored
Currently a new warning is shown every time a character is typed, which results in a flashing warning when typing. This CL makes it so we consider typing as dismissing the warning and no longer show it again. Bug: 1106542 Change-Id: Iac0aa33bd8e063f27b0aca7ff36cd5bdeef7400d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352215 Commit-Queue: Carlos IL <carlosil@chromium.org> Reviewed-by:
Dominic Battré <battre@chromium.org> Cr-Commit-Position: refs/heads/master@{#797856}
-
Mehrdad Hessar authored
This changes enables us to set number of threads used by TFLite predictor and measure performance at various scenarios. Bug: 1115689 Change-Id: Ib5b0a1315fb426851e0b8d54f6e43128e3303877 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352213Reviewed-by:
David Roger <droger@chromium.org> Reviewed-by:
Michael Crouse <mcrouse@chromium.org> Reviewed-by:
Ryan Sturm <ryansturm@chromium.org> Commit-Queue: Mehrdad Hessar <mehrdadh@google.com> Cr-Commit-Position: refs/heads/master@{#797855}
-
Sean McAllister authored
Currently, ChromeOS defines the OS_LINUX directive as well as OS_CHROMEOS. We're working to separate these two, so we're making the fact that OS_LINUX == OS_LINUX || OS_CHROMEOS explicit. Bug: 1110266 Change-Id: Ic9db5ec66ce83df62c1b5eecfca1ceadd8c8766c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352032Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Sean McAllister <smcallis@google.com> Cr-Commit-Position: refs/heads/master@{#797854}
-
Taylor Bergquist authored
This is a reland of b6c0ca2a The only change is a line in tab_scrubber_browsertest.cc that ensures that any invalid layout are laid out after modifying the tabstrip. Original change's description: > Tab strip only occupies the space needed for its tabs. > > Bug: 1093972 > Change-Id: I0ca6cc1a7dad9240b85745fefb39ac4f52eb9355 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2300993 > Commit-Queue: Taylor Bergquist <tbergquist@chromium.org> > Reviewed-by: Connie Wan <connily@chromium.org> > Cr-Commit-Position: refs/heads/master@{#793270} Bug: 1093972 Change-Id: I4ded68fde336b14b38ad862cd63118ebc9fc7a72 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2336296 Commit-Queue: Taylor Bergquist <tbergquist@chromium.org> Reviewed-by:
Connie Wan <connily@chromium.org> Reviewed-by:
Peter Boström <pbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#797853}
-
Hai Bi authored
Using SyncPtr causes a deadlock since the caller is waiting for the call to return, while the reboot component may not return right away, so caller is blocked and cannot process any notification during the time. Changed to AdminPtr to make caller still active during reboot. Bug: b/163045578 Test: local test and updated unit test Change-Id: Icf2644191ef5113b8ff9f7de73feb0765b4ea2e8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2350741 Auto-Submit: Hai Bi <bihai@google.com> Commit-Queue: Hai Bi <bihai@google.com> Reviewed-by:
Michael Spang <spang@chromium.org> Cr-Commit-Position: refs/heads/master@{#797852}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1597319582-be9645d468b25404b91084b442e1381733e63a51.profdata to chrome-mac-master-1597341503-4f5bca114f9d97d0c5a366353ca44da70cbc454a.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-mac-chromium Please CC sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@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: chrome/try:mac-chrome Tbr: sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@google.com Change-Id: I92773f74c51a79b2ee14bd61c3e20325973f1955 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354578Reviewed-by:
-
Liquan (Max) Gu authored
Change: * Rename teardown() to close(). "Teardown" was named because CPRImpl used to implement PR#close. Now that MojoPaymentRequestGateKeeper has taken over the PR#close implementation, CPRImpl can use "close" now. CPRImpl#close is consistent in meaning with PaymentRequestImpl#close. * Move BrowserPaymentRequestFactory from CPRImpl to BrowserPaymentRequest, and it get renamed as Factory because now it's in BrowserPaymentRequest's context. Bug: 1102522 Change-Id: I47926eaa0a394d0698c1704823ba428e9abe4766 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2348542 Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org> Reviewed-by:
Sahel Sharify <sahel@chromium.org> Cr-Commit-Position: refs/heads/master@{#797850}
-
Lexi Stavrakos authored
This change implements the subscribe mechanism for the QuotaChange event. Listeners are plumbed through to a new class, QuotaChangeDispatcher, which is owned by QuotaContext. Events are dispatched with a randomized delay; by adding noise, we can prevent bad actors from using this event as a signal to correlate users across profiles/origins or to identify the size of cross-origin resources. Listeners are organized by origin, so that all events for a single origin will be dispatched with the same randomized delay. Bug: 1088004 Change-Id: Ie2513f127eeedf9422f5bb463f2dd515dfa90bea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2270667 Commit-Queue: Lexi Stavrakos <astavrakos@google.com> Reviewed-by:
Jarryd Goodman <jarrydg@chromium.org> Reviewed-by:
Matthew Denton <mpdenton@chromium.org> Reviewed-by:
Darwin Huang <huangdarwin@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#797849}
-
Jao-ke Chin-Lee authored
Add utilities to help handle initialization and teardown of VA objects. Users of VaapiDevice may still manipulate the VA objects directly with libva calls. BUG=crbug:1062407 Change-Id: Id5f5233d1476f1abe006f04e3ad54fc6fb9b2486 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2296871 Commit-Queue: Jao-ke Chin-Lee <jchinlee@chromium.org> Reviewed-by:
Andres Calderon Jaramillo <andrescj@chromium.org> Reviewed-by:
Miguel Casas <mcasas@chromium.org> Cr-Commit-Position: refs/heads/master@{#797848}
-
Mohamed Heikal authored
If the update_android_aar_prebuilts gn arg is set, all info files are updated. However, some info files could actually not be part of the repo but instead be pulled in via cipd along with the aar itself. This cl adds a gn template flag to disable updating info files for android_aar_prebuilt targets that specify it. Change-Id: I5b82b8e614ab989936834a1b270c0d97bba2da3f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353355 Commit-Queue: Mohamed Heikal <mheikal@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#797847}
-
Eric Orth authored
Use the tracking in DnsUdpTracker to detect situations of DNS ID mismatches or port reuse. Bug: 1093361 Change-Id: I67a339a8ea6f6c34d5626f5587324f9dfb6cbc4d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2340677 Commit-Queue: Eric Orth <ericorth@chromium.org> Reviewed-by:
Dan McArdle <dmcardle@chromium.org> Cr-Commit-Position: refs/heads/master@{#797846}
-
Chong Gu authored
Bug: 1105308,1096746 Change-Id: Ie02e83fea75a075441b66cd3c6ac7f2f812e74e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354420Reviewed-by:
Brian Sheedy <bsheedy@chromium.org> Commit-Queue: Chong Gu <chonggu@google.com> Cr-Commit-Position: refs/heads/master@{#797845}
-
chromium-autoroll authored
Roll ChromeOS Broadwell AFDO profile from 86-4183.48-1597052523-benchmark-86.0.4229.0-r1 to 86-4183.48-1597052523-benchmark-86.0.4231.0-r1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/cros-afdo-broadwell-chromium Please CC c-compiler-chrome@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 Tbr: c-compiler-chrome@google.com Change-Id: I764a3a194d8d0782833c2e74083ee9827aec5b15 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354895Reviewed-by:
-
Chong Gu authored
Add instructions for when access to kvm is denied. Change-Id: Ie3d4b5f8a172212bdda1177b04ea80076cbe5588 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2347165 Commit-Queue: Chong Gu <chonggu@google.com> Reviewed-by:
Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#797843}
-
Jonah Chin authored
ClusterFuzz found an issue in RasterDecoderImpl::DoReadbackImagePixelsINTERNAL. When |row_bytes| is very large, SkImageInfo::computeByteSize() can return a 64bit integer larger than UINT32_MAX. Since GetSharedMemoryAs() takes a 32bit integer for |size|, the int is truncated, resulting in an incorrect value. This change ensures that the result of computeByteSize() is < UINT32_MAX. This change also addresses the same potential case in RasterDecoderImpl::DoWritePixelsINTERNAL. Bug: 1114500 Change-Id: I5cd3acfaac788e97353e0da866b63f694e326e2a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353402Reviewed-by:
Khushal <khushalsagar@chromium.org> Commit-Queue: Jonah Chin <jochin@microsoft.com> Cr-Commit-Position: refs/heads/master@{#797842}
-
Sunny Sachanandani authored
SharedImageBacking attributes its allocation to the MemoryTypeTracker of its first SharedImageRepresentation which is considered its owning ref. When the owning ref changes, the backing will switch the allocation to the new owning ref's tracker. This can happen on a different thread than the one the representation was created on, and in general calling the underlying MemoryTracker is not thread safe e.g. dereferencing the peak memory monitor's WeakPtr on a different thread. This issue was discovered while testing the DrDC prototype which makes the display's gpu work run on the viz thread instead of the gpu main thread. This CL fixes the above problem by making MemoryTypeTracker forward its calls to its original sequence (and thus thread). If a sequenced task runner isn't set e.g. on the render thread on Android Webview, then the calls are made synchronously. Bug: 1114888 Change-Id: I6833139c96de3824f450b09333f755560dff62c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2350398 Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org> Reviewed-by:
vikas soni <vikassoni@chromium.org> Reviewed-by:
Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/master@{#797841}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/e1360ddcec9e..78d7b4b8250e If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-trace-processor-linux-chromium 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 Tbr: perfetto-bugs@google.com Change-Id: I542a2ead0b348d8beb9a6667bf0d20bbb92cddb8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354606Reviewed-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/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/+doc/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: Ib80e49108602c8bbfd4683a709cc1f80273f46d7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354482Reviewed-by:
-
Brian Sheedy authored
Fixes run_performance_tests.py causing the merge script to blow up in cases where a gtest-based perf test is run on multiple shards. This was caused by the script outputting a summary to JSON instead of per-test results, which caused the merge script to try to merge the identically named tests. This is worked around by appending the shard number to the end of the name, but a proper fix where all test results are reported should still be implemented. Bug: 1115658 Change-Id: I55aa3d6c2ce2a4ae681fdcc2338e5016ec478866 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2351386 Auto-Submit: Brian Sheedy <bsheedy@chromium.org> Commit-Queue: John Chen <johnchen@chromium.org> Reviewed-by:
John Chen <johnchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#797838}
-
Numfor Mbiziwo-Tiapo authored
Implements putAllValues where any errors cause the whole request to fail, instead of just the value/s that failed. Explainer: https://github.com/nums11/idb-putall/blob/master/Explainer.md Design Doc: https://docs.google.com/document/d/1wawQ8Pl-Vi6GQN5-y2UVkcghipcOGg0WRAC0ZyBkezg/edit I2P: https://groups.google.com/a/chromium.org/g/blink-dev/c/TPd_rtgO3_k/m/qZmPy1dfAgAJ Change-Id: I976db2fe4c441f0ae288e63deb4c69c148721a18 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2324146Reviewed-by:
Christian Biesinger <cbiesinger@chromium.org> Reviewed-by:
Joshua Bell <jsbell@chromium.org> Reviewed-by:
Chris Palmer <palmer@chromium.org> Reviewed-by:
Olivier Yiptong <oyiptong@chromium.org> Commit-Queue: Daniel Murphy <dmurph@chromium.org> Cr-Commit-Position: refs/heads/master@{#797837}
-
David Tseng authored
When SA calls someAutomationNode.focus(), it may generate focus events on someAutomationNode later. This isn't always desirable, e.g. when the node is a text field and SA wants to remain on the VK. Correct this by ignoring focus events of this type i.e. these events have eventFrom 'action'. R=anastasi@google.com Fixed: 1113669 AX-Relnotes: n/a Change-Id: I2266f0aced57db1949dfad2793cc58ac2be923eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352613 Commit-Queue: David Tseng <dtseng@chromium.org> Reviewed-by:
Anastasia Helfinstein <anastasi@google.com> Cr-Commit-Position: refs/heads/master@{#797836}
-
Jordan Taylor authored
Prior to this change, effects are always given the current phase of the timeline associated with them. This fails in certain situations such as pausing and then scrolling, setting current time with an inactive timeline, and many other scenarios where hold_time is set. In order to fix this, we have introduced hold_phase. Anytime hold_time is updated, hold_phase will also be updated with the appropriate phase. Sometimes the phase is set explicitly and other times we pull from the timeline current time. Animation effects will be given the animation hold_phase if it is populated, otherwise it will calculate its current phase (similar to how current time is calculated). The WebAnimations spec is being updated to reflect this change. Bug: 1046833 Change-Id: I4bf1e42eaab684c18829a79acc1ab8911ec893af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2135336 Commit-Queue: Jordan Taylor <jortaylo@microsoft.com> Reviewed-by:
Kevin Ellis <kevers@chromium.org> Reviewed-by:
Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#797835}
-
Nate Fischer authored
No change to logic. This exposes cc/base/switches.cc to Java with java_cpp_strings. Fixed: 1114378 Test: autoninja -C out/Default system_webview_apk Change-Id: Ie0ffebbaff78e2ee657b1518d8cab15c79760478 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2343850Reviewed-by:
Bo <boliu@chromium.org> Reviewed-by:
vmpstr <vmpstr@chromium.org> Commit-Queue: Nate Fischer <ntfschr@chromium.org> Cr-Commit-Position: refs/heads/master@{#797834}
-
Klaus Weidner authored
Propagate the actual fullscreen request type to OOPIF fullscreen ancestors so that they fire matching prefixed or unprefixed fullscreen events. (Previously, it was always using "unprefixed" for OOPIF.) Change-Id: I04000d2190e06127329db1d91565914227aa9480 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2351000 Commit-Queue: Klaus Weidner <klausw@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Reviewed-by:
Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#797833}
-
chromium-autoroll authored
Roll ChromeOS Airmont AFDO profile from 86-4183.57-1597053344-benchmark-86.0.4229.0-r1 to 86-4183.57-1597053344-benchmark-86.0.4231.0-r1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/cros-afdo-airmont-chromium Please CC c-compiler-chrome@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 Tbr: c-compiler-chrome@google.com Change-Id: I5c889ab859f04f507be20a0e1798f7a5a368d949 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354483Reviewed-by:
-
Victor-Gabriel Savu authored
Add the DeviceReleaseLtsTag policy to allow devices to keep receiving updates from the LTS branch. Design doc: https://docs.google.com/document/d/1gPf9MyncHTRoB9xhq6dL8ngeKenq2Xe4dxg1z26GpdE Bug: chromium:1114784 Change-Id: I8d48994a0ad69a7f06989efded9f9ff70c9af7cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2341128 Commit-Queue: Victor-Gabriel Savu <vsavu@google.com> Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Reviewed-by:
Achuith Bhandarkar <achuith@chromium.org> Cr-Commit-Position: refs/heads/master@{#797831}
-
Takumi Fujimoto authored
Disabled for being flaky TBR=collinbaker@chromium.org Bug: 1116108 Change-Id: I66af00be5f80cbb78a77b73f108ef762f9528126 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354540Reviewed-by:
Takumi Fujimoto <takumif@chromium.org> Reviewed-by:
Collin Baker <collinbaker@chromium.org> Commit-Queue: Takumi Fujimoto <takumif@chromium.org> Cr-Commit-Position: refs/heads/master@{#797830}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/a22614c51d49..c71a9c2930fa 2020-08-13 changhaohan@chromium.org Enable real-time grid adorner 2020-08-13 alexrudenko@chromium.org Support enum members as types 2020-08-13 brgoddar@microsoft.com Add Presubmit for Devtools Experiment Telemetry 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:1047356,chromium:1066772,chromium:1107636 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I157f34e90b32018ab8cab8ff231ea70528e380e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354481Reviewed-by:
-
