- 10 Sep, 2018 40 commits
-
-
Stephen Martinis authored
merge_results.py outputs a log line for every file that it 'merges'. Some of these files are only 'merging' one file. This makes the step log on buildbot be incredibly verbose, since there are thousands of artifacts generated by webkit_layout_tests. This CL changes the behavior to only log something if it's doing a non-trivial merge. 'Merges' which only merge one file aren't logged. Change-Id: I6e5bf7316a2f1ab41f8997582b12368c23456378 Reviewed-on: https://chromium-review.googlesource.com/1217594Reviewed-by:
Robert Ma <robertma@chromium.org> Commit-Queue: Stephen Martinis <martiniss@chromium.org> Cr-Commit-Position: refs/heads/master@{#590102}
-
Chromium WPT Sync authored
Using wpt-import in Chromium d476f83e. With Chromium commits locally applied on WPT: d7762551 "Consistently use single quotes in Background Fetch WPTs." Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/24517 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: ericwilligers@chromium.org: external/wpt/css/motion meade@chromium.org: external/wpt/web-animations NOAUTOREVERT=true TBR=raphael.kubo.da.costa@intel.com No-Export: true Change-Id: I4ad93e94f176e1809a9004d6cd2ebef266c703e2 Reviewed-on: https://chromium-review.googlesource.com/1217508 Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Reviewed-by:
Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Cr-Commit-Position: refs/heads/master@{#590101}
-
Kenneth Russell authored
This workaround appears to mostly be necessary for compositing and rasterization contexts, and has a performance cost when used with WebGL. Disable it there. Bug: 882317 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_optional_gpu_tests_rel Change-Id: I7dc89d11b2818f3af029d0dfb62d1a6e6fabfef3 Reviewed-on: https://chromium-review.googlesource.com/1217586Reviewed-by:
ccameron <ccameron@chromium.org> Reviewed-by:
Kai Ninomiya <kainino@chromium.org> Commit-Queue: Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#590100}
-
Daniel Rubery authored
In some cases, vec->at(i) was used as a more-readable alternative to (*vec)[i]. In others, it was used for const access to maps. at has questionable interactions with exceptions (see https://groups.google.com/a/chromium.org/forum/#!msg/cxx/6TDgM5g-NH4/NJSmyU01BgAJ), so I've added (*vec)[i] where possible, and bounds checked everywhere. Bug: 881604 Change-Id: Ia38ec235a8264a54ddc0dbe570c79e0227fe0f9e Reviewed-on: https://chromium-review.googlesource.com/1217104Reviewed-by:
Varun Khaneja <vakh@chromium.org> Commit-Queue: Daniel Rubery <drubery@chromium.org> Cr-Commit-Position: refs/heads/master@{#590099}
-
Tatiana Buldina authored
Change-Id: I30d965d28b5b2713b141899e494b254f67a38df5 Reviewed-on: https://chromium-review.googlesource.com/1217759Reviewed-by:
John Chen <johnchen@chromium.org> Commit-Queue: Tatiana Buldina <buldina@chromium.org> Cr-Commit-Position: refs/heads/master@{#590098}
-
Zach Stein authored
Enable on the command line by passing "--enable-features=WebRtcHideLocalIpsWithMdns" Check runtime setting with base::FeatureList::IsEnabled(features::kWebRtcHideLocalIpsWithMdns) Bug: chromium:875740 Change-Id: Ic8afd743d1b78da165cacb21ebc10837262af086 Reviewed-on: https://chromium-review.googlesource.com/1214328Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Commit-Queue: Zach Stein <zstein@google.com> Cr-Commit-Position: refs/heads/master@{#590097}
-
afdo-chromium-autoroll authored
This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file a bug against gbiv@chromium.org. Additional context: https://crbug.com/805539 The AutoRoll server is located here: https://autoroll.skia.org/r/afdo-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=gbiv@chromium.org Change-Id: I559955e313363142b566f71a2a9e412f87ac9aeb Reviewed-on: https://chromium-review.googlesource.com/1217705 Commit-Queue: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#590096}
-
Christian Biesinger authored
The number 8 for the initial capacity was picked at random. This seems to help especially with the float perf tests. Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Change-Id: Ie4217a459848e7269c791cf864f9aab163d7895d Reviewed-on: https://chromium-review.googlesource.com/1216813Reviewed-by:
Emil A Eklund <eae@chromium.org> Commit-Queue: Christian Biesinger <cbiesinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#590095}
-
Ben Pastene authored
We're planning on adding more types of VM tests, so this flag should come in handy in the future. Bug: 876587 Change-Id: I0db628151ae2016b4fd891fdbd5064ee41b1720f Reviewed-on: https://chromium-review.googlesource.com/1217073 Commit-Queue: Ben Pastene <bpastene@chromium.org> Reviewed-by:
John Budorick <jbudorick@chromium.org> Cr-Commit-Position: refs/heads/master@{#590094}
-
Tom Anderson authored
This became necessary to build Chrome after [1] when building without the sysroot. [1] https://chromium.googlesource.com/chromium/src/+/297928530fc400a897f62fa98ccf4a5485990f22 BUG=879147 TBR=dpranke Change-Id: Iff2d59b247cd764f404f0beeaf232cc8dc8188aa Reviewed-on: https://chromium-review.googlesource.com/1214699Reviewed-by:
Michael Moss <mmoss@chromium.org> Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/master@{#590093}
-
Artur Khachatryan authored
Test ChromeDriver.testTakeElementScreenshot fails on Android platforms. Disabling test for now. Bug: chromedriver:2579 Change-Id: I5ceb2cf4ba39cbfbeb37c851724e0b7ccd5a9925 Reviewed-on: https://chromium-review.googlesource.com/1217601Reviewed-by:
-
Scott Chen authored
This CL moves the extension-view-manager to a shared location to be used by other WebUIs. The immediate use case is for a new welcome page; see linked bug for details. Bug: 874146 Change-Id: Ieb168e61cf6ae02e04d624c92a131e9ec38fcdae Reviewed-on: https://chromium-review.googlesource.com/1157241Reviewed-by:
Hector Carmona <hcarmona@chromium.org> Commit-Queue: Scott Chen <scottchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#590091}
-
Moe Ahmadi authored
The root cause was that item of type ItemTypeSavedPasswords was not being properly formatter in |-collectionView:cellForItemAtIndexPath:| Also sets the detail text of the item at the time of creation, and not only when the preference changes. Bug: 882583 Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs Change-Id: I68a3d8660e520a99ec59b3fc48fb2f78dc59b5fe Reviewed-on: https://chromium-review.googlesource.com/1217503Reviewed-by:
Peter Lee <pkl@chromium.org> Commit-Queue: Moe Ahmadi <mahmadi@chromium.org> Cr-Commit-Position: refs/heads/master@{#590090}
-
Antonio Gomes authored
URLFetcher will stop working with advent of Network Service, and SimpleURLLoader is the replacement API for most clients. This CL migrates chromeos::chromeos::AttestationCAClient and the respective unittests away from URLFetcher. BUG=773295,879782 Change-Id: I9ccdad3a73108ad3e3e7ab4f148b93048433b3bd Reviewed-on: https://chromium-review.googlesource.com/1202223 Commit-Queue: Antonio Gomes <tonikitoo@igalia.com> Reviewed-by:
Matt Menke <mmenke@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#590089}
-
Kai Ninomiya authored
Bug: 881144 Change-Id: Idc5292cecf9a3d4dbc101a9c44c47bd3db62dab6 Reviewed-on: https://chromium-review.googlesource.com/1208941Reviewed-by:
Alexander Timin <altimin@chromium.org> Reviewed-by:
Ken Rockot <rockot@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Kai Ninomiya <kainino@chromium.org> Cr-Commit-Position: refs/heads/master@{#590088}
-
Quan Nguyen authored
Previously we prevented the login bubbles from overlapping into the shelf. This had some annoying side effects like obscuring the password field. This CL removes that part of the widget repositioning logic. A future CL will address the potential case of login bubbles going off screen on the bottom. Need to clarify the correct UX for this case. Bug: 880224, 875787 Change-Id: Iea42cd612e9b0c57516fdc9681843182fa8d268b Reviewed-on: https://chromium-review.googlesource.com/1217742Reviewed-by:
Jacob Dufault <jdufault@chromium.org> Commit-Queue: Quan Nguyen <qnnguyen@chromium.org> Cr-Commit-Position: refs/heads/master@{#590087}
-
Min Chen authored
changes in this cl, - Do not change the shelf's visibility if drag on the shelf that has been set to always shown. - Gesture drag on the shelf should not change its auto-hide behavior. Since we can only change it through the context menu of shelf now. - Fixed the failed related ShelfLayoutManagerTest*. Bug: 880682, 881154 Change-Id: I2187c4636b1bbb5ca59149e33dbcbb8c664863b1 Reviewed-on: https://chromium-review.googlesource.com/1214049Reviewed-by:
-
Xiaohui Chen authored
When Views are invisible by opacity 0 but still have visibility true, screenreader would still be able to read it. We need to explicitly set their visibility to false. Bug: b:113731925 Test: locally build and not able to navigate to these elements with Test: screen reader Change-Id: Ibb1b111844dbd6021c267ef594777614cf127189 Reviewed-on: https://chromium-review.googlesource.com/1212342Reviewed-by:
Muyuan Li <muyuanli@chromium.org> Commit-Queue: Xiaohui Chen <xiaohuic@chromium.org> Cr-Commit-Position: refs/heads/master@{#590085}
-
Quan Nguyen authored
Bug: 879542 Change-Id: I3712f517ab3ee5f78eede3922335ac5e240b9816 Reviewed-on: https://chromium-review.googlesource.com/1217342Reviewed-by:
-
David Black authored
This reverts commit 9bc4c7ef. Reason for revert: CL fixed UI jank but regressed accessibility. Will re-implement with another approach. Original change's description: > Fix UI jank caused by visibility change. > > Previously, when animating the footer view and/or its children, we > modified visibility so as not to receive focus/accessibility events on > hidden views. > > Unfortunately, changing the visibility of the footer view has a side > effect of freeing up space for UiElementContainerView. When this > happens, there is a bit of UI jank when the UiElementContainerView > takes that available space when really that space should permanently be > reserved for the footer. This becomes more obvious in a follow up CL in > which we add a shadow above the footer. > > Now, we don't modify view visibility. Instead, we update focus behavior > as appropriate before animations start and after they end. > > See bug for repro steps. > > Bug: b:113871610 > Change-Id: Ic8aa509c722ace44675a3ab7c7e0453c0aa4a352 > Reviewed-on: https://chromium-review.googlesource.com/1197906 > Commit-Queue: David Black <dmblack@google.com> > Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org> > Cr-Commit-Position: refs/heads/master@{#588926} TBR=xiaohuic@chromium.org,dmblack@google.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: b:113871610 Change-Id: I81f93ff5b641fab87e9b00fffc1c6c428ff44388 Reviewed-on: https://chromium-review.googlesource.com/1216812Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Commit-Queue: David Black <dmblack@google.com> Cr-Commit-Position: refs/heads/master@{#590083}
-
wutao authored
This patch flips the flag of Continue Reading to default on. Bug: 882602, 843839 Test: manual. Change-Id: Idaebea1a12926d1a64482b06af3644e55fc01b4a Reviewed-on: https://chromium-review.googlesource.com/1217593Reviewed-by:
-
Chris Palmer authored
Also embellish the PA API a bit to make accessing the new zero-fill functionality more usable. There are likely additional call sites that can make use of this functionality. Bug: 864462 Change-Id: I8881c5774b6083b210f5160d4b4f2ac345f2467e Reviewed-on: https://chromium-review.googlesource.com/1212443 Commit-Queue: Chris Palmer <palmer@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Hongchan Choi <hongchan@chromium.org> Cr-Commit-Position: refs/heads/master@{#590081}
-
webrtc-chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/b2d711673390..cf64a04acdf3 git log b2d711673390..cf64a04acdf3 --date=short --no-merges --format='%ad %ae %s' 2018-09-10 phoglund@webrtc.org Bump tryserver mac versions and xcode versions. 2018-09-10 mbonadei@webrtc.org Refactor initialization of GetRealTimeClock singleton. 2018-09-10 srte@webrtc.org Adds initial data window field trial to GoogCC. 2018-09-10 henrik.lundin@webrtc.org NetEq tools: Fixing an issue with measuring the simulation time 2018-09-10 aleloi@webrtc.org Added flags for the adaptive analog AGC in audioproc_f. Created with: gclient setdep -r src/third_party/webrtc@cf64a04acdf3 The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_chromium_archive_rel_ng;luci.chromium.try:mac_chromium_archive_rel_ng BUG=chromium:None TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I4a7573ec8ab7da1f4c2404187a965ace673b0590 Reviewed-on: https://chromium-review.googlesource.com/1217153Reviewed-by:
webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#590080}
-
Victor Costan authored
This CL only handles the files in //remoting. The files in //net were tackled in https://crrev.com/c/1188959. Parallel CLs will tackle other directories. net::IOBuffer is (thread-safe) ref-counted. Asides from improving the ability to reason about instance ownership locally, creating instances via base::MakeRefCounted makes it possible to use 1-based ref-counting in the future (see base/memory/ref_counted.h). This CL is mechanical, to avoid introducing any behavior changes. The difficult cases will be tackled by follow-up CLs. The following transformations were performed. * new IOBufferType(args) => base::MakeRefCounted<IOBufferType>(args) * new IOBufferType => base::MakeRefCounted<IOBufferType>() * scoped_refptr x(base::MakeRefCounted<IOBufferType>(args)) => scoped_refptr x = base::MakeRefCounted<IOBufferType>(args) * scoped_refptr<IOBufferType>(base::MakeRefCounted<IOBufferType>(args)) => base::MakeRefCounted<IOBufferType>(args) * In comments: creates a new IOBufferType => creates an IOBufferType (so it wouldn't trigger future searches for "new BufferType") * Instantiated static members in HttpResponseBodyDrainer, HttpNetworkTransaction, HttpProxyClientSocket, WritersTest, UDPSocketTest, TestDelegate, UDPSocketPerfTest (needed to fix linker errors) * arraysize -> base::size (where needed to pass presubmit checks) * git cl format Change-Id: I4feed626ef76c0da3934748ea063ce317ce2ce86 Reviewed-on: https://chromium-review.googlesource.com/1200571Reviewed-by:
Gary Kacmarcik <garykac@chromium.org> Commit-Queue: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#590079}
-
liberato@chromium.org authored
This makes D3D11VideoDecoder use the visible rect from the H264 decoder when constructing a VideoFrame. Change-Id: Ic8a3095a86bb9282a6d1fcf06aed1cf6aeef60d7 Reviewed-on: https://chromium-review.googlesource.com/1217354Reviewed-by:
Dan Sanders <sandersd@chromium.org> Commit-Queue: Frank Liberato <liberato@chromium.org> Cr-Commit-Position: refs/heads/master@{#590078}
-
catapult-chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/77a15654a753..03c80a36415d git log 77a15654a753..03c80a36415d --date=short --no-merges --format='%ad %ae %s' 2018-09-10 benjhayden@chromium.org Add scalar-span for v2spa Created with: gclient setdep -r src/third_party/catapult@03c80a36415d The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. 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_optional_gpu_tests_rel TBR=sullivan@chromium.org Change-Id: I10cddb8fe7c7773d73152b86fa15cc760c6f09e5 Reviewed-on: https://chromium-review.googlesource.com/1216869Reviewed-by:
catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#590077}
-
Victor Costan authored
This CL only handles the difficult cases in //remoting. The easy cases were tackled by mechanical CLs, such as https://crrev.com/c/1188959 for //net. Parallel CLs will tackle other difficult cases. net::IOBuffer is (thread-safe) ref-counted. Asides from improving the ability to reason about instance ownership locally, creating instances via base::MakeRefCounted makes it possible to use 1-based ref-counting in the future (see base/memory/ref_counted.h). This CL replaces raw IOBuffer pointers with scoped_refptr<net::IOBuffer> in some APIs. Local inspection of the impacted implementations should reveal that no extra reference churn was introduced. Change-Id: I59940c49e6635540a4a42840919ff114b3a1941f Reviewed-on: https://chromium-review.googlesource.com/1215463Reviewed-by:
-
Victor Costan authored
This CL only handles a difficult case in //jingle. The easy cases were tackled by mechanical CLs, such as https://crrev.com/c/1188959 for //net. Parallel CLs will tackle other difficult cases. ability to reason about instance ownership locally, creating instances via base::MakeRefCounted makes it possible to use 1-based ref-counting in the future (see base/memory/ref_counted.h). net: :IOBuffer is (thread-safe) ref-counted. Asides from improving the Change-Id: I06317e9410389b226fbe7818c8d7138d5bb79050 Reviewed-on: https://chromium-review.googlesource.com/1215464Reviewed-by:
Nicolas Zea <zea@chromium.org> Commit-Queue: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#590075}
-
Pedro Amaral authored
Bug: 876051 Change-Id: I7826a815732a64d4b728be2f6b8565c5259f974c Reviewed-on: https://chromium-review.googlesource.com/1217585 Commit-Queue: Pedro Amaral <amaralp@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Cr-Commit-Position: refs/heads/master@{#590074}
-
Ojan Vafai authored
This reverts commit 0962c66c. Reason for revert: This test also fails on some mac bots, e.g. https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac10.12%20Tests/15266 Original change's description: > Implement crash report prototype (behind flag) > > This patch implements crash reporting, as detailed in the > reporting spec: https://w3c.github.io/reporting/#crash-report > > Change-Id: I209880150193910a0947608e6b08a6eeea29206c > Reviewed-on: https://chromium-review.googlesource.com/1174965 > Commit-Queue: Paul Meyer <paulmeyer@chromium.org> > Reviewed-by: Nick Carter <nick@chromium.org> > Reviewed-by: Avi Drissman <avi@chromium.org> > Cr-Commit-Position: refs/heads/master@{#589941} TBR=avi@chromium.org,nick@chromium.org,paulmeyer@chromium.org Change-Id: I52ea9472a94c7c5eaa13e29dcd3569e0db3c8280 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/1217513Reviewed-by:
Ojan Vafai <ojan@chromium.org> Commit-Queue: Ojan Vafai <ojan@chromium.org> Cr-Commit-Position: refs/heads/master@{#590073}
-
Jani Hautakangas authored
Refactor base/ime components and dependencies for ozone plaform integration to avoid cyclic dependencies. - Groups ui/base/ime common types into their own GN component (ime_types) to break a dependency cycle that ozone ime context integration would cause on ChromeOS. - Groups some of ui/base/ime/linux interfaces into their own GN component (ime_linux) to break a dependency cycle that ozone ime context integration would cause on ChromeOS. - Move chromeos source files under is_chromeos flag to avoid depending them when chromeos is not used, but ime is needed (kudos to msisov@igalia.com). Bug: 791920 Change-Id: I0b1668564dde22c6e2b05ee1323ebbe4a1343475 Reviewed-on: https://chromium-review.googlesource.com/1193871 Commit-Queue: Jani Hautakangas <jani.hautakangas@lge.com> Reviewed-by:
Shu Chen <shuchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#590072}
-
khmel@chromium.org authored
This reverts commit 37385434. (Test flakiness fixed) When app is pinned, icon image is loaded via controller using loader owner by chrome launcher controller. Once new ARC app window appears in the system, it's icon is loaded asynchronously. In this flow, default app icon is applied first and then, once real image is loaded final icon is set. Each update of ARC window icon is reflected on shelf. That means default app icon appear on the shelf for a moment and in most cases this is very noticeable. This CL prevents setting default app in favor of final app icon and default icon is set only as a fallback when final icon could not be loaded. TEST=Manual BUG=882048 BUG=882043 Bug: b:114246197 TBR=xiyuan@chromium.org,jdonnelly@chromium.org,khmel@google.com # Not skipping CQ checks because original CL landed > 1 day ago. Change-Id: Ic2015afe42b4b3aacd05a307350e643a6967d3e8 Reviewed-on: https://chromium-review.googlesource.com/1216721 Commit-Queue: Yury Khmel <khmel@chromium.org> Reviewed-by:
Yury Khmel <khmel@chromium.org> Cr-Commit-Position: refs/heads/master@{#590071}
-
Varun Khaneja authored
Bug: 754341 Change-Id: Ib8dcfcba25ea2f563365fca13f79873499639c52 Reviewed-on: https://chromium-review.googlesource.com/1211979Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Reviewed-by:
Nathan Parker <nparker@chromium.org> Commit-Queue: Varun Khaneja <vakh@chromium.org> Cr-Commit-Position: refs/heads/master@{#590070}
-
Bailey Berro authored
Currently, we wait until the first batch of shares is returned from host discovery before attempting to Mount a share so that name resolution can be performed. This change switches to using the GatherSharesInNetwork method that takes a HostDiscoveryResponse callback so that the delay is shortened. Bug: chromium:757625 Change-Id: I22cf5fd48bdcc633fa4d7f2f08b1e6f7e10af764 Reviewed-on: https://chromium-review.googlesource.com/1211947 Commit-Queue: Bailey Berro <baileyberro@chromium.org> Reviewed-by:
Scott Chen <scottchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#590069}
-
Weilun Shi authored
Add button should be hidden when there are max number of most visited tiles. Bug: 881091 Change-Id: I40d33e533691885204f1fd813ce077fb060678d9 Reviewed-on: https://chromium-review.googlesource.com/1214180 Commit-Queue: Weilun Shi <sweilun@chromium.org> Reviewed-by:
Kristi Park <kristipark@chromium.org> Cr-Commit-Position: refs/heads/master@{#590068}
-
Aiden Benner authored
e.g. public int x = 0; public boolean x = false; - Adds errorprone rule that will detect when fields are initialized to default values (results in larger class sizes and can't be optimized away see https://issuetracker.google.com/issues/37124982) - Refactor current redundant initializations - Fix cases where classes were being generated with redundant initializations TBR=agrieve Bug: 878853 Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;master.tryserver.chromium.android:android_cronet_tester Change-Id: Ia76a02ea73a55f2fa66b4ef6461ac985eba574bb Reviewed-on: https://chromium-review.googlesource.com/1209547 Commit-Queue: agrieve <agrieve@chromium.org> Reviewed-by:agrieve <agrieve@chromium.org> Reviewed-by:
Peter Wen <wnwen@chromium.org> Cr-Commit-Position: refs/heads/master@{#590067}
-
depot-tools-chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/d91f0adca280..11bc3991530d git log d91f0adca280..11bc3991530d --date=short --no-merges --format='%ad %ae %s' 2018-09-10 nodir@google.com [bot_update] add ignore_input_commit parameter Created with: gclient setdep -r src/third_party/depot_tools@11bc3991530d The AutoRoll server is located here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. BUG=chromium:882094 TBR=agable@chromium.org Change-Id: I189dbf46abcf77ef9ad2fb1362d82c03777f67a2 Reviewed-on: https://chromium-review.googlesource.com/1216868Reviewed-by:
depot-tools-chromium-autoroll <depot-tools-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: depot-tools-chromium-autoroll <depot-tools-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#590066}
-
Luna Lu authored
Design doc: https://docs.google.com/document/d/1yh_-ayeaFV0EjuR51U641zbrPAB0Baqj6UrC9bT9iqQ/edit#heading=h.y7amr11fn0tb This CL implements "intrinsicSize" attribute to SVGImageElement. This attribute has been added to HTMLImageElement and HTMLVideoElement. The value of "intrinsicSize" overrides the intrinsic size: 1. When no width and height is specified, the value of "intrinsicSize" specifies the <svg:image> element's layout size. 2. When one dimension is specified, the value of "intrinsicSize" is used as an aspect ratio to determine the other dimension. 3. If both width and height are specified, "intrinsicSize" has no effect. Bug: 874629 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I9023d6cf7a818c983155efc12505f1d6fd18de43 Reviewed-on: https://chromium-review.googlesource.com/1210544Reviewed-by:
Steve Kobes <skobes@chromium.org> Commit-Queue: Luna Lu <loonybear@chromium.org> Cr-Commit-Position: refs/heads/master@{#590065}
-
Eugene But authored
Experiment results were collected in M69. Bug: 853774 Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs Change-Id: I44d71ec5a620b8ac5b9673161dbf9172cfc67fdf Reviewed-on: https://chromium-review.googlesource.com/1213268Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Commit-Queue: Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#590064}
-
Alex Moshchuk authored
Previously isolated origins were stored in a set. This resulted in large overheads when URLs needed to be checked against isolated origins, since the set had to be walked through linearly, running a fairly slow comparison function (IsolatedOriginUtil::DoesOriginMatchIsolatedOrigin()) on each isolated origin, and this lookup turned out to be fairly common. This CL reorganizes the underlying data structure into a map keyed by site URLs. For example, if we add {https://foo.com, https://bar.foo.com, https://www.bar.com} as isolated origins, the map will look like this: https://foo.com -> { https://foo.com, https://bar.foo.com } https://bar.com -> { https://www.bar.com } When checking a URL against isolated origins, we now can just look up the map using the URL's site and then look for the most specific isolated origins as before. The site can be found in O(log n) time, and the corresponding list of origins to search using DoesOriginMatchIsolatedOrigin() changes from O(n) to O(originsPerSite), which is expected to be ~1. Bug: 877653 Change-Id: I41667f94cea7f1f8e5b53fa23443d83cfbb3c0ed Reviewed-on: https://chromium-review.googlesource.com/1208942 Commit-Queue: Alex Moshchuk <alexmos@chromium.org> Reviewed-by:Łukasz Anforowicz <lukasza@chromium.org> Reviewed-by:
Charlie Reis <creis@chromium.org> Cr-Commit-Position: refs/heads/master@{#590063}
-
