- 13 Nov, 2020 28 commits
-
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/40e2a6830ac5..daab6896e293 2020-11-12 philipp.hancke@googlemail.com doc: port release notes 2020-11-12 natim@webrtc.org Delay VoipCore initialization. 2020-11-12 natim@webrtc.org Name change on channel and channel_id for consistency. 2020-11-12 titovartem@webrtc.org Add support for loopback route on emulated endpoints 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: I1663d5e29e226c77d2bb3ae9c88addb712d9ff4b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2535798Reviewed-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@{#827078}
-
Brandon Wylie authored
TBR=roagarwal@chromium.org Bug: 1148556 Change-Id: I95f5c7c0b246a119c4e7b5db6c5492f16cc521eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2536089Reviewed-by:
Brandon Wylie <wylieb@chromium.org> Commit-Queue: Brandon Wylie <wylieb@chromium.org> Cr-Commit-Position: refs/heads/master@{#827077}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/c6215e29d0ea..6a79629904ea 2020-11-12 tmathmeyer@chromium.org Add freezing score property, and fix Date crash 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: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Id36e9aae1e11ec4edab413a45f755844ee2d5ef9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2535879Reviewed-by:
-
Caitlin Fischer authored
Bug: 1144791 Change-Id: I3e66d25b9b92dc9662c29a6f5ea5a1ce21dc91bb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2527890Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Commit-Queue: Mark Pearson <mpearson@chromium.org> Cr-Commit-Position: refs/heads/master@{#827075}
-
Maggie Cai authored
This CL extends the metrics expiry date for ChromeOS.Apps.ExternalProtocolDialog, ChromeOS.Apps.ExternalProtocolDialog.Accept, and ChromeOS.Apps.ExternalProtocolDialog.Rejected. BUG=1138256 Change-Id: I77d8fe378040c2448ee1d76f94b85a7c4674399b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2533217Reviewed-by:
Caitlin Fischer <caitlinfischer@google.com> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Commit-Queue: Maggie Cai <mxcai@chromium.org> Cr-Commit-Position: refs/heads/master@{#827074}
-
Daniel Hosseinian authored
Implement a custom hasher for base::GUID so it may be used in standard hash containers. Bug: 1026195 Change-Id: I4a6315b21543e374b7eb6e8863b0afc3ff57f334 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2533644 Commit-Queue: Daniel Hosseinian <dhoss@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#827073}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/ac95abdb4b12..420f7362d68a 2020-11-12 wenbinzhang@google.com [benchmarking] skip finding possible browser if it is found already If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/catapult-autoroll Please CC zhanliang@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:chromeos-kevin-rel;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: chromium:1013630 Tbr: zhanliang@google.com Change-Id: I0880a9872ca13ba201b1ce66e7c721a0600c41b8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2533166Reviewed-by:
-
Haiyang Pan authored
On android CQ bots, content_browsertests currently only runs on L. But due to test device shortage on L, it experiences high pending time quite often. Since we have got 290 more Pie test devices (crbug.com/1111436#c43), content_browsertests should be able to run on Pie CQ. But first, let's start with 50% to see how it goes. Bug: 1111436 Change-Id: I7e5255c9a16bcc307a6f192e8d4d2f8076ad6f77 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2534602Reviewed-by:
Garrett Beaty <gbeaty@chromium.org> Commit-Queue: Haiyang Pan <hypan@google.com> Cr-Commit-Position: refs/heads/master@{#827071}
-
Ted Meyer authored
This adds a cache for both total number of players as well as total number of events kept by the each individual player, in order to prevent long-living pages from creating an otherwise unbounded number of events and creating memory pressure. There is some logic for selecting which players to prune, but no logic to do anything special for events yet. Events, Messages, and Errors are all subject to the same cache size limits, but the Properties can't grow unbounded so they aren't. R=dalecurtis Bug: 1145392 Change-Id: Iab39207276b6179b9f8828df7ced210154ab97dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2517928 Commit-Queue: Ted Meyer <tmathmeyer@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#827070}
-
Gabriel Marin authored
perf record with callstacks is not impacted by the large PEBS kernel bug https://lore.kernel.org/patchwork/project/lkml/list/?series=470855. BUG=b:168312716 Change-Id: I47b8a9eb3d7fcf72a06b47d3ee11166a07f8bc43 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2536095Reviewed-by:
George Burgess <gbiv@chromium.org> Reviewed-by:
Gabriel Marin <gmx@chromium.org> Commit-Queue: Gabriel Marin <gmx@chromium.org> Cr-Commit-Position: refs/heads/master@{#827069}
-
Jason Lin authored
Bug: 1145053 Change-Id: I99bcbf0afe97ddc8d2ad8486e8683b645668d4b1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2536412 Commit-Queue: Jason Lin <lxj@google.com> Commit-Queue: Joel Hockey <joelhockey@chromium.org> Auto-Submit: Jason Lin <lxj@google.com> Reviewed-by:
Joel Hockey <joelhockey@chromium.org> Cr-Commit-Position: refs/heads/master@{#827068}
-
Tommy Li authored
This CL is a partial revert of: https://chromium-review.googlesource.com/c/chromium/src/+/2523556 We still need the plugin_is_deprecated field for Flash for delivery to M87 via component updater. (That should get manual testing before delivery). Bug: 1148537 Change-Id: I3eb5094c5b00d34f5f82b321d24f55a3f869a025 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2535922 Commit-Queue: Tommy Li <tommycli@chromium.org> Reviewed-by:
Bill Budge <bbudge@chromium.org> Reviewed-by:
Will Harris <wfh@chromium.org> Cr-Commit-Position: refs/heads/master@{#827067}
-
Aaron Leventhal authored
A previous CL tried to defer work in DidInsertChildrenOfNode() so that occurred when layout was clean, but the change was incorrect because: 1. DidInsertChildrenOfNodeWithCleanLayout() wasn't even called! 2. Even if that method is called via DeferTreeUpdate, the loop would not iterate as before, because by the time it's called, Get(node) will return different results for some nodes. Therefore, do the loop right away, and call TextChanged() on the first ancestor with an AXObject, as TextChanged() defers its work anyway. Bug: 1136770 Change-Id: I5ae270317f506bd7ba4fc3cf27b7728b5dca73a3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2533139 Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Auto-Submit: Aaron Leventhal <aleventhal@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#827066}
-
Darren Shen authored
All files in this directory are already Chrome OS only. Change-Id: I1d6f953371940745c5429ba33777f533ae2a1325 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2532142Reviewed-by:
Jing Wang <jiwan@chromium.org> Reviewed-by:
Yuichiro Hanada <yhanada@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#827065}
-
Josh Nohle authored
Record metrics for * total payload size in kB, * total payload transfer rate in kB/s * the number of file/text attachments per payload We also slice the first two metrics by * send/receive * phone/Chromebook/tablet/unknown * success/failure/cancelled Manually tested and verified results at chrome://histograms. Bug: 1105579 Change-Id: I94d6283157ca65bc4cd33fcf9d0c2074fb89db66 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2531899Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
James Vecore <vecore@google.com> Reviewed-by:
Ryan Hansberry <hansberry@chromium.org> Commit-Queue: Josh Nohle <nohle@chromium.org> Cr-Commit-Position: refs/heads/master@{#827064}
-
Wan-Teh Chang authored
Bug: 1147863 Change-Id: Ia3186b0c09d3b73a14e0745ffb0a3b2fb12b1a3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2533915Reviewed-by:
Urvang Joshi <urvang@chromium.org> Reviewed-by:
James Zern <jzern@google.com> Commit-Queue: Wan-Teh Chang <wtc@google.com> Cr-Commit-Position: refs/heads/master@{#827063}
-
Yue Li authored
Currently we detect the language only using the surrounding text. Check user selected text first and fall back to the surrounding text if the confidence level is no high enough. Bug: b/172374961 Test: Run existing tests Change-Id: Ifbcd820828aa7628994b90b756bcd2c9797f30c5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2528646Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Reviewed-by:
Jeroen Dhollander <jeroendh@chromium.org> Commit-Queue: Yue Li <updowndota@chromium.org> Cr-Commit-Position: refs/heads/master@{#827062}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/f0517095b853..5157fbfbae86 2020-11-12 cwallez@chromium.org roll_dep.py: Support upstream branch being origin/main. 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: I536ee9bbc6f02a7ee8f0bba9ab15468f918a68b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2535580Reviewed-by:
-
chromium-autoroll authored
https://dawn.googlesource.com/tint.git/+log/1980095da7f4..20a8d31849c9 2020-11-12 dsinclair@chromium.org Create an AST builder class. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/tint-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: If33ce849b84f9809bc872d0cee70cb636197601d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2535570Reviewed-by:
-
Dale Curtis authored
This allows for direct planar access to capture buffers on macOS. R=sandersd Bug: 1137288, 1141214 Change-Id: I6a4859a807f2d77fd2fdd87c61f8c15dbdfbb0ac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2536035 Commit-Queue: Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Dan Sanders <sandersd@chromium.org> Reviewed-by:
Dan Sanders <sandersd@chromium.org> Auto-Submit: Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#827059}
-
Dave Tapuska authored
Collapse WebViewImpl's implementation together with WebFrameWidgetImpl's and place it in base. WebViewImpl's version was not checking for drag and drop, and IgnoreInputEvents state but WebFrameWidgetImpl's was. These were unnecessary because all input first goes through HandleInputEvent and if there were any messages would be first discarded there. Add a test to ensure the messages are dropped correctly without the additional checks. BUG=1097816 Change-Id: I0bb95f0585296a48bff96bcc553c5ca80c701ecc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2532732 Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#827058}
-
Xiang Ji authored
Validation: tryjob Bug: 1105203 Change-Id: Ife6434732a999e32a44868bcf7bb996a72e907f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2533308Reviewed-by:
Owen Min <zmin@chromium.org> Commit-Queue: Xiang Ji <jxiang@google.com> Cr-Commit-Position: refs/heads/master@{#827057}
-
Collin Baker authored
Bug: 1100596 Change-Id: I64212babff827e76f0f614ad375fc690a3d6db30 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2533835 Commit-Queue: Collin Baker <collinbaker@chromium.org> Reviewed-by:
Weilun Shi <sweilun@chromium.org> Cr-Commit-Position: refs/heads/master@{#827056}
-
Mark Pearson authored
Some of these would get different types of data depending on the process it is run from. Does not comment all relevant functions, just the ones I noticed. Change-Id: I4450624db96021d39dbc1fb11b41e7d2fa561d23 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2519857 Commit-Queue: Mark Pearson <mpearson@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#827055}
-
Josh Nohle authored
For each discovery session, report the number of devices * discovered, * lost, and * present when a send starts. Also, track the number of milliseconds between a the start of a discovery session and * discovery of the first share target, * discovery of any share target, and * the start of a transfer. Manually verified using chrome://histograms Bug: 1105579 Change-Id: Ib998663d968fadcfb016c580ecf9119eefb5f0c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2530169Reviewed-by:
Jesse Doherty <jwd@chromium.org> Reviewed-by:
-
Nick Diego Yamane authored
A regression was introduced with initial extended-drag integration in Ozone/Wayland as described in details at https://crbug.com/1148021. This CL addresses the issue 2 described in the link above: When an already mapped window is dragged, it is not supposed to get a wl_pointer::enter again after the DND/extended session finishes (it already had focus before it started), so it's client responsibility to restore the focused window when upon drop event. That's like that because it is updated by the window drag controller based on data device events during the DND session. This patch fixes it by explicitly restoring the focus to the dragged window, if any, when the session finishes. Bug: 1148021 Change-Id: I8315a873673c303fb7726ff98a4a247983225442 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2533036 Commit-Queue: Nick Yamane <nickdiego@igalia.com> Reviewed-by:
Antonio Gomes <tonikitoo@igalia.com> Cr-Commit-Position: refs/heads/master@{#827053}
-
David Bertoni authored
Bug: 1143311 Change-Id: Ie8a50d33f65b2799e1a36f8aeacfed423acc96ce NoTry: True Tbr: perkj@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2536118Reviewed-by:
David Bertoni <dbertoni@chromium.org> Commit-Queue: David Bertoni <dbertoni@chromium.org> Auto-Submit: David Bertoni <dbertoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#827052}
-
dstockwell authored
Change-Id: I3661c364631551ed4bb0cbb3f0ee3c0b9cc81681 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2536411Reviewed-by:
David Lei <dlei@google.com> Commit-Queue: David Lei <dlei@google.com> Cr-Commit-Position: refs/heads/master@{#827051}
-
- 12 Nov, 2020 12 commits
-
-
Jeffrey Kardatzke authored
This adds the VAAPI accelerator delegate for H265 decoding. This is not actually enabled yet because there are other pieces higher up in the decoding pipeline that still need to be turned on. BUG=chromium:1141237,b:153111783 TEST=HEVC playback works w/ full set of changes, vaapi_unittest Change-Id: Ic0a2dbe774267d4852e0d4d47aa378c6602ad41f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2530798Reviewed-by:
Sergey Volk <servolk@chromium.org> Reviewed-by:
Miguel Casas <mcasas@chromium.org> Commit-Queue: Jeffrey Kardatzke <jkardatzke@google.com> Cr-Commit-Position: refs/heads/master@{#827050}
-
Dave Tapuska authored
No more widget associated messages exist they all have been moved to mojo, so remove this interface. BUG=993189,1097816 Change-Id: I069b3ae061ad8cd0587d12040779f183ef129878 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2514477 Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Kevin McNee <mcnee@chromium.org> Cr-Commit-Position: refs/heads/master@{#827049}
-
Jesse Schettler authored
Sort the page sizes and correctly select the default option. Bug: 1059779 Change-Id: Ibfc1f482d84b75785ae790f3349b93839590327d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2532969 Commit-Queue: Jesse Schettler <jschettler@chromium.org> Commit-Queue: Zentaro Kavanagh <zentaro@chromium.org> Reviewed-by:
Zentaro Kavanagh <zentaro@chromium.org> Auto-Submit: Jesse Schettler <jschettler@chromium.org> Cr-Commit-Position: refs/heads/master@{#827048}
-
Sam Maier authored
This warning message doesn't flood the screen like we feared it might. Increase this message size so it's more usable when importing new libraries. Change-Id: Ie3d2424e2763ac5aa7b969a3baafb66dd3c9a450 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2535932 Commit-Queue: Sam Maier <smaier@chromium.org> Commit-Queue: Andrew Grieve <agrieve@chromium.org> Auto-Submit: Sam Maier <smaier@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#827047}
-
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: Ibfbe02eac593171dea3ace043dfa2c535410c028 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2535794Reviewed-by:
-
Stephen Chenney authored
The painting path that uses tiled image painting to draw background images was incorrectly orientating images sized with contains or covers. The problem was in using an un-oriented image size when correcting the source rect for orientation, when an oriented size is expected. In hindsight, we should be using the oriented size for the tile size, subsetting and other operations in the slow path. This also simplifies the repeated tile case. The test fails due to decoding artifacts from the oriented images, but the reference result also shows bad antialiasing artifacts around the edges. We need fuzzy matching. Bug: 1129956 Change-Id: I584b821f110720854fc21df49168afcf37fdc09b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2533505 Commit-Queue: Stephen Chenney <schenney@chromium.org> Reviewed-by:
Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#827045}
-
Adam Langley authored
WebSocket connection failures resulted in a human-readable error message getting propagated to the Mojo interface, but there was no reliable way to, for example, know which HTTP status code caused an error. This change plumbs net error codes and HTTP status codes up into an optional calling in the Mojo interface. Other than implementing the new function in order to satisfy the interface, this has no effect on users. Change-Id: I8047b5b82422ca80e5bc0e0e8345408d29d9ede4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2527889 Commit-Queue: Adam Langley <agl@chromium.org> Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Reviewed-by:
Adam Rice <ricea@chromium.org> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#827044}
-
Jeffrey Cohen authored
Bug: 1141839 Change-Id: I1da008817c240679b37193b1e2bb13faf0036a52 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2530905 Commit-Queue: Jeffrey Cohen <jeffreycohen@chromium.org> Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#827043}
-
Christopher Cameron authored
Merge GetSkColorSpaceForSkSurfaces with GetSkColorSpace. This function never returns nullptr, so remove branches that checked for that. Remove RequiresColorConversion and inline in its one location. TBR=fserb Bug: 1115317 Change-Id: Icb011165f5f18a328ff52492d1c4760de96847df Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2530184Reviewed-by:
ccameron <ccameron@chromium.org> Commit-Queue: ccameron <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#827042}
-
James Hawkins authored
The initial implementation creates and persists a device name at startup, but this is not yet used anywhere else. Bug: 126802 Test: DeviceNameStoreTest.* Change-Id: Ibd185803947e90b53f87a789c4d4727e538d3a8a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523741 Commit-Queue: James Hawkins <jhawkins@chromium.org> Reviewed-by:
Dominic Battré <battre@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#827041}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/google/shaderc/+log/e258cf5e7aa9..88f9156d7f6a 2020-11-12 dneto@google.com Replace C-style cast with static_cast If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/shaderc-chromium-autoroll Please CC radial-bots+chrome-roll@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: radial-bots+chrome-roll@google.com Change-Id: I7628e8a60aa9fce7ebb81ae63fafc31da892c5a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2535993Reviewed-by:
-
Patrick Noland authored
This delegate serves two purposes: 1. It severs unwanted coupling between StartSurface/tasks and LocationBar via ReturnToChromeExperimentsUtil 2. It enables us to supply the parent tab via glue code in ToolbarManager rather than leaking this implementation detail into FakeboxDelegate Bug: 1119256 Change-Id: I0b161df67bd94e3f3fa9c9dbfda0cfcaf0ba05da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2533407 Commit-Queue: Patrick Noland <pnoland@chromium.org> Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Reviewed-by:
Yue Zhang <yuezhanggg@chromium.org> Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Cr-Commit-Position: refs/heads/master@{#827039}
-
