- 22 Jul, 2020 40 commits
-
-
Stefan Zager authored
Change-Id: I904d9eac5d9084f5936118cab4029bd6500e6f6b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313380 Commit-Queue: Stefan Zager <szager@chromium.org> Reviewed-by:
Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#790898}
-
Mila Green authored
Bug: 1108416 Change-Id: I9fd080dbb66ca50656a2451b94c3e5610dce0040 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313876Reviewed-by:
Joshua Pawlicki <waffles@chromium.org> Commit-Queue: Mila Green <milagreen@chromium.org> Cr-Commit-Position: refs/heads/master@{#790897}
-
John Abd-El-Malek authored
This exposed a bug in the existing implementation (see test failures in patchset 1) since the UKM enabled state was being set based on the last profile's state instead of all profiles. Bug: 1107439, 1088488 Change-Id: I8191e69f4abfa7a7a0e0fab7093378372b00310a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2308938 Commit-Queue: John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#790896}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/c07c59ddb0be..6081b23b2980 2020-07-22 gbeaty@chromium.org Modify bot_update to support setting blamelist pins. 2020-07-22 gbeaty@chromium.org Use fixed revisions in bot_update's test API output_json. 2020-07-22 cwallez@chromium.org gclient: print use_relative_hooks deprecation on stderr. 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 ehmaldonado@google.com,sokcevic@google.com,ajp@google.com,apolito@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: chromium:1047893,chromium:1107325,chromium:1108301 Tbr: ehmaldonado@google.com,sokcevic@google.com,ajp@google.com,apolito@google.com Change-Id: I9b0fb5713c25581b2848711c5e4d3f0eace9585a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313537Reviewed-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@{#790895}
-
Guido Urdaneta authored
Prior to this CL, this function iterated over a source map that could be modified by a re-entrant call triggered by JS code. Bug: 1105426 Change-Id: I47e49e4132cba98e12ee7c195720ac9ecc1f485b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2312703Reviewed-by:
Marina Ciocea <marinaciocea@chromium.org> Commit-Queue: Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#790894}
-
chromium-autoroll authored
This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file a bug against gbiv@chromium.org. Additional context: https://crbug.com/805539 Please note that, despite rolling to chrome/android, this profile is used for both Linux and Android. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/afdo-chromium-autoroll Please CC gbiv@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 Tbr: gbiv@chromium.org Change-Id: Ic1c755c17b6619f3afa0d429a9006083f063808f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313536Reviewed-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@{#790893}
-
Josip Sokcevic authored
Bug: 1108431 Cr-Commit-Position: refs/heads/master@{#790892}
-
Josip Sokcevic authored
This changes return type of following functions: * SearchByTitle * GetRemainingFileList * AddNewDirectory * RemoveResourceFromDirectory * GetFileListInDirectory Bug: 1007686 Change-Id: I4720a98a28d78d76f200535c1b4199fb5347147d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2304668Reviewed-by:
Yoshiki Iguchi <yoshiki@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Josip Sokcevic <sokcevic@google.com>
-
Jose Dapena Paz authored
GCC fails to resolve NoDestructor of an initializer list for initializing kInvalidCharacters. But if we use also initializer list for NoDestructor it will work. Bug: 819294 Change-Id: I22d80b8a8c345287152f6f033ef0d9e2f1ea9734 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2310413Reviewed-by:
Brian Sheedy <bsheedy@chromium.org> Commit-Queue: José Dapena Paz <jdapena@igalia.com> Cr-Commit-Position: refs/heads/master@{#790890}
-
Lei Zhang authored
Slightly surprising, but apparently on Windows, one can write base::DeleteFileW() and still end up calling base::DeleteFile(). Fix these callers to use base::DeleteFile() directly, rather than relying on some macro magic. Also stop using the deprecated version of base::DeleteFile() and fix some nits. Bug: 1009837 Change-Id: I3e8e35c7d57928b587dc103217fccb7d1f0b4fa3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313042Reviewed-by:
Will Harris <wfh@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#790889}
-
Ryan Harrison authored
BUG=tint:123 Change-Id: I10915ff259d0f22c4074e9df59c90d0fbe21c68b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313099 Auto-Submit: Ryan Harrison <rharrison@chromium.org> Commit-Queue: Jonathan Backer <backer@chromium.org> Reviewed-by:
Jonathan Backer <backer@chromium.org> Cr-Commit-Position: refs/heads/master@{#790888}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/f272427bda39..d7a1fced41b0 2020-07-22 tommek@google.com Fix copying between images and buffers with padding 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: I9ab5cdc1fbeb435c84f5d1f737c13437a0bc26f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313177Reviewed-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@{#790887}
-
Zach Trudo authored
Bug: chromium:1078512 Change-Id: I96ecb2bd4a8a41cf8d55ce1c0f041999115389db Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2302717Reviewed-by:
Sergey Poromov <poromov@chromium.org> Commit-Queue: Zach Trudo <zatrudo@google.com> Cr-Commit-Position: refs/heads/master@{#790886}
-
Nohemi Fernandez authored
Use NSURLSession utilities instead of mocks in order to ensure that we do not make false assumptions around iOS APIs. Bug: 1102903 Change-Id: I2cf0db073bb21ea05e2d43c0eb6d39f8f276ad81 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307254Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Commit-Queue: Nohemi Fernandez <fernandex@chromium.org> Cr-Commit-Position: refs/heads/master@{#790885}
-
Mehran Mahmoudi authored
This removes a deps on paint preview test data which is no longer needed. Bug: 1106035 Change-Id: I612fb3ea91b1e313de4d651a4c2bf95e9e1415c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313219Reviewed-by:
Michael Thiessen <mthiesse@chromium.org> Commit-Queue: Mehran Mahmoudi <mahmoudi@chromium.org> Cr-Commit-Position: refs/heads/master@{#790884}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/c4cebc7efae1..8bd3bcf43431 2020-07-22 cwallez@chromium.org Revert "Turn on WGSL support by default in Dawn" 2020-07-21 rharrison@chromium.org Turn on WGSL support by default in Dawn 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: Ie688b1380848c67a61b1fc6d90f327c59154a6e0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313040Reviewed-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@{#790883}
-
arthursonzogni authored
This is a reland of 6e52cf21 The caused of the revert was a crash, fixed in: https://chromium-review.googlesource.com/c/chromium/src/+/2312696 Original change's description: > [COOP] access reporting [5/N] Plumb report type. > > All of this is put behind a flag disabled by default. > This is mostly based on the initial prototype: > https://chromium-review.googlesource.com/c/chromium/src/+/2223934/24 > > Define, plumb and use the "report-type" for COOP access reporting. > > COOP access reporting: > [1/N] https://chromium-review.googlesource.com/c/chromium/src/+/2264294 > [2/N] https://chromium-review.googlesource.com/c/chromium/src/+/2270185 > [3/N] https://chromium-review.googlesource.com/c/chromium/src/+/2270472 > [4/N] https://chromium-review.googlesource.com/c/chromium/src/+/2273120 > [5/N] this patch. > > Bug: chromium:1090273 > Change-Id: I5e51b3da6a20c85c073ea1fd84ea74557760a42f > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2309433 > Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> > Reviewed-by: Camille Lamy <clamy@chromium.org> > Reviewed-by: Pâris Meuleman <pmeuleman@chromium.org> > Reviewed-by: Mike West <mkwst@chromium.org> > Cr-Commit-Position: refs/heads/master@{#790420} TBR=clamy,pmeuleman,mkwst Bug: chromium:1090273 Change-Id: I720649b8aa580c438ab2abd3ba049636e36e3aa4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2312638Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Pâris Meuleman <pmeuleman@chromium.org> Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#790882}
-
Jose Dapena Paz authored
GCC will consider that as a type mistmatch, so this change replaces auto with the expected TimeDelta type. Bug: 819294 Change-Id: I798ddec83079ce572f820ca572db97c7993ee81e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2310433Reviewed-by:
Gabriel Charette <gab@chromium.org> Commit-Queue: José Dapena Paz <jdapena@igalia.com> Cr-Commit-Position: refs/heads/master@{#790881}
-
Alexander Cooper authored
Remove directories that either no longer exist (remoting/internal), or that no longer return any results via the git grep regex. google_apis/dive does not exist, but google_apis/drive does and triggers the regex, so assuming that was just a typo, that directory is also updated. Bug: 714018 Change-Id: I82096a0e957055a8cc4339a9b25b7bbc9b4a3eb0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2305019 Commit-Queue: Alexander Cooper <alcooper@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#790880}
-
Mustaq Ahmed authored
We have quite a few cases where some internal methods "synthesize" user activation notification triggers, as if they were real user interactions. After UAv2 shipped in M72, these calls /should/ be unnecessary, see the bug. However the compat implication is not clear. This CL is part of a sequence that would hook up histograms to each type of triggers. If a synthetic trigger turns out to be ineffective, we would blindly remove them. We will then investigate the remaining ones one-by-one. This CL covers the part of the change in blink/renderer/core/ to ease reviewing. Bug: 1103249 Change-Id: I572367eecec300b635a95b543b7538b7e5c2a8be Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2281301 Commit-Queue: Mustaq Ahmed <mustaq@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Cr-Commit-Position: refs/heads/master@{#790879}
-
Rushan Suleymanov authored
SetTestingFactory may reset existing services. This behaviour leads to using of deleted pointers in dependent services. It may affect only new services during trybot checks. SetUpInProcessBrowserTestFixture helps to initialize testing factory and prevent using deleted services. Bug: 1102307b Change-Id: Id2aaa7589d8a660c5a59f38e3c07051f8933ac9c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2312596Reviewed-by:
Jian Li <jianli@chromium.org> Commit-Queue: Rushan Suleymanov <rushans@google.com> Cr-Commit-Position: refs/heads/master@{#790878}
-
Shimi Zhang authored
As the AndroidX change is made, we don't need to keep this API interface anymore. Bug: 918065, b/161126366 Change-Id: Ie5f3d5007c604a2a343be7df45f8e8dfa8b1c236 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2311064 Auto-Submit: Shimi Zhang <ctzsm@chromium.org> Commit-Queue: Changwan Ryu <changwan@chromium.org> Reviewed-by:
Changwan Ryu <changwan@chromium.org> Cr-Commit-Position: refs/heads/master@{#790877}
-
Evan Stade authored
Turns out the shared tab doesn't always have a web contents, so revert to using getLastUsedRegularProfile instead of trying to get it from the tab. Bug: 1108202 Change-Id: I1a9199f67e7e4f8939b1621ade8d32222359e5b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313176Reviewed-by:
Gayane Petrosyan <gayane@chromium.org> Commit-Queue: Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#790876}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/20440b51438f..76e4baebf3bd 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 wjmaclean@google.com,orphis@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: wjmaclean@google.com,orphis@google.com Change-Id: I8ce868bfcd45b03d2bfa2e8b8b5bde13c1810892 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313036Reviewed-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@{#790875}
-
Yann Dago authored
Bug: 1106508 Change-Id: I60517f7e30a72d8d9194e3136ad228b02b27f100 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2303791 Commit-Queue: Yann Dago <ydago@chromium.org> Reviewed-by:
Owen Min <zmin@chromium.org> Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Cr-Commit-Position: refs/heads/master@{#790874}
-
Chris Hamilton authored
This is a reland of 3d677a19 Original change's description: > Introduce DedicatedWorkerToken. > > Subsequent CLs will migrate Shared and Service workers to use similar > tokens. This is in support of the performance.measureMemory API, endowing > workers with tokens that can be used as an identifier when communicating > information regarding V8 memory usage. > > BUG=1085129, 1096617 > > Change-Id: I184eabcd1a421ffcfb561f388f620eaf9471d9f8 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2297702 > Reviewed-by: Ahmed Fakhry <afakhry@chromium.org> > Reviewed-by: Matt Falkenhagen <falken@chromium.org> > Reviewed-by: Will Harris <wfh@chromium.org> > Commit-Queue: Chris Hamilton <chrisha@chromium.org> > Cr-Commit-Position: refs/heads/master@{#789141} Bug: 1085129 Bug: 1096617 Change-Id: I61f9ecfaaa155e0293fcdc243ca85f7eb8b6228d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2304174Reviewed-by:
Will Harris <wfh@chromium.org> Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Commit-Queue: Chris Hamilton <chrisha@chromium.org> Cr-Commit-Position: refs/heads/master@{#790873}
-
Josh Nohle authored
Constructs a test private certificate with the input visibility. This will be useful for certificate manager fakes and unit tests that require certificates with different visibilities. Change-Id: Ibd3e71d51d06e38c4029a6dbfc3653cc57dbef97 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2311048 Commit-Queue: James Vecore <vecore@google.com> Auto-Submit: Josh Nohle <nohle@chromium.org> Reviewed-by:
James Vecore <vecore@google.com> Cr-Commit-Position: refs/heads/master@{#790872}
-
Mila Green authored
Bug: 1106783 Change-Id: Ie9e9f5ed1898b012469516a3b96491b1bcb98d39 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313120Reviewed-by:
Joshua Pawlicki <waffles@chromium.org> Commit-Queue: Mila Green <milagreen@chromium.org> Cr-Commit-Position: refs/heads/master@{#790871}
-
spdonghao authored
Bug: 1076139 Change-Id: Iceed665287c5bf438b240a53e6379704e15edc59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2293217 Commit-Queue: Hao Dong <spdonghao@chromium.org> Reviewed-by:
Henrique Nakashima <hnakashima@chromium.org> Reviewed-by:
Xi Han <hanxi@chromium.org> Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Cr-Commit-Position: refs/heads/master@{#790870}
-
David Bokan authored
Page scale is changed when the user pinch-zooms a page or via parameters controlled by the viewport meta tag. Internally, there are two notions of page scale. A typical page hosted in a main frame will have a |page_scale_factor| that transforms all geometry below the the visual viewport. In this situation, a descendant widget (e.g. an OOPIF) will have its surface in the compositor scaled as a result of the page scale changes in the top-level frame. However, the descendant needs to update its content to reraster at the new scale. We cannot change the |page_scale_factor| inside it as that would scale all the geometry inside (the output of which is already scaled in the compositor). To solve this, nested frame widgets use an |external_page_scale_factor|. This value is used solely to affect the scale used for raster without applying any transforms to its layers. However, some widgets are in a state of being both a main frame and also nested inside a frame hierarchy. Portals and GuestViews(*) are two such widgets. Because it is a main frame and runs on Android, a portaled page may require scaling due to constraints set in the viewport <meta> tag; this scaling must apply to the |page_scale_factor|. That is, we want it to apply independently of the scale in the top-level frame and remain when the portal is activated to become top-level. However, prior to the portal being activated, we do also need to reraster its contents based on the page scale in the embedder. This CL does two things. First, it ensures that nested main frame widgets, like portals and GuestViews, participate in the |external_page_scale_factor| propagation from the main frame, as an OOPIF would. Alone, this change breaks assumptions about the |external_page_scale_factor| and |page_scale_factor| never being used in tandem. Thus, we also update PictureLayerImpl to combine these two values for raster and update DCHECKs in various places to make this a new possibility. (*) GuestViews also have this property but aren't really relevant in this case as they do not support browser native pinch-zoom or scaling. However, this fix applies to GuestViews as well, should they ever stop suppressing pinch-zoom. Bug: 932669 Change-Id: I0be06f577c634f3a752a8f8c2439a284f94472d5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2284613Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Lucas Gadani <lfg@chromium.org> Commit-Queue: David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#790869}
-
Lan Wei authored
hr-timestamp/input-events.htmlEvent timestamp tests that the received events on the page should be equal to the timestamp provided by the eventSender's recorded last event. But we should deprecate eventSender in the future, and GpuBenchmarking sends events based on the current system time, which cannot be equal to the received events' timestamp. Bug: 1047176 Change-Id: I225dec07b1928ae254d61e8a8384ebfc7dab75e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2173421 Commit-Queue: Lan Wei <lanwei@chromium.org> Reviewed-by:
David Bokan <bokan@chromium.org> Reviewed-by:
Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#790868}
-
arthursonzogni authored
This patch fixes a TODO. A COOP access report is sent when two windows from different virtual browsing context groups tries to access each other. COOP access reporting: [1/N] https://chromium-review.googlesource.com/c/chromium/src/+/2264294 [2/N] https://chromium-review.googlesource.com/c/chromium/src/+/2270185 [3/N] https://chromium-review.googlesource.com/c/chromium/src/+/2270472 [4/N] https://chromium-review.googlesource.com/c/chromium/src/+/2273120 [5/N] https://chromium-review.googlesource.com/c/chromium/src/+/2309433 [6/N] https://chromium-review.googlesource.com/c/chromium/src/+/2308715 [7/N] https://chromium-review.googlesource.com/c/chromium/src/+/2309697 [8/N] https://chromium-review.googlesource.com/c/chromium/src/+/2275889 [9/N] this patch. Bug: 1090273 Change-Id: I249183839ee8a5b93b6e8d35a033a99a4942b62b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2310530 Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Camille Lamy <clamy@chromium.org> Reviewed-by:
Pâris Meuleman <pmeuleman@chromium.org> Cr-Commit-Position: refs/heads/master@{#790867}
-
Eugene But authored
marq was added to OWNERS file when stuartmorgan left the team. Since that time marq did not do much of ios/web development and codereviews. Currently ios/web has 3 active owners from 3 different timezones (ajuma, eugenebut, gambard) who regularly do codereviews. marq is still top level owner of //ios/ and can review changes in ios/web if other owners are OOO. Confirmed with mark to remove him from OWNERS, so he does not have to do codereviews. Bug: None Change-Id: I0d2c6cef08c6f05f7d9f1bb5e6f9ab2dca2397f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2311055 Commit-Queue: Eugene But <eugenebut@chromium.org> Reviewed-by:
Mark Cogan <marq@chromium.org> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#790866}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/e3f70cddc88f..19031583c314 2020-07-22 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 6b2bcf62..8d6c555e (790515:790803) 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: I9c21b20b01817b760403d186b141341e4273d0e9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313039Reviewed-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@{#790865}
-
Prabir Pradhan authored
BUG=None TEST=None Change-Id: I8782a4af6ccbf7f44571826d8dea9c2dc3343d2d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2310976Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Commit-Queue: Prabir Pradhan <prabirmsp@chromium.org> Auto-Submit: Prabir Pradhan <prabirmsp@chromium.org> Cr-Commit-Position: refs/heads/master@{#790864}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/99a565b6..724a04e1 Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I9dcf23eca2a67e0aa3da86735522085b3aa70095 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313136Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#790863}
-
ckitagawa authored
This CL adds a smoke test for the scaling of paint previews. Bug: 1106035 Change-Id: I70db04a8dd83466f585f9c2949bf923b6bce8740 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2310893 Commit-Queue: Calder Kitagawa <ckitagawa@chromium.org> Reviewed-by:
Mehran Mahmoudi <mahmoudi@chromium.org> Cr-Commit-Position: refs/heads/master@{#790862}
-
W. James MacLean authored
This test is causing a fair amount of flake, disabling. TBR=dbertoni@chromium.org Bug: 1107934 Change-Id: Ieda5264517dcfd69f275379434ca3da9a0649f33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313121Reviewed-by:
James MacLean <wjmaclean@chromium.org> Commit-Queue: James MacLean <wjmaclean@chromium.org> Cr-Commit-Position: refs/heads/master@{#790861}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/01373555fef7..e9ced4f3da51 2020-07-22 tdenniston@google.com Elide inner loop geometry sometimes (toy stroker) 2020-07-22 nigeltao@google.com Flip Skia-uses-Wuffs-v0.3 from opt-in to opt-out 2020-07-22 johnstiles@google.com Simplify GrProcessorSet by removing multiple color/coverage FP support. 2020-07-22 adlai@google.com Reland "Migrate SkImage::makeWithFilter to GrRecordingContext" 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 robertphillips@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 Bug: None Tbr: robertphillips@google.com Change-Id: Ibee4c658ef662aed30f726dc78c8a2fd7480e216 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313037Reviewed-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@{#790860}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/75efd91227eb..9e1fc05ef7a2 2020-07-22 vmiklos@collabora.co.uk Add FPDFSignatureObj_GetByteRange() API 2020-07-22 thestig@chromium.org Remove deprecated use_relative_hooks setting from DEPS. 2020-07-22 nigi@chromium.org Enable FPDFAnnotEmbedderTest.RenderMultilineMarkupAnnotWithoutAP for Skia. 2020-07-22 nigi@chromium.org Enable FPDFAnnotEmbedderTest.AddAndSaveUnderlineAnnotation for Skia/SkiaPaths. 2020-07-21 tsepez@chromium.org Split off fxv8_unittest.h from cfx_v8_unittest.h 2020-07-21 dmazzoni@chromium.org Add FPDF_StructElement_GetID and FPDF_StructElement_GetLang 2020-07-21 nigi@chromium.org Enable FPDFEditEmbedderTest.InsertAndRemoveLargeFile for Skia/SkiaPaths. 2020-07-21 nigi@chromium.org Make Skia and SkiaPaths take fill option |aliased_path| into account. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pdfium-autoroll Please CC pdfium-deps-rolls@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: chromium:1107325 Tbr: pdfium-deps-rolls@chromium.org Change-Id: I29aed166f6154077545ef358d32ce6e8f589f346 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313038Reviewed-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@{#790859}
-