- 30 Jan, 2020 40 commits
-
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/0b3f3f156be2..b2f79dd4c2c7 Created with: gclient setdep -r src-internal@b2f79dd4c2c7 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC jbudorick@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: chromium:1041820 Tbr: jbudorick@google.com Change-Id: Ie07e0a507361be9f21d844c6c3442cea870b5d6c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031605Reviewed-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@{#736975}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/c31a4ec66af2..670af2692e5d git log c31a4ec66af2..670af2692e5d --date=short --first-parent --format='%ad %ae %s' 2020-01-30 danilchap@webrtc.org in RtpSenderVideo add support for writing DependencyDescriptor header extension 2020-01-30 danilchap@webrtc.org Add extra input validation to RtpFrameReferenceFinder for codec-specific cases Created with: gclient setdep -r src/third_party/webrtc@670af2692e5d If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Bug: chromium:1046995,chromium:1047024,chromium:1047095,chromium:1047165,chromium:1047190 Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: Ie6c340af20b9d7e02069e5373d7a03f360e5012c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031604Reviewed-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@{#736974}
-
John Chen authored
Rebaseline fast/css/css2-system-color-expected.html with updated rgb color values for MacOS 10.14. Rebaseline several other tests by explicitly specifying text colors. Bug: 1046986, 1028242 Change-Id: I815469a852d5c0808bc7df6d9876c29941bdf714 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029998Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: John Chen <johnchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#736973}
-
Xinghui Lu authored
Several changes in realtimeapi.proto are made in this CL: 1. The old cache_expression field is renamed to cache_expression_covering_match, this is to avoid breaking old clients that are using this field. 2. Add a new enum named cache_expression_match_type, if this field is not set, ignore this entry; if this field is set to EXACT_MATCH, this entry is applicable for exact url matching; if this field is set to COVERING_MATCH, this entry is applicable for host-suffix path-prefix matching. 3. Add a new cache_expression field, this field will be used as the cache expression for new clients. For details, see go/chrome-protego-cache-matching-field. Server-side change: http://cl/292004484 Bug: 1041675 Change-Id: I5a40babdb9be0ebad8661361a93194daa445f479 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008080Reviewed-by:
Varun Khaneja <vakh@chromium.org> Commit-Queue: Xinghui Lu <xinghuilu@chromium.org> Cr-Commit-Position: refs/heads/master@{#736972}
-
Reilly Grant authored
Bug: 884928 Change-Id: I3692c3d9093d67572336c6d6270ff3370bc2683e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994274 Auto-Submit: Reilly Grant <reillyg@chromium.org> Commit-Queue: Reilly Grant <reillyg@chromium.org> Commit-Queue: Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org> Reviewed-by:
Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org> Cr-Commit-Position: refs/heads/master@{#736971}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/ee07cb317579..d9884d3e7123 git log ee07cb317579..d9884d3e7123 --date=short --first-parent --format='%ad %ae %s' 2020-01-30 jmadill@chromium.org Vulkan: Don't dirty index/vertex buffers on each syncState. Created with: gclient setdep -r src/third_party/angle@d9884d3e7123 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC tobine@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;luci.chromium.try:win_optional_gpu_tests_rel Bug: None Tbr: tobine@google.com Change-Id: I9b52c29cc57f9983207a4508da2fe47259d877ea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031444Reviewed-by:
-
Owen Min authored
It watches the Profile create/delete event to create ExtensionRequestObserver for each Profile. Bug: 1006899 Change-Id: I19a89427a957813d41f843b4e92256bfff0d1edd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028456 Commit-Queue: Owen Min <zmin@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Cr-Commit-Position: refs/heads/master@{#736969}
-
Garrett Beaty authored
This change involves two semantic differences: 1. stable-gitiles-trigger is a poller rather than a scheduled trigger because it's not possible to generate a scheduled trigger using lucicfg. With the upcoming branch, this is a change that would need to be made soon regardless. 2. The notifiers for builders that are scheduled by a trigger now populate the repository field. Bug: 1011908 Change-Id: I217089efba52bd6ec92b291f2141a6e36e1477d8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031189 Commit-Queue: Garrett Beaty <gbeaty@chromium.org> Reviewed-by:
Aaron Gable <agable@chromium.org> Cr-Commit-Position: refs/heads/master@{#736968}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/096422a54f2c..e702867eed40 git log 096422a54f2c..e702867eed40 --date=short --first-parent --format='%ad %ae %s' 2020-01-30 brgoddar@microsoft.com Update PRESUBMIT.py to print current check running Created with: gclient setdep -r src/third_party/devtools-frontend/src@e702867eed40 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Bug: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I80d15700e0d05ec67f1334cbcda1fe5de54a6321 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031624Reviewed-by:
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/1ac8524b6984..65137d177ac2 git log 1ac8524b6984..65137d177ac2 --date=short --first-parent --format='%ad %ae %s' 2020-01-30 thestig@chromium.org Avoid an integer overflow in OpenJPEG. 2020-01-30 tsepez@chromium.org Comment two POD structs with raw c strings. 2020-01-30 tsepez@chromium.org Avoid raw c-style strings in CPDF_FormField. Created with: gclient setdep -r src/third_party/pdfium@65137d177ac2 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/+/master/autoroll/README.md Bug: chromium:1047097 Tbr: pdfium-deps-rolls@chromium.org Change-Id: I7a43f0568b471ef9866fc6302db3f81c95c49f51 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031626Reviewed-by:
-
Thomas Guilbert authored
The video-frame-size-change.html is flaky because it sometimes finishes before the pixels have rendered on screen. There are two reasons for this: 1) We only wait on the second video to finish seeking to end the test. 2) Seeking doesn't guarantee that the frames will be painted on screen. This CL fixes the issue by waiting for both videos to render on screen, by using video.rAF calls to end the test as soon as both videos have painted their frames. Bug: 993671 Change-Id: I236777bf3fa83fc57e9e4e80560703965602d40c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2025581 Commit-Queue: Thomas Guilbert <tguilbert@chromium.org> Commit-Queue: Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Auto-Submit: Thomas Guilbert <tguilbert@chromium.org> Cr-Commit-Position: refs/heads/master@{#736965}
-
Xida Chen authored
We could have off screen damages that is currently counted as frame expected. For example, there is a main thread animation outside of the current viewport, then for each begin main-frame, we neither report is "no-damage", nor report "submit-frame". In this case, we treat that main-frame as it caused no damage. Bug: 1021963 Change-Id: I3d9c37e625b78d6cf275208d77676ffe17b47611 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1987603Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#736964}
-
Olya Kalitova authored
This flips the feature that enables admins to configure default Crostini container via user cloud external policy to enabled by default. Bug: 1000287 Change-Id: I6bec81f759374ff9edad6207e2c2ae70d42b0a23 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031031Reviewed-by:
Igor <igorcov@chromium.org> Commit-Queue: Olya Kalitova <okalitova@chromium.org> Cr-Commit-Position: refs/heads/master@{#736963}
-
Eric Karl authored
No longer tuning this code, UMA not needed. Bug: 859757 Change-Id: I6756922422883b8369d2aa63b1ee4f0d2a94f94b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029234 Auto-Submit: Eric Karl <ericrk@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Commit-Queue: Eric Karl <ericrk@chromium.org> Cr-Commit-Position: refs/heads/master@{#736962}
-
Eric Karl authored
These were all expired after M77, adding <obsolete> tag and cleaning up code. Bug: 691863 Change-Id: Ibf654b78aad2b6bbbf85b2527f55dfe1d51c9f35 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029289Reviewed-by:
-
John Rummell authored
Bug: 1007802 Test: Modified browser_test passes Change-Id: I7847afc1c4989e31ebbd46482be1e14765faed13 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028929 Commit-Queue: John Rummell <jrummell@chromium.org> Reviewed-by:
Xiaohan Wang <xhwang@chromium.org> Cr-Commit-Position: refs/heads/master@{#736960}
-
Josh Simmons authored
OptimizationGuideDecider API. Bug: 1030813 Change-Id: I2d0e73e22ec52f1c09e218e50fe11cd737525d48 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029228Reviewed-by:
Megan Jablonski <megjablon@chromium.org> Reviewed-by:
Robert Ogden <robertogden@chromium.org> Commit-Queue: Josh Simmons <jds@google.com> Cr-Commit-Position: refs/heads/master@{#736959}
-
Will Spaetzal authored
R=crouleau@chromium.org, tmrts@chromium.org, ulan@chromium.org Bug: chromium:1044682 Change-Id: I4c2c564ba47d6822ebe911562ff2488ef2bc32e0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016347 Commit-Queue: Will Spaetzel <spaetzel@google.com> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Caleb Rouleau <crouleau@chromium.org> Cr-Commit-Position: refs/heads/master@{#736958}
-
Lijin Shen authored
Remove application context since it throws too many false positive warnings on some cases, especially when application context is widely used and is not used for ui change. TBR=twellington@chromium.org Bug: 775198, 908651 Change-Id: I88d635b2f273570d7344c4f558fbeb769c42c897 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031554 Commit-Queue: Andrew Grieve <agrieve@chromium.org> Auto-Submit: Lijin Shen <lazzzis@google.com> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#736957}
-
Ahmed Mehfooz authored
Bug: 1040960 Change-Id: Id84fbea0565c9ff48e89249dfb32dd134125c3ca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029198Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Ahmed Mehfooz <amehfooz@chromium.org> Cr-Commit-Position: refs/heads/master@{#736956}
-
Ian Prest authored
The linked bug is a crash caused by a dangling pointer; we hypothesize that it occurs in one of the few places where AXTree::Unserialize is called without an error being treated as fatal. This change adds a CHECK around one such call (which didn't have any error handling), and logs some data with a crash-key in a second case (which had existing error handling, but didn't treat it as fatal). This will help us prove (or disprove) these scenarios as the culprit. Bug: 1034755 Change-Id: I1b1164295b25e508c61ef97c1ea0ce093b52ba18 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2025836Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Reviewed-by:
Ethan Jimenez <ethavar@microsoft.com> Reviewed-by:
Aaron Leventhal <aleventhal@chromium.org> Commit-Queue: Ian Prest <iapres@microsoft.com> Cr-Commit-Position: refs/heads/master@{#736955}
-
Tanya Gupta authored
Added ability to prompt user for camera permissions. Change-Id: I8d831836a1c90aefc1d52b11e6886e1370c6db7a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015401 Commit-Queue: Tanya Gupta <tgupta@chromium.org> Reviewed-by:
Gayane Petrosyan <gayane@chromium.org> Cr-Commit-Position: refs/heads/master@{#736954}
-
Alex Clarke authored
WebLayer will be using VariationsService but it's distinct from android chrome so we need a way to override the platform in the variations url request. Bug: 1025612 Change-Id: Ie4f9f6bfabc3a6b9234fcf5589ad9f5b98c3224f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1951012 Commit-Queue: Alex Clarke <alexclarke@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#736953}
-
Garrett Beaty authored
* In lucicfg, ACLs cannot be applied indivudally to jobs, they are specified at the bucket level, so for the webrtc jobs to have the webrtc ACLS applied, they must also be applied to the webrtc triggers. * Job IDs are determined automatically by lucicfg, so jobs that have a different ID than their builder name were changed to match the builder name. * Remove unnecessary trailing space from schedules. Bug: 1011908 Change-Id: I250ee9a2c31d32ce729ab9a9ebd89eb40ddb6ae0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031244Reviewed-by:
-
Himanshu Jaju authored
Logs the reason why connection could not be established while exchanging offer or answer between the two devices. Bug: 1021984 Change-Id: If3743336e04c5cb631e8ba0ea1dde601b6ad502b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028067 Commit-Queue: Himanshu Jaju <himanshujaju@chromium.org> Reviewed-by:
Richard Knoll <knollr@chromium.org> Reviewed-by:
Brian White <bcwhite@chromium.org> Cr-Commit-Position: refs/heads/master@{#736951}
-
arthursonzogni authored
This correspond to step 1.d from the "Unify CSP" document: https://docs.google.com/document/d/1v5mJnXJ5dSVXE_rgvJnNM9bzH0ni0YzdhPQ7GLqyhao This merges: - content::ContentSecurityPolicy (removed) - network::mojom::ContentSecurityPolicy (kept) Only the mojo one remains: network::mojom::ContentSecurityPolicy; Future follow-up will: * move CSPContext to network. * remove content/common/content/security_policy/ With this patch, the goal "have a unique data structure for representing CSP outside of blink" is completed \o/ Bug: 1021462 Change-Id: I262b6c976a9096bc6ff7235ffd56a1985e948d43 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028128 Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#736950}
-
Thomas Tellier authored
Bug: 1010249 Change-Id: Ia44fdb3202c54a296fc22ae0d90703d2980d9d49 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2025549Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Reviewed-by:
-
Xida Chen authored
TBR=odejesush@chromium.org NOTRY=true Bug: 1047293 Change-Id: Ie5fc08657a7675f7030d8ad5779d2c5f1c792d6f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031553Reviewed-by:
Xida Chen <xidachen@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#736948}
-
Ryan Sturm authored
This adds a check to prevent DSE preconnect when the user has opted out of DSE automplete and URL uploads. Bug: 1036489 Change-Id: I015f4111377657193e6db99ca7bf2f809629270f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028296Reviewed-by:
Ryan Sturm <ryansturm@chromium.org> Reviewed-by:
-
Garrett Beaty authored
lucicfg does not allow for arbitrarily settings ACLs on jobs and triggers, instead triggers get the scheduler ACLs for the associated bucket and ACLs for jobs are based on what is necessary for whatever triggers it. Segmenting the parent trigger ACLs based on what the service account of the parent is matches what will be produced by lucicfg. This avoids adding additional ACLs to a large portion of the builders. Bug: 1011908 Change-Id: I8a2b3309016c58b27da929abd4dce5c82abff9c3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031186Reviewed-by:
-
Martin Kreichgauer authored
Turning a Bluetooth adapter on results in two StateChanged events for the corresponding Radio instance. Ensure that either way BluetoothAdapter::AdapterPoweredChanged() is only invoked once. Also remove equivalent code from FidoCableDiscovery since it is made obsolete by this change. Change-Id: Iaf5a039ca51e1970fbab2dc63e653e3b69c3339c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026591 Commit-Queue: Martin Kreichgauer <martinkr@google.com> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#736945}
-
kylechar authored
The tests setup and general structure was more complicated than necessary. Cleanup before landing some new tests. No changes to the test logic itself. Bug: 1047217 Change-Id: I6c676f67385e1f712a8479c75da52e216dc58b2b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031188Reviewed-by:
Vasiliy Telezhnikov <vasilyt@chromium.org> Commit-Queue: kylechar <kylechar@chromium.org> Cr-Commit-Position: refs/heads/master@{#736944}
-
Xida Chen authored
TBR=odejesush@chromium.org NOTRY=true Bug: 1047282 Change-Id: I430d96beb39ddf88c3bc9ab94db49fdbb5d5be29 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031549Reviewed-by:
-
Boris Sazonov authored
Follow-up to https://crrev.com/c/2027531. Renames CoreAccountInfo.getName to getEmail to match the C++ CoreAccountInfo object. Bug: None Change-Id: Icbe98595e75ff8d1827dd780e31c1babc8efd6f1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2027807 Commit-Queue: Boris Sazonov <bsazonov@chromium.org> Reviewed-by:
Tanmoy Mollik <triploblastic@chromium.org> Cr-Commit-Position: refs/heads/master@{#736942}
-
Clark DuVall authored
The URLLoaderFactory created in AppCacheHost::MaybePassSubresourceFactory() was not being passed through ContentBrowserClient::WillCreateURLLoaderFactory(), so wasn't getting picked up by things like AwProxyingURLLoaderFactory or WebRequestProxyingURLLoaderFactory. This change required threading the correct origin through to AppCacheHost so it can call WillCreateURLLoaderFactory() with the correct origin. Bug: 998340 Change-Id: I3d417ca2d07e14909f9ebca13eef367160951b44 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028164Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Marijn Kruisselbrink <mek@chromium.org> Commit-Queue: Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/heads/master@{#736941}
-
Himanshu Jaju authored
Logs the result of sending a SharingMessage via the webrtc service. Bug: 1021984 Change-Id: I71a722e2ac79c00cc237d5ffb306b5f212f28778 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2027411Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/916bee6fe15b..0b3f3f156be2 Created with: gclient setdep -r src-internal@0b3f3f156be2 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC jbudorick@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: jbudorick@google.com Change-Id: I52b00af720e3cbcfc64fa2922ad84a70d34f2307 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031131Reviewed-by:
-
Maks Orlovich authored
Seeing some flakiness due to timeouts in them, and they do look like they do a lot of things. Bug: 1047067 Change-Id: I1892f35a8047fdad8c50aeafc2da54665b522bc6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031364Reviewed-by:
Lily Chen <chlily@chromium.org> Commit-Queue: Maksim Orlovich <morlovich@chromium.org> Cr-Commit-Position: refs/heads/master@{#736938}
-
Allen Bauer authored
Bug: 1041614 Change-Id: Ie2bd59392a07d83d693603ccc4d540bc99680193 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028737 Commit-Queue: Peter Kasting <pkasting@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#736937}
-
Erik Jensen authored
The Apple Japanese keyboard has two language keys: kana to the right of the spacebar, and eisu to the left. These use the USB codes for Lang1 and Lang2, respectively. The uievents-code spec mentions this in the (non-normative) notes for Lang1 and Lang2: https://www.w3.org/TR/uievents-code/#table-key-code-alphanumeric-functional-2 This can also be seen in the USB-to-ADB mapping table used by the HID driver source code published by Apple: https://opensource.apple.com/source/IOHIDFamily/IOHIDFamily-1090.260.23/IOHIDFamily/Cosmo_USB2ADB.c.auto.html Change-Id: Ib856fbba2d0916c6016625abe226d394edcb5fa1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029173Reviewed-by:
Wez <wez@chromium.org> Commit-Queue: Erik Jensen <rkjnsn@chromium.org> Cr-Commit-Position: refs/heads/master@{#736936}
-
