- 28 Sep, 2020 40 commits
-
-
Kevin McNee authored
static_cast is better suited for downcasting since it can check that the types are related. /components/cronet This CL was uploaded by git cl split. R=ericorth@chromium.org Change-Id: I4d485c7b43cdc9a755112f093e691f6077b13bdb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435753 Auto-Submit: Kevin McNee <mcnee@chromium.org> Reviewed-by:
Eric Orth <ericorth@chromium.org> Commit-Queue: Eric Orth <ericorth@chromium.org> Cr-Commit-Position: refs/heads/master@{#811301}
-
Chris Lu authored
Confirm Infobars do not have badges, so there is not need to update the state of the Infobar. Moreover, after ConfirmInfobarDelegate::Accept() the tab, and therefore the infobar, is removed. Bug: 1129762 Change-Id: I79d9c636b1df3e9de19c3f24f20193e9d0c2df88 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2432584 Commit-Queue: Chris Lu <thegreenfrog@chromium.org> Reviewed-by:
Sergio Collazos <sczs@chromium.org> Cr-Commit-Position: refs/heads/master@{#811300}
-
Haiyang Pan authored
The builder runs a smaller test suite since crrev.com/c/2422710. The GCE capacity should be able to hold more traffic. Bug: 997376, 1127110 Change-Id: I23c9bb5b55aa5f335dea3bdc1817c4793fcf9eb0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2429249Reviewed-by:
Yuke Liao <liaoyuke@chromium.org> Commit-Queue: Haiyang Pan <hypan@google.com> Cr-Commit-Position: refs/heads/master@{#811299}
-
Haiyang Pan authored
After the test suites adjustment in crrev.com/c/2427028, the device usage looks in a good shape and should be able to hold more traffc: http://shortn/_E2uBVeObl6 Bug: 1111436 Change-Id: I9bfb44a96feb2bc2d49ec8335afc73324711db5c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2429931Reviewed-by:
Ben Pastene <bpastene@chromium.org> Commit-Queue: Haiyang Pan <hypan@google.com> Cr-Commit-Position: refs/heads/master@{#811298}
-
Peter Qiu authored
Added support for virtual capture device that can transport video frames backed by GpuMemoryBuffer. Bug: 1129531 Test: service_unittests, manual test on Cast device Change-Id: I045046c403df714996e4c3908d889cecfab22fb6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2417105Reviewed-by:
Dominick Ng <dominickn@chromium.org> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Reviewed-by:
Ken Rockot <rockot@google.com> Commit-Queue: Peter Qiu <zqiu@chromium.org> Cr-Commit-Position: refs/heads/master@{#811297}
-
Peng Huang authored
Bug: 1132059 Change-Id: Ie6a27071d2427f5ce529c0b481138cff8ae66290 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2434098Reviewed-by:
Emircan Uysaler <emircan@chromium.org> Commit-Queue: Peng Huang <penghuang@chromium.org> Cr-Commit-Position: refs/heads/master@{#811296}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/58ceb60bf6b1..5ac564dd6553 2020-09-28 wolfi@chromium.org Fix horizontal scroll/overflow for frame details view If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: chromium:1066415 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I01cb5415333e80dec19be54e795b46c2602dd1ae Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435498Reviewed-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@{#811295}
-
James Hawkins authored
R=khorimoto@chromium.org Bug: 1045266 Test: OSSettingsNetworkSummary* Change-Id: I7829685316e5f9cf52e20296a0d73f66ef5cc2ac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2432081 Commit-Queue: James Hawkins <jhawkins@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#811294}
-
chromium-autoroll authored
Roll ChromeOS Silvermont AFDO profile from 87-4258.0-1600689257-benchmark-87.0.4275.0-r1 to 87-4265.0-1601289755-benchmark-87.0.4275.0-r1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/cros-afdo-silvermont-chromium Please CC c-compiler-chrome@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Tbr: c-compiler-chrome@google.com Change-Id: I3f1a9de8d4e7066a565821bfd708778e9a9e835a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435913Reviewed-by:
-
Tomasz Wiszkowski authored
This change moves the two frequently used interfaces to a shared Omnibox suggestions namespace. Bug: 1106109 Change-Id: Ida2aa4f3ea2f961b5ab901df62e570fa4402122b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2433053Reviewed-by:
Ted Choc <tedchoc@chromium.org> Commit-Queue: Tomasz Wiszkowski <ender@google.com> Cr-Commit-Position: refs/heads/master@{#811292}
-
Kevin Ellis authored
This patch adds support for logical styles in animations created via element.animate(). Previously, CSSPropertyValueSets were kept for shorthand properties for the sole purpose of serialization of the shorthand property values in getKeyframes. These sets now hold additional usage for reevaluation as needed to resolve naming conflicts or applying updates after a change to the text direction or writing mode. An optimistic strategy is used during the initial parse to minimize computational overhead. A second pass of the property name expansion is only applied when needed. During style update, a change in text direction or writing mode will trigger an update to all running animations. CSS animations and transitions are affected only if modified by a setKeyframes call. Keyframes without logical properties are also uneffected. Any keyframe model with one or more affected keyframes is automatically invalidated and resampled. Bug: 865579 Change-Id: Ia2a34b465fadbb8c8f81aeefa72ea38d52fd97d4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425167 Commit-Queue: Kevin Ellis <kevers@chromium.org> Reviewed-by:
Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#811291}
-
Nela Kaczmarek authored
This change creates AffiliationFetcherBase which derives from AffiliationFetcherInterface. This is a base class for existing AffiliationFetcher, which allows a derived class to implement the request part of the fetcher. The response part stays the same. Bug: 1108279 Change-Id: Ia54a4d88f6684c0c95345b6c26eb5132d1ec6233 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404843Reviewed-by:
Jan Wilken Dörrie <jdoerrie@chromium.org> Commit-Queue: Nela Kaczmarek <nelakaczmarek@google.com> Cr-Commit-Position: refs/heads/master@{#811290}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/79c5fa7eebcb..8b16441c661b 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 gayane@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: gayane@google.com Change-Id: I5381376db49143743769f34364da613347253c25 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435494Reviewed-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@{#811289}
-
Javier Fernández García-Boente authored
The crash described in the issue 1132762 was caused by our rencet change in r811115, to ensure the trailing_collapsible_space_ structure is reset when the associated item_result changed. However, there was an error in the condition, so that we should ensure we only call the 'reset()' function when the Optional has value. Bug: 1132762, 1132811 Change-Id: I73d10c309162649e143cd66ff7702c4ac7e5eed2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435388 Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#811288}
-
Daniel Classon authored
For some edgecases, i.e. Chromeboxes, there is an ethernet section shown with "No network". Show a search result for Ethernet that links to the Network Section. Fixed: 1096768 Test: Remove the lines as seen in Patchset 2 (test setup) and run on Linux CrOS emulator.. Change-Id: I0dd06b1fd77129499ad11b732dffedb5c28d2f00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2429258 Commit-Queue: Daniel Classon <dclasson@google.com> Reviewed-by:
-
James Cook authored
There are some build hacks that compile ozone/wayland into the stock chromeos build. Those hacks caused the original CL to pass GN check for the CQ linux, chromeos and lacros bots, but fail gn check on the on chromeos code search bot. I'm trying to remove the hacks with crrev.com/c/2432137 but it may take some time to validate and get reviewed. For now, add nogncheck to the include. I've verified locally that the codesearch config builds correctly and passes gn check. Original CL description: The ID prefix is shared between the Wayland client code in Lacros and the Wayland server code in ash, so share the constant. Bug: 1095360 Change-Id: Ied9c879e3aef8224e1d6c5f871a42cfe0745e614 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2427546Reviewed-by:
Antonio Gomes (GMT-4) <tonikitoo@igalia.com> Commit-Queue: James Cook <jamescook@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#810277} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2433024 Cr-Commit-Position: refs/heads/master@{#811286}
-
Curt Clemens authored
Adds strings to ash/ash_strings.grd and uses them in the NearbyShareVisibilityFeaturePodController. Change-Id: I112c8a413bb8deffc038e9272ecbebd7f53ddc99 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401842 Commit-Queue: Curt Clemens <cclem@google.com> Reviewed-by:
James Vecore <vecore@google.com> Reviewed-by:
James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#811285}
-
Alice Wang authored
This CL sets line height of the bottom sheet subtitle and incognito message to 20sp, according to UI mock and chrome UI spec on Android. Screenshots: https://crbug.com/1132215/#c4 Bug: 1132215 Change-Id: I7f632f2d8906a8cdbf4e4b1965a667ef38d35860 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435187 Commit-Queue: Alice Wang <aliceywang@chromium.org> Reviewed-by:
Boris Sazonov <bsazonov@chromium.org> Cr-Commit-Position: refs/heads/master@{#811284}
-
Jazz Xu authored
Bug: 1132904 Change-Id: If39e460248f4358002f1d05c76a32a24d3a0d154 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435747Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Reviewed-by:
Tommy Steimel <steimel@chromium.org> Commit-Queue: Jazz Xu <jazzhsu@chromium.org> Cr-Commit-Position: refs/heads/master@{#811283}
-
Keren Zhu authored
* Change title and body text alignment to left. * Change font size to - with title: title 18pt, body 13pt, button 13pt - w/o title: body 14pt, button 13pt This change will apply to all IPH bubbles, i.e. both snooze and non-snooze bubbles. spec: go/desktop-iph-snooze-ux-spec Bug: 1121399 Change-Id: Idee04707d42d57b9f65cb99b36a29fa19a99318b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425194Reviewed-by:
Collin Baker <collinbaker@chromium.org> Commit-Queue: Keren Zhu <kerenzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#811282}
-
Francois Doray authored
Change description: ------------------- This CL changes the intensive wake up throttling policy so that it does not affect the execution of timers with nesting level < 5 : In a Window whose top Window has been hidden for 5 minutes and which is not opted out from intensive wake up throttling, a timer task can run: - on a 1-second aligned wake up if: - the task's nesting level is < 5, or, - the Window is same-origin with the top Window and at least 1 minute has elapsed since the last timer with nesting level >= 5 has run in any Window in the tree that is same-origin with the top Window - on a 1-minute aligned wake up, otherwise. Rationale: ---------- Unfortunately, limiting all timers to 1 wake up per minute caused breakages on some sites. After reaching out to site owners, we established that opting out timer tasks with nesting level < 5 prevents these breakages. Local tests suggest that most timers tasks have a nesting level >= 5. Therefore, we don't expect that this policy change will have a significant impact on power usage. Timers with nesting level >= 5 can run on a 1-second aligned wake up if there hasn't been a wake up in the last minute, because we don't want to penalize pages that have their own logic to ensure that the wake up rate is below 1 per minute. For example, a repeating timer with a 90 seconds timeout should not be affected by intensive throttling. Discussion: ----------- https://groups.google.com/a/chromium.org/g/scheduler-dev/c/EWKYCZlWjpc Bug: 1075553 Change-Id: I90d553608b9e3e64a9e6456112d5f4454d51bf1d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2417293Reviewed-by:Kentaro Hara <haraken@chromium.org> Reviewed-by:
Sami Kyöstilä <skyostil@chromium.org> Commit-Queue: François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#811281}
-
chromium-internal-autoroll authored
Release_Notes: http://go/media_app-x20/relnotes/Main/media_app_202009280800_RC00.html https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/media_app/app/+/W-Axu-xOAC73R6IETvUzr5ssqwyUgIQVQPtCBDfKISUC If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/media-app-chromium-autoroll Please CC media-app@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 Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome;luci.chrome.try:linux-chromeos-chrome-easwa Bug: b/159851982,b/161406194 Tbr: media-app@grotations.appspotmail.com Change-Id: Ief0718dce2eb40392f58fb007ca7f94cef12264e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435489Reviewed-by:
-
Sadrul Habib Chowdhury authored
Emit a trace-event for devtools when a frame is dropped. This trace-event will be used to show the dropped frames in the devtools timeline. The |id| of the LayerTreeHostImpl is required for these trace events, so the id is plumbed through CompositorFrameReportingController to the CompositorFrameReporter during creation from LayerTreeHostImpl. BUG=1075865 Change-Id: I300d5384af6aa8ed68a56c77bac5c77f3eac8d04 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2169848 Auto-Submit: Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Behdad Bakhshinategh <behdadb@chromium.org> Reviewed-by:
Behdad Bakhshinategh <behdadb@chromium.org> Cr-Commit-Position: refs/heads/master@{#811279}
-
Lei Zhang authored
Wrap |kMenuButtonDetails| in a getter function so it is initialized on first use. Also wrap it in a base::NoDestructor to prevent static destruction. Bug: 537099 Change-Id: Ia50bed6c089ee554bd0fe59677bda19280883362 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2429872 Commit-Queue: Lei Zhang <thestig@chromium.org> Reviewed-by:
Anastasia Helfinstein <anastasi@google.com> Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Tetsui Ohkubo <tetsui@chromium.org> Cr-Commit-Position: refs/heads/master@{#811278}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/b6103ff5f992..08ae7cea30d2 2020-09-28 nisse@webrtc.org Reland "Delete the non-const version of the EncodedImage::data() method." 2020-09-28 tommi@webrtc.org Remove asyncinvoker from PeerConnection. 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: I29c7b64fb48ef8204c70152cf269d1901f2a29e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435490Reviewed-by:
-
Chris Sharp authored
supported It isn't clear when this behavior was actually supported for these OS, so I picked 73 because that is when the description was updated. Also update DnsOverHttpsMode and DnsOverHttpsTemplates to list android as supported since 85. BYPASS_POLICY_COMPATIBILITY_CHECK=These platforms were already supported, this is just updating documentation. Change-Id: Id45b0819e38c46ca17bc3f78ce8724ef5f5f2065 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401060 Commit-Queue: Chris Sharp <csharp@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Reviewed-by:
-
Mila Green authored
Bug: 1114719 Change-Id: I0fffe541f385079b8f34cb197c228545cfff77ea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2429583Reviewed-by:
Joshua Pawlicki <waffles@chromium.org> Reviewed-by:
Sorin Jianu <sorin@chromium.org> Commit-Queue: Mila Green <milagreen@chromium.org> Cr-Commit-Position: refs/heads/master@{#811275}
-
Demetrios Papadopoulos authored
Fixed: 1132421 Change-Id: I7d3e3261fcd35a27bc0da0338a5c1182adca7378 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2431574 Commit-Queue: John Lee <johntlee@chromium.org> Reviewed-by:
John Lee <johntlee@chromium.org> Auto-Submit: dpapad <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#811274}
-
Tanmoy Mollik authored
This cl adds render tests for different types of sync errors in SyncErrorCardPreference. Bug: 1107420 Change-Id: I3ebc308932eadb677310ea041559bb54bbb1765c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353255 Commit-Queue: Tanmoy Mollik <triploblastic@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Reviewed-by:
Alice Wang <aliceywang@chromium.org> Cr-Commit-Position: refs/heads/master@{#811273}
-
Colin Blundell authored
As part of bringing up ad blocking in WebLayer, we will need to componentize the ads blocked infobar. This CL takes an initial preparatory step by changing the dependence on the //chrome-level InfoBarService to be a dependence on the //components-level ContentInfoBarManager. No actual functionality needs to be changed, as the former is a subclass of the latter. Bug: 1116095 Change-Id: Iab5920f285cfd5a3e4fa61e314e166192e4462d3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2429953Reviewed-by:
Charlie Harrison <csharrison@chromium.org> Commit-Queue: Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/master@{#811272}
-
Garrett Beaty authored
Change-Id: I026f760b9d605d1ea29bd2a87b44990f5758a5ba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2432139Reviewed-by:
Erik Staab <estaab@chromium.org> Commit-Queue: Garrett Beaty <gbeaty@chromium.org> Cr-Commit-Position: refs/heads/master@{#811271}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/145f115c5496..306fc502cf96 2020-09-28 cwallez@chromium.org Use typed integers for the Fence FenceAPISerial 2020-09-28 cwallez@chromium.org Use typed integers for the Buffer MapRequestID 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: I4e8238f44655cbed855d15e6be8ae8bb3ebd7b21 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435488Reviewed-by:
-
Dominic Farolino authored
This CL associates RenderFrameProxy with AgentSchedulingGroup. It is a prerequisite for making AgentSchedulingGroup a fully-fledged RouteProvider and AssociatedInterfaceProvider. See: https://docs.google.com/document/d/1hnOeki8nNwZfVYi4vbid4kn12T7XS361uL0Zbb7ilSA/edit R=haraken@chromium.org, kouhei@chromium.org, talp@chromium.org Bug: 1111231, 1132901 Change-Id: Icb50fd9d11e7c53459172be86ca7834cad1a522f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2432866 Commit-Queue: Dominic Farolino <dom@chromium.org> Reviewed-by:
Tal Pressman <talp@chromium.org> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
-
Elly Fong-Jones authored
Bug: 1121927 Change-Id: I5abc297d2d5573d2e6dd8a887e29b9efbd573f1a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422465Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#811268}
-
Adrian McCarthy authored
* De-emphasize Sheriff-O'-Matic * Add bug search link for sheriff handoffs * Sheriff is the Lexan notetaker. Change-Id: I58da53452bce1d59204bcebe473866a10e2043f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423750 Commit-Queue: Adrian McCarthy <amccarth@google.com> Reviewed-by:
Reid Kleckner <rnk@chromium.org> Cr-Commit-Position: refs/heads/master@{#811267}
-
Gayane Petrosyan authored
TBR=estark@chromium.org Bug: 1132860 Change-Id: Ibfa8c6c05d63dd868b2b6f310079ed60226bfa87 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2434099Reviewed-by:
Gayane Petrosyan <gayane@chromium.org> Commit-Queue: Gayane Petrosyan <gayane@chromium.org> Cr-Commit-Position: refs/heads/master@{#811266}
-
Eric Willigers authored
We update behavior to match spec change https://github.com/w3c/web-share/pull/113 If a share() call is in progress and share() is called again, the new share request fails immediately. WebShare for ChromeOS and Windows will only ever have this new behavior. WebShare for Android (already shipped) would previously spin up multiple shares simultaneously. Spec: https://w3c.github.io/web-share/#share-method Note: we no longer have an Android post Lollipop MR1 test for user cancellation of the dialog - the existing test simply issues a second share request. Bug: 1002337 Change-Id: I1bef4923cb048a28f882f9dac889c841f1fc8265 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425933Reviewed-by:
-
Chromium WPT Sync authored
Using wpt-import in Chromium 40d727bf. With Chromium commits locally applied on WPT: 74e4b2fc "[COOP] access reporting: Use infinite timeout for receive." 9a583fa4 "Increase timeout of Content-Security-Policy WP test" Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md Directory owners for changes in this CL: nzolghadr@chromium.org, yosin@chromium.org: external/wpt/input-events NOAUTOREVERT=true TBR=robertma@google.com No-Export: true Change-Id: Ib7f62e7743459b1613c696dfed364f7c3761eb0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435659Reviewed-by:
WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#811264}
-
Koji Ishii authored
Following up r811190 crrev.com/c/2433926 that enabled DCHECK in |Self| for block fragmentation, this patch enables the same DCHECK for |SelfAndContents|. This DCHECK was added recently, at r811125 <crrev.com/c/2428530>. Bug: 1132619 Change-Id: I45855e1d421cad90db135256745f9b92ab7621dd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2432148 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#811263}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/ea1181f182dc..def823dfb288 2020-09-26 chrome-bot@chromium.org Update config settings by config-updater. 2020-09-26 chrome-bot@chromium.org Update config settings by config-updater. 2020-09-25 saklein@chromium.org BuildTargetUnitTest: Only use package atoms, not cpf. 2020-09-25 saklein@chromium.org api/validate: Add require_each validator. 2020-09-25 saklein@chromium.org api: refresh proto & fix payload unittests 2020-09-25 saklein@chromium.org api/controller: Remove redundant python version checks. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/chromite-chromium-autoroll Please CC chrome-os-gardeners@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:chromeos-betty-pi-arc-chrome;luci.chromium.try:chromeos-kevin-rel Tbr: chrome-os-gardeners@google.com Change-Id: I06b168ba3a11c18b9315b3ac2d33249d1ca0ca23 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435633Reviewed-by:
-
