- 22 Jan, 2021 40 commits
-
-
Dave Tapuska authored
A few more removals with respect to conversions from WebRect->gfx::Rect. BUG=738465 Change-Id: I93c62c173fa3788a2354f2c3406d58bdc5469e3f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2639230 Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#846328}
-
Peng Huang authored
Releasing SharedContextState needs a context current if it is GL. So we need to make a gl context current for it. Bug: 1157501 Change-Id: I7cdcff0422f83949065adcd386bb6d5f8c27a09b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2645332 Commit-Queue: Peng Huang <penghuang@chromium.org> Commit-Queue: Bo <boliu@chromium.org> Auto-Submit: Peng Huang <penghuang@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#846327}
-
Jeffrey Kardatzke authored
For cases where we are video only decrypt, we need to make calls into OEMCrypto to get the key material even if we already have it in order to update the key usage times. The update interval should be ~1 min. This ensures that we are making that call. BUG=b:178208439 TEST=Key usage time updates are occurring during Netflix playback Change-Id: I14d19e4a962c79206a8f41fa2ba5281bd0b95c77 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2644909Reviewed-by:
Jao-ke Chin-Lee <jchinlee@chromium.org> Commit-Queue: Jao-ke Chin-Lee <jchinlee@chromium.org> Auto-Submit: Jeffrey Kardatzke <jkardatzke@google.com> Cr-Commit-Position: refs/heads/master@{#846326}
-
Katie Dektar authored
Bug: 1169396 Change-Id: Iee21b83a251e8e724327d8cc816194ee71807f7b AX-Relnotes: N/A Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2643190 Auto-Submit: Katie Dektar <katie@chromium.org> Reviewed-by:
Nina Satragno <nsatragno@chromium.org> Commit-Queue: Nina Satragno <nsatragno@chromium.org> Cr-Commit-Position: refs/heads/master@{#846325}
-
Internal Frameworks Autoroller authored
TBR=bling-team@google.com Change-Id: I71902eb33c77ad91323caff6b3b3eaf0301121d6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2645444Reviewed-by:
Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#846324}
-
Victor Costan authored
This CL takes advantage of the fact that NativeIOQuotaClient is now mojofied and no longer ref-counted, and simpifies NativeIO's ownership graph. Bug: 1016065 Change-Id: I6eb6fa259111101e95459b5c0655261b0d7e43d6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2644638Reviewed-by:
Jarryd Goodman <jarrydg@chromium.org> Commit-Queue: Victor Costan <pwnall@chromium.org> Auto-Submit: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#846323}
-
Victor Costan authored
Bug: 1163048 Change-Id: I1c44ceeec54cd6f509c7a135cd27fb885b0667a5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628170 Commit-Queue: Victor Costan <pwnall@chromium.org> Reviewed-by:
Ben Kelly <wanderview@chromium.org> Cr-Commit-Position: refs/heads/master@{#846322}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/3232876ee47b..44860edcd260 2021-01-22 skyostil@google.com Merge "tracing: Fix potential track confusion" 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: None Tbr: perfetto-bugs@google.com Change-Id: I348f83876a9328a63ba178629f0bbe09f60c8c5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2644733Reviewed-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@{#846321}
-
Joon Ahn authored
http://screen/8wHgGmLWLSoJjrS Bug: 1125150 Test: browser_tests --gtest_filter=DiagnosticsApp* Change-Id: If3c7f35e4594557d04c9c343c92a25d029850b1f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2643944Reviewed-by:
Bailey Berro <baileyberro@chromium.org> Commit-Queue: Joon Ahn <joonbug@chromium.org> Cr-Commit-Position: refs/heads/master@{#846320}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/57144c8685d3..3232876ee47b 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: Ifa4787dc96e89597d6a39bc84d57c87a11ae19f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2644564Reviewed-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@{#846319}
-
Dave Tapuska authored
A few more removals with respect to conversions from WebRect->gfx::Rect. BUG=738465 Change-Id: Id61dad97afff35df06e242312c833f7e580440e4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2643623 Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#846318}
-
Robert Ogden authored
Also bumps the expiration of all the histograms to June 2021. No other behavioral changes. Bug: 1165072, 1165073 Change-Id: I7c78f6a9220167c050fb6aa50990ad92699b13a6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2630830Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Commit-Queue: Robert Ogden <robertogden@chromium.org> Cr-Commit-Position: refs/heads/master@{#846317}
-
Reilly Grant authored
This change converts callbacks from base::Bind and base::Callback to Once/Repeating in //chrome/browser/chromeos/customization. Bug: 1148570 Change-Id: I973f393e8b7a4f82a5f7cd1c668968ede150f34f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2645307 Auto-Submit: Reilly Grant <reillyg@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Commit-Queue: James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#846316}
-
Olivier Yiptong authored
This change unifies the font chooser and enumeration capabilities under one API. A developer will be able to choose between using enumeration and a chooser by passing an option parameter to the API. Bug: 1140267 Change-Id: I4cdbb7c89d4795255c2cf709ec76f8c518d1e699 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2638548 Commit-Queue: Olivier Yiptong <oyiptong@chromium.org> Reviewed-by:
Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/master@{#846315}
-
Thomas Guilbert authored
This CL introduces MediaStreamAudioTrackUnderlyingSource. It is an audio sink (in the MediaStream sense) which receives audio data. It is also an underlying source (in the Streams API sense), which converts the data received from an audio track into blink::AudioFrames, which can then be pulled from a ReadableStream. The CL also removes PushableAudioData and replaces it with AudioFrameSerializationData, which will be improved upon (or replaced) in crbug.com/1168418. Bug: 1157608, 1168418 Change-Id: I8230ada4331899d8f1ef7373fb3f3eeb9a5fde95 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2640913 Commit-Queue: Thomas Guilbert <tguilbert@chromium.org> Auto-Submit: Thomas Guilbert <tguilbert@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Reviewed-by:
Chrome Cunningham <chcunningham@chromium.org> Cr-Commit-Position: refs/heads/master@{#846314}
-
Adam Langley authored
This reverts commit 0b693d80. This triggers for small URLs but Sharing puts a proportionally much larger dino image over the top of it, degrading it too much in many cases. Reverting to merge to M89 then will revert-revert and add hack to set a minimum size for Sharing. BUG=1168455 Original change's description: > qr_code_generator: add version 2-L > > This change adds support for version two QR codes, with “low” error > correction. This configuration matches how other platforms generate eSIM > QR codes. Additionally, since version two QR codes are smaller, their > blocks can be displayed with more pixels each, so a lower level of error > correction is reasonable. > > Change-Id: I7f42239835f3d5c6c981b9c73680247858cc0f28 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623842 > Commit-Queue: Adam Langley <agl@chromium.org> > Auto-Submit: Adam Langley <agl@chromium.org> > Reviewed-by: Martin Kreichgauer <martinkr@google.com> > Cr-Commit-Position: refs/heads/master@{#843693} Change-Id: Icdbb28bfc660cca5006a5fe7bf33cb4663dd2e44 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2643228Reviewed-by:
Martin Kreichgauer <martinkr@google.com> Commit-Queue: Adam Langley <agl@chromium.org> Commit-Queue: Martin Kreichgauer <martinkr@google.com> Auto-Submit: Adam Langley <agl@chromium.org> Cr-Commit-Position: refs/heads/master@{#846313}
-
Yi Gu authored
This patch updates the infobar to show both the top and embedded origins if WebOTP is used in a cross-origin iframe. The UI remains the same if the API is used in the top frame. Note: the exact string to show to users is still under UI review. Bug: 1136506 Change-Id: I4320545c306abeb3cd44987bf0d2ba2ed94b192e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2643626 Commit-Queue: Yi Gu <yigu@chromium.org> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Reviewed-by:
Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#846312}
-
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-aemu-chromium-autoroll Please CC chrome-fuchsia-gardener@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 Tbr: chrome-fuchsia-gardener@grotations.appspotmail.com Change-Id: I62f02b5027cb5161017c7569e2c6a099ea19f4c3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2643191Reviewed-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@{#846311}
-
Shane Fitzpatrick authored
In the case where only 1 item is being sent, the spec calls for the format '<item_type> received...'. The previous functionality had it as '1 <item_type> received...'. This change aligns the strings to the spec. I opted for separate capitialized and non-capitialized version to reduce the risk of a runtime determination being wrong for some locales. Confirmed with Shiba that this new functionality is as expected. Fixed: 1158069 Change-Id: I2d12e305aa52b7c52389c71f53c6c5586f13be44 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2643696Reviewed-by:
Ryan Hansberry <hansberry@chromium.org> Commit-Queue: Shane Fitzpatrick <shanefitz@google.com> Cr-Commit-Position: refs/heads/master@{#846310}
-
Daniel Hosseinian authored
Also check-in the requisite encrypted PDF. Fixed: 1167036 Change-Id: I4234d3bfd3cb600907f3e9262e64aaf3cace9e8f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2638916 Commit-Queue: Daniel Hosseinian <dhoss@chromium.org> Reviewed-by:
dpapad <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#846309}
-
Eugene But authored
Bug: None Change-Id: If9375f350e354325a6eccd56ab47ace3d3c7130a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642755Reviewed-by:
Ali Juma <ajuma@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Commit-Queue: Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#846308}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/bf47f1bdf381..8ce2fad80022 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 katydek@google.com,nsatragno@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: chromium:1138953,chromium:1150968,chromium:1169257 Tbr: katydek@google.com,nsatragno@google.com Change-Id: Ibf7adf0821311ebc64d322918f73ddffc99ac6ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2644734Reviewed-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@{#846307}
-
Yicheng Li authored
https://chromium.googlesource.com/chromiumos/platform2/system_api.git/+log/1ee85a708f6a..2260ccd36830 $ git log 1ee85a708..2260ccd36 --date=short --no-merges --format='%ad %ae %s' 2021-01-13 yichengli u2fd: Add API to check whether u2f is enabled 2021-01-16 kimjae minios: Add DBus adaptor + service to minios Created with: roll-dep src/third_party/cros_system_api Bug: b/165724836 Change-Id: Iad34f9b1bb781bbf1742d66f17cd10bef84134ab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2645208 Commit-Queue: Yicheng Li <yichengli@chromium.org> Commit-Queue: Martin Kreichgauer <martinkr@google.com> Reviewed-by:
Martin Kreichgauer <martinkr@google.com> Cr-Commit-Position: refs/heads/master@{#846306}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/5397151e88ff..07bd252238b7 2021-01-22 ehmaldonado@chromium.org Change whitespace.txt 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 ajp@google.com,apolito@google.com,ehmaldonado@google.com,sokcevic@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: ajp@google.com,apolito@google.com,ehmaldonado@google.com,sokcevic@google.com Change-Id: I7c0ece816639446208d408796eaaf0fdaba6a3a4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2645326Reviewed-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@{#846305}
-
Katie Dektar authored
Bug: 1046784 Change-Id: I2779fd3a8ac092ab7f4cb69b77ae44740f3ab8f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2645204 Commit-Queue: Katie Dektar <katie@chromium.org> Auto-Submit: Katie Dektar <katie@chromium.org> Reviewed-by:
Nina Satragno <nsatragno@chromium.org> Cr-Commit-Position: refs/heads/master@{#846304}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/72cd1a5e8953..2c32fa647608 2021-01-22 cwallez@chromium.org Make ComboVertexStateDescriptor non-copyable non-movable. 2021-01-22 enga@chromium.org d3d12/vulkan: Skip descriptor update/creation if resource is destroyed 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 sarahmashay@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: sarahmashay@google.com Change-Id: Ia52a17b6185cb08d38cf0de371696e9c212572c3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2644729Reviewed-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@{#846303}
-
Xida Chen authored
This CL is intended to fix a flaky layout test. I cannot repro the flakiness locally, so this would be a speculative. We suspect that when the test ends, even though the text matches exactly, the rendering of the result is not updated yet so we need another rendering frame to show the correct result. Bug: 623434 Change-Id: Ib1a521114d31db9d698929761d9e4cd928798e60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2644722Reviewed-by:
Kevin Ellis <kevers@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#846302}
-
Rohan Pavone authored
Defines web_engine_shell target in isolate map, while also adding additional build targets for fuchsia-builder-perf-fyi. Change-Id: I9e11dda427f6461ce948ba104a7e09d1657511d1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2644345Reviewed-by:
Garrett Beaty <gbeaty@chromium.org> Reviewed-by:
John Chen <johnchen@chromium.org> Commit-Queue: Rohan Pavone <rohpavone@chromium.org> Cr-Commit-Position: refs/heads/master@{#846301}
-
Alice Gong authored
Implement OAuth2 authentication flow for Box to obtain authorization, refresh token, and access token using a pop-up window, and store tokens into profile prefs. This is part of a series that will eventually, if enabled by enterprise admin, replace regular DownloadItemRenameHandler with FileSystemConnectorRenameHandler, which uses FileSystemConnector to redirect downloaded local temporary files to get uploaded through a series of BoxApiCallFlow steps. This CL does the following: 1/ Create new profile prefs to hold the OAuth2 tokens needed for file system connectors. (connectors/connectors_prefs.h/cc) 2/ Implement UX for gathering Box user consent. This is being implemented as pop-up window hosting the Box consent flow, much like the force sign in dialog hosts the Google sign in flow. (connectors/ file_system/signin_dialog_delegate.h/cc) 3/ Implement OAuth2 flow to mint access and refresh tokens from user consent’s auth_code. 4/ Implement OAuth2 flow to mint access and refresh tokens from the previous refresh token. (connectors/file_system/ box_access_token_fetcher.h/cc) BUG=1168607 Change-Id: If4882440315151a7cc23f2a6f56430bdb2bc09bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2591667 Commit-Queue: Alice Gong <alicego@google.com> Auto-Submit: Alice Gong <alicego@google.com> Reviewed-by:
Nicolas Ouellet-Payeur <nicolaso@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Roger Tawa <rogerta@chromium.org> Reviewed-by:
Marc-André Decoste <mad@chromium.org> Reviewed-by:
Dominique Fauteux-Chapleau <domfc@chromium.org> Cr-Commit-Position: refs/heads/master@{#846300}
-
Tommy Li authored
Currently, when Chrome adds a new engine from the OpenSearch description file, it can delete the Default Search Engine if it is is safe_for_autoreplace() and not prepopulated. This is an edge case, but there are crash reports of this triggering our CHECK. From what I can tell, this issue has existed for a long time, but was never caught because we had a DCHECK instead of a CHECK. This CL does two things: 1. Prevents that happening by no longer returning an |existing_engine| from the CanAddAutogeneratedKeyword() method. Since Add() can now automatically do ranking and deduplication, there's no need for the caller to manually Remove() engines like before. 2. Makes OpenSearch outrank form-search autogenerated engines in TemplateURL::IsBetterThanEngineWithConflictingKeyword(). We always treated it this way, but this formalizes it in our sorting function, which helps us build our total ordering of TemplateURLs. In summary: This CL makes the auto-generated engine adding logic reuse our existing deduplication logic, rather than relying on its own custom logic, which didn't respect the default search provider. This is meant to be merged into M89. Bug: 1166372 Change-Id: I410a0f8870f65cd16001f5ebd120ccbf04aadd93 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2644936Reviewed-by:
Peter Kasting <pkasting@chromium.org> Reviewed-by:
Orin Jaworski <orinj@chromium.org> Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Commit-Queue: Tommy Li <tommycli@chromium.org> Cr-Commit-Position: refs/heads/master@{#846299}
-
Nathan Zabriskie authored
Currently with some texture sizes GLES2Util::ComputeImageDataSizesES3 will attempt to add row padding when calculating the size of a VideoFrame plane. This is because it's currently assumed that each row aligns on a 4 byte boundary based on GL_UNPACK_ALIGNMENT but VideoFrames make no such guarantee as they may be densely packed. This CL removes the GL_UNPACK_ALIGNMENT assumption so that we only use the VideoFrame's stride when calculating padding. Bug: 1166504, 1161131 Change-Id: I2484f5dfd2ad85b088fee57758776a5c9bd01d95 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642765Reviewed-by:
Vasiliy Telezhnikov <vasilyt@chromium.org> Commit-Queue: Nathan Zabriskie <nazabris@microsoft.com> Cr-Commit-Position: refs/heads/master@{#846298}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/1d5174b9dc3b..3fe96b789504 2021-01-22 capn@google.com Target macOS 10.14 on ARM64 to enable C++17 2021-01-22 bclayton@google.com Merge changes I6c21b03d,Ic6136d02,I988c0288,I21d11818,I79fa8162, ... 2021-01-21 capn@google.com Implement non-void indirect Reactor Call() support 2021-01-21 amaiorano@google.com Make RoutineT::getEntry() type safe 2021-01-21 swiftshader.regress@gmail.com Regres: Update test lists @ b3e5c440 2021-01-21 capn@google.com Target macOS 10.12 when building LLVM 2021-01-21 capn@google.com Use aligned allocation for classes with aligned members 2021-01-21 nicolascapens@google.com Enable and require C++17 compilation 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: I00e926222eb0c3c21c1eca6556da874af335badb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2645058Reviewed-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@{#846297}
-
yilkal authored
This cl makes sure that the dialog size and bounds are consistent with the rest of onboarding flow. Bug: 1169786 Change-Id: Ie433562bf353a287eaa8449cc8e50c27c0bce4b7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2645298Reviewed-by:
Dan S <danan@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Yilkal Abe <yilkal@chromium.org> Cr-Commit-Position: refs/heads/master@{#846296}
-
Andre Vincent authored
As of now, the Drive Service fetches an access token. Fixed: 1166345 Change-Id: I9446d5811ea1726c8865c7f3604da1554cce4fe5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628048 Commit-Queue: Andre Vincent <andrevincent@google.com> Reviewed-by:
Esmael Elmoslimany <aee@chromium.org> Reviewed-by:
Tibor Goldschwendt <tiborg@chromium.org> Cr-Commit-Position: refs/heads/master@{#846295}
-
Klaus Weidner authored
The onbeforexrselect event is supposed to be part of GlobalEventHandlers and separately inherited by {HTML,MathML,SVG}Element, Window, and Document. The current implementation had added it at the Element level which isn't correct, causing test failures in the idlharness test. Update the implementation to fix the inheritance, which unfortunately adds a bit of extra boilerplate. Also add objects to the idlharness test to verify the inheritance. Spec: https://immersive-web.github.io/dom-overlays/#onbeforexrselect Fixed: 1108685 Change-Id: I8df73304b7b2d9bd93df30b78953aa9b378f8cad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317813 Commit-Queue: Klaus Weidner <klausw@chromium.org> Reviewed-by:
Philip Jägenstedt <foolip@chromium.org> Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#846294}
-
Reilly Grant authored
This change converts callbacks from base::Bind and base::Callback to Once/Repeating in //chrome/browser/chromeos/app_mode. Bug: 1148570 Change-Id: I92338ffa90e975cf9c79e151f2c784a55ddd2556 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2645404 Commit-Queue: Reilly Grant <reillyg@chromium.org> Commit-Queue: Sergey Poromov <poromov@chromium.org> Reviewed-by:
Sergey Poromov <poromov@chromium.org> Auto-Submit: Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#846293}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1611316382-256aee3c7474e8e8ef074b7619cf9a4131f41980.profdata to chrome-mac-master-1611338398-fa58905b438c50560fef9145146b7c6ec25beb1e.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 pgo-profile-sheriffs@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:mac-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I67b394ba47370b8116884835e0a51d44fa6e297b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2645325Reviewed-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@{#846292}
-
Gauthier Ambard authored
This CL ensures that the fakebox width is correct when the screenshot of the NTP is taken. It was wrong as the width was first computed while the collection view had a zero width. The width is now re-computed when the NTP is added to its parent ViewController. Fixed: 1165956 Change-Id: I63cf57584fe185280956779791973495092dfbb9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2640440 Auto-Submit: Gauthier Ambard <gambard@chromium.org> Reviewed-by:
Sergio Collazos <sczs@chromium.org> Commit-Queue: Sergio Collazos <sczs@chromium.org> Cr-Commit-Position: refs/heads/master@{#846291}
-
Roberto Carrillo authored
Also, accept a flag on builder() to specify this, but make it False by default. R=chanli,nodir,bpastene@chromium.org Bug: 1074407 Change-Id: Ic27a484138f7ccedab2f0daebed4bccc448a435d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2644319 Commit-Queue: Roberto Carrillo <robertocn@chromium.org> Reviewed-by:
Nodir Turakulov <nodir@chromium.org> Reviewed-by:
Ben Pastene <bpastene@chromium.org> Reviewed-by:
Chan Li <chanli@chromium.org> Cr-Commit-Position: refs/heads/master@{#846290}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/5b2a5204087d..57144c8685d3 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-mac-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: I739bd6b4cdda298c4d9bdc58d4684fe389806a8e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2644524Reviewed-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@{#846289}
-