- 05 Jan, 2019 13 commits
-
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/599dad1eadaf..1457e48474e7 git log 599dad1eadaf..1457e48474e7 --date=short --no-merges --format='%ad %ae %s' 2019-01-04 vapier@chromium.org cros_extract_deps: sort output 2019-01-04 vapier@chromium.org cros_extract_deps: clean up cli parser a bit Created with: gclient setdep -r src/third_party/chromite@1457e48474e7 The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-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=chrome-os-gardeners@chromium.org Change-Id: I340c72f4d78eb5543dc4de920119184819383741 Reviewed-on: https://chromium-review.googlesource.com/c/1396685Reviewed-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@{#620127}
-
Dmitry Gozman authored
After we started calling CreatePlaceholderDocumentLoader [1] for empty-document navigations, existing logic which checks for placeholder DL handles the case of empty documents as well. [1] https://chromium-review.googlesource.com/c/chromium/src/+/1380552 Bug: none Change-Id: I2b1f9d73e00cd8ed3ab1f3f7f54ea930930c35dd Reviewed-on: https://chromium-review.googlesource.com/c/1390236Reviewed-by:
Nate Chapin <japhet@chromium.org> Commit-Queue: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#620126}
-
Zhiqiang Zhang authored
There was a crash in SDK before version 16.0.2. This CL works around the issue by generating the low-level message directly. Bug: 711860 Change-Id: I262143fae845ae6e8d4f9042487f554f7f5d94a1 Reviewed-on: https://chromium-review.googlesource.com/c/1396380Reviewed-by:
Thomas Guilbert <tguilbert@chromium.org> Commit-Queue: Zhiqiang Zhang <zqzhang@chromium.org> Cr-Commit-Position: refs/heads/master@{#620125}
-
Takuto Ikuta authored
base::hash_map is alias of std::unordered_map now. I applied following command to make this CL. $ git grep -l 'base::hash_map' | fgrep -v base/ | xargs sed -i -e 's/base::hash_map/std::unordered_set/g' -e 's/\(#include <[a-z_]*>\)/\1\n#include <unordered_map>/' -e 's/BASE_HASH_NAMESPACE/std/' $ git cl format $ # Added IntPairHash and replaced BASE_HASH_NAMESPACE with std in some places. TBR: dcheng@chromium.org Bug: 576864 Change-Id: I38941d9f9bcb05ec474b8dee5230c4c5dcd2211f Reviewed-on: https://chromium-review.googlesource.com/c/1390892 Commit-Queue: Takuto Ikuta <tikuta@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#620124}
-
Ryan Tseng authored
It looks like someone added these builders to buildbot after I mirrored chromium.clang, but did not add the LUCI entries. This will fix the console. Bug: 919081 Change-Id: I3839c9aad4e4570ba9963546da5d57acd1657dcf Reviewed-on: https://chromium-review.googlesource.com/c/1396492 Commit-Queue: Eric Foo <efoo@chromium.org> Commit-Queue: Ryan Tseng <hinoka@chromium.org> Reviewed-by:
Eric Foo <efoo@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#620123}
-
Daniel Rubery authored
These are multi-part rar archives, and should be inspected as such. Bug: 919157 Change-Id: I53ee4aea51f33d7283772e2987fa2ffd66c92e6d Reviewed-on: https://chromium-review.googlesource.com/c/1396558Reviewed-by:
Nathan Parker <nparker@chromium.org> Commit-Queue: Daniel Rubery <drubery@chromium.org> Cr-Commit-Position: refs/heads/master@{#620122}
-
Peter Kasting authored
This allows shortening a lot of copy-and-pasted code. A few places cannot be converted yet and will be handled in a subsequent CL. Bug: none Change-Id: I3b9dc34f55c287cac09621f251bcaf5221ad8bc4 TBR: kylixrd Reviewed-on: https://chromium-review.googlesource.com/c/1396788Reviewed-by:
Peter Kasting <pkasting@chromium.org> Commit-Queue: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#620121}
-
Domenic Denicola authored
Follows https://github.com/domenic/async-local-storage/commit/5bf31109f37d1371f619ea33d0e2391f10e8b8f5, and includes web platform test updates. Bug: 918704 Change-Id: Ibc99816d10dba457194ff9e651ead9fc07bd6537 Reviewed-on: https://chromium-review.googlesource.com/c/1393704Reviewed-by:
Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Commit-Queue: Domenic Denicola <domenic@chromium.org> Cr-Commit-Position: refs/heads/master@{#620120}
-
Chris Harrelson authored
This reduces the size of a LayoutBox or InlineFlowBox without overflow by one pointer. Change-Id: I3461f44950ad29f9ab1c66b10ce0f921ab010c10 Reviewed-on: https://chromium-review.googlesource.com/c/1396332 Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Reviewed-by:
Aleks Totic <atotic@chromium.org> Cr-Commit-Position: refs/heads/master@{#620119}
-
Sreerenj Balachandran authored
The Vp9Parser::ParseNextFrame() may get invoked with null decrypt_config, so make sure to not to do the null poitner dereferencing. Change-Id: Idd459377ef78e16b8262e61174165c0dc52d3ead Reviewed-on: https://chromium-review.googlesource.com/c/1396479Reviewed-by:
Chrome Cunningham <chcunningham@chromium.org> Commit-Queue: Sreerenj Balachandran <sreerenj.balachandran@intel.com> Cr-Commit-Position: refs/heads/master@{#620118}
-
Alex Moshchuk authored
GetRequestInitiatorSiteLock currently calls ShouldLockToOrigin, but that check is redundant for one of its call sites from RenderProcessHostImpl, which only calls GetRequestInitiatorSiteLock for valid, non-empty process locks. This CL moves the ShouldLockToOrigin call to the other call site in RenderFrameHostImpl. This removes GetRequestInitiatorSiteLock's dependency on ShouldLockToOrigin params, which helps prepare for the dynamic isolated origin plumbing to be introduced in https://chromium-review.googlesource.com/c/chromium/src/+/1377616. Bug: 905513 Change-Id: I4f64bd71370f67536c37156274ea578745c56e0e Reviewed-on: https://chromium-review.googlesource.com/c/1396450Reviewed-by:
Łukasz Anforowicz <lukasza@chromium.org> Commit-Queue: Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#620117}
-
Esmael El-Moslimany authored
Bug: 862839 Change-Id: Ie85e1abe1958665fef83f25c1eb3d437a2555f7b Reviewed-on: https://chromium-review.googlesource.com/c/1396168Reviewed-by:
Dan Beam <dbeam@chromium.org> Commit-Queue: Esmael El-Moslimany <aee@chromium.org> Cr-Commit-Position: refs/heads/master@{#620116}
-
Chris Harrelson authored
This is merely a performance optimization, with unclear benefits, and adds complication. Change-Id: Ibda65f18145bef919639d89fc0e36647e5aec3e4 Reviewed-on: https://chromium-review.googlesource.com/c/1395816Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#620115}
-
- 04 Jan, 2019 27 commits
-
-
Brandon Jones authored
This is the first step to removing XRDevice entirely. Bug: 916287 Change-Id: Ie5f86738632636927a822c6ccbecba3202446d41 Reviewed-on: https://chromium-review.googlesource.com/c/1383391Reviewed-by:
Brian Sheedy <bsheedy@chromium.org> Reviewed-by:
Miguel Casas <mcasas@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Brandon Jones <bajones@chromium.org> Cr-Commit-Position: refs/heads/master@{#620114}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/20cbd600de8b..f6b46a78785b Created with: gclient setdep -r src-internal@f6b46a78785b The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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=mmoss@chromium.org Change-Id: Ie31108c237887f2fa455ece6eb1fb3fc02dd1784 Reviewed-on: https://chromium-review.googlesource.com/c/1395827Reviewed-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@{#620113}
-
Hector Carmona authored
R=dpapad@chromium.org Bug: NONE Change-Id: I73051130e3a8d8f0791ac172666b179a29de4dd9 Reviewed-on: https://chromium-review.googlesource.com/c/1395815Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Hector Carmona <hcarmona@chromium.org> Cr-Commit-Position: refs/heads/master@{#620112}
-
Sandra Sun authored
Currently, the duration of programmatic smooth scroll curves depend on the distance of the scroll delta. However, it could be considerably long for long pages. This patch sets an upper-limit of 3 seconds for the programmatic smooth scrolls. For shorter scrolls, the duration would still be related to the delta. Bug: 852549 Change-Id: Idbb95a15b7440a16c3e3632f063daa7b7e8fe705 Reviewed-on: https://chromium-review.googlesource.com/c/1396493 Commit-Queue: David Bokan <bokan@chromium.org> Reviewed-by:
David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#620111}
-
Ryan Meier authored
Bug: 913227 Change-Id: Ic2e96b96bd9239c39ffe5023d5b6aa7465f91558 Reviewed-on: https://chromium-review.googlesource.com/c/1396496 Commit-Queue: Ryan Meier <rameier@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#620110}
-
Philip Rogers authored
In [1], main thread scrolling reasons were moved from cc::Layer to cc::ScrollNode. That patch missed a case where painted scrollbar layers always set main thread scrolling reasons for non-overlay scrollbars. This is not possible to support with main thread reasons on ScrollNode because it would force main thread scrolling for the entire scroll layer. This functionality is not actually needed anymore because LayerTreeHostImpl::ScrollBegin now falls back to the main thread when touch-dragging a scrollbar. LayerTreeHostImplTestMultiScrollable::ScrollHitTestOnScrollbar tests the main codepath for falling back to the main thread when touch-dragging. I also manually checked that touch-scrolling on the scrollbar and thumb work as expected with this patch. [1] https://crrev.com/617642 Bug: 918699 Change-Id: If8c9cf528639266e49956c5513c2a04b23829622 Reviewed-on: https://chromium-review.googlesource.com/c/1396439Reviewed-by:
David Bokan <bokan@chromium.org> Commit-Queue: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#620109}
-
CJ DiMeglio authored
This CL changes the caption button to use by aria attributes instead of explicitly creating accessibility nodes. It also eliminates some of the duplicate information heard in TalkBack. Bug: 836549 Change-Id: If22a232bc67d2e64148b2cfa5ff48da9bd33e855 Reviewed-on: https://chromium-review.googlesource.com/c/1375396Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: CJ DiMeglio <lethalantidote@chromium.org> Cr-Commit-Position: refs/heads/master@{#620108}
-
Hector Carmona authored
Bug: 919140 Change-Id: Ifc5c680e5e48afd4b0f75d260cd6c277350d5d7b Reviewed-on: https://chromium-review.googlesource.com/c/1396712Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Hector Carmona <hcarmona@chromium.org> Cr-Commit-Position: refs/heads/master@{#620107}
-
Caroline Rising authored
Bug: 910739 Change-Id: I3ab7dd42d8f74806f427acea15257879c810787a Reviewed-on: https://chromium-review.googlesource.com/c/1394439Reviewed-by:
Peter Boström <pbos@chromium.org> Commit-Queue: Caroline Rising <corising@chromium.org> Cr-Commit-Position: refs/heads/master@{#620106}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/dde2a376f7cd..8061ba857072 git log dde2a376f7cd..8061ba857072 --date=short --no-merges --format='%ad %ae %s' 2019-01-04 recipe-roller@chromium.org Roll recipe dependencies (trivial). 2019-01-04 benjaminwagner@google.com Add IntelIris655 Win10 jobs. 2019-01-04 kjlubick@google.com [pathkit] Increase test timeouts (for asmjs mostly) 2019-01-04 csmartdalton@google.com ccpr: Rework the path cache to support sporadic flushing 2019-01-04 fmalita@chromium.org [skjson] NaN while parsing long decimals 2019-01-04 kjlubick@google.com [pathkit] Add .ready() to initialize 2019-01-04 ethannicholas@google.com Fixed GL shader link status checks 2019-01-04 kjlubick@google.com [canvaskit] Add .ready() which is a real promise 2019-01-04 reed@google.com change paint serialization to exclude font-related fields Created with: gclient setdep -r src/third_party/skia@8061ba857072 The AutoRoll server is located here: https://autoroll.skia.org/r/skia-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-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;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=bungeman@chromium.org Change-Id: I34a76f063f20033f4683319ca6f0d1ca942c6b90 Reviewed-on: https://chromium-review.googlesource.com/c/1396363Reviewed-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@{#620105}
-
Collin Baker authored
FileSelectHelper::OnListDone(), which is called when directory listing is complete, launches an upload confirmation dialog associated with the WebContents the upload request originated from. It does not consider the case where the WebContents has been destroyed. FileSelectHelper already handles the WebContentsDestroyed message, and sets its web_contents_ member to null accordingly. All that needs to be done is cleanup and an early return in OnListDone() if web_contents_ is null. Bug: 916529 Change-Id: Ic362c42a72a2c83bf21ad798d4b05c080c4b972f Reviewed-on: https://chromium-review.googlesource.com/c/1395138Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Collin Baker <collinbaker@chromium.org> Cr-Commit-Position: refs/heads/master@{#620104}
-
James Cook authored
This reverts commit badd8a0f. Reason for revert: Breaks the Wi-Fi network password entry field http://crbug.com/919183 Original change's description: > chromeos: Enable SingleProcessMash (in-proc window service) by default > > Turns on the window service (code in //services/ws) and uses it to back > aura and views (code in //ui/aura/mus and //ui/views/mus). Runs the > window service in-process. > > A label "SingleProcessMash enabled" will appear on the desktop > wallpaper to let developers and QA know the feature is enabled. > The label will be removed in a separate CL before this feature > goes to dev channel. Otherwise there are no visible changes. > > Flips the former "single_process_mash_*" bot configs to > "non_single_process_mash_*" and runs them with the feature disabled. > This should keep the old code paths working until we're sure this > feature will stick. > > TBR=sky@chromium.org > > BUG=918537 > TEST=single_process_mash_* bots > > Change-Id: I58a30fd81ea12645b1aabc049c7e697ef1d9e72a > Reviewed-on: https://chromium-review.googlesource.com/c/1393467 > Reviewed-by: Jun Mukai <mukai@chromium.org> > Reviewed-by: James Cook <jamescook@chromium.org> > Commit-Queue: James Cook <jamescook@chromium.org> > Cr-Commit-Position: refs/heads/master@{#619508} TBR=jamescook@chromium.org,mukai@chromium.org,sky@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 918537, 919183 Change-Id: Ic3b5f0dd5b941d6383fd7290a0a55b60eedce30d Reviewed-on: https://chromium-review.googlesource.com/c/1396702Reviewed-by:
James Cook <jamescook@chromium.org> Reviewed-by:
Jun Mukai <mukai@chromium.org> Commit-Queue: James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#620103}
-
Becca Hughes authored
This changes MediaSession to be controllable if we have set a playback state through the routed service. This is to fix cases where a site may not be controllable if the media is shorter than 7 seconds but we want it to be controllable (e.g. if it is a media app). BUG=902519 Change-Id: I86ef8ffca0fb6a3e6c11b2ca90e2a3c020cb9d70 Reviewed-on: https://chromium-review.googlesource.com/c/1393444 Commit-Queue: Becca Hughes <beccahughes@chromium.org> Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Cr-Commit-Position: refs/heads/master@{#620102}
-
Joey Arhar authored
window.applicationCache isn't available within DevTools after http://crrev.com/c/1160644/ so we can't use it for status constants. Bug: 892562 Change-Id: Icbd33c345003595f090558fdb2ce7312f54ba93a Reviewed-on: https://chromium-review.googlesource.com/c/1396615Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Joey Arhar <jarhar@chromium.org> Cr-Commit-Position: refs/heads/master@{#620101}
-
Matthew Wolenetz authored
This reverts commit 919d2dee. Reason for revert: Strongly suspected as culprit in regressed blink web_tests: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/WebKit%20Linux%20Trusty%20ASAN/19960: media_capabilities/encodingInfo.html https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/WebKit%20Linux%20Trusty%20Leak/28348: media_capabilities/encodingInfo.html fast/mediarecorder/MediaRecorder-isTypeSupported.html Original change's description: > MediaRecorder: only announce h264/avc1 support if RTC_USE_H264 > > Support for AVC1 encoding (a.k.a. H264) is dependent on RTC_USE_H264 [1], > but due to an omission, this was not tested when enumerating the video > codecs. This CL fixes that. > > [1] https://cs.chromium.org/chromium/src/third_party/webrtc/webrtc.gni?type=cs&q=rtc_use_h264&sq=package:chromium&g=0&l=156 > > TBR=emircan@chromium.org > > Bug: 809980, 719023 > Change-Id: I03a375b269b042cb8cf64680153b878f60ea723f > Reviewed-on: https://chromium-review.googlesource.com/c/1395887 > Commit-Queue: Miguel Casas <mcasas@chromium.org> > Reviewed-by: Miguel Casas <mcasas@chromium.org> > Cr-Commit-Position: refs/heads/master@{#620078} TBR=mcasas@chromium.org,mbarowsky@chromium.org Change-Id: I59b3a89c5a2e6c41c589617a3ab4d3f66b53dfa2 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 809980, 719023 Reviewed-on: https://chromium-review.googlesource.com/c/1396716Reviewed-by:
Matthew Wolenetz <wolenetz@chromium.org> Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org> Cr-Commit-Position: refs/heads/master@{#620100}
-
khachatryan authored
Tests 'ChromeDriverTest.testTakeElementScreenshot' and 'ChromeDriverTest.testTakeElementScreenshotInIframe' are flaky on Waterfall for Mac platform. Disabling those tests. Bug: chromedriver:2579 Change-Id: Iee1675d6bd7d1c8cbed266ae5e2b56495c9d42a5 Reviewed-on: https://chromium-review.googlesource.com/c/1396698Reviewed-by:
John Chen <johnchen@chromium.org> Commit-Queue: Artur Khachatryan <khachatryan@chromium.org> Cr-Commit-Position: refs/heads/master@{#620099}
-
Lukasz Anforowicz authored
r589029 changed bucketing of some navigation-timing histograms, and broke data continuity. To fix things going forward, the re-bucketed histograms need to be renamed. The old CL changed the overflow-bucket boundary of the following histograms to 3 minutes: 1. Navigation.TimeToReadyToCommit.* 2. Navigation.StartToCommit.* 3. Navigation.ReadyToCommitUntilCommit.* Histogram #2 above wasn't affected (the old overflow-bucket boundary was already at 3 minutes). Histograms #1 and #3 need to have their names changed - the current CL is adding a "2" suffix: - Navigation.TimeToReadyToCommit2.* - Navigation.ReadyToCommitUntilCommit2.* Bug: 848821 Change-Id: I6029d88df863ba3ed3edd2327c46f4ec20e6ce6d Reviewed-on: https://chromium-review.googlesource.com/c/1394783Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Cr-Commit-Position: refs/heads/master@{#620098}
-
John Chen authored
Increase ChromeDriver's HTTP server listen queue length, to avoid losing connection requests when they arrive too close to each other. Bug: chromedriver:2714 Change-Id: I9af6e74c415054a1e000b24c2a55bbb1fd64221a Reviewed-on: https://chromium-review.googlesource.com/c/1396306Reviewed-by:
Caleb Rouleau <crouleau@chromium.org> Commit-Queue: John Chen <johnchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#620097}
-
Peter Kasting authored
No code change, this just modifies the order of lines in the file. Bug: none Change-Id: I2bf05f0864adb514fd935a20dcc247e709d033a2 TBR: kylixrd Reviewed-on: https://chromium-review.googlesource.com/c/1395895Reviewed-by:
Peter Kasting <pkasting@chromium.org> Commit-Queue: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#620096}
-
dpapad authored
This is in preparation of converting more var to let/const. Bug: 792774 Change-Id: I2b6ab4b92c3a81e775051ed535ffec1e88b2adc2 Reviewed-on: https://chromium-review.googlesource.com/c/1396477Reviewed-by:
Dan Beam <dbeam@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#620095}
-
Nasko Oskov authored
Browser Side Navigation (aka PlzNavigate) has been the only navigation code path since M65, so IsBrowserSideNavigationEnabled is a redundant method. This CL removes the last usage of it. Since the last test gated by it is failing, I've just move it to DISABLED_ rather than using the policy function, which semantically does the same thing. Bug: 789577 Change-Id: I8e4050d382a897929a6c8c5555d2bf4a25d2fc53 Reviewed-on: https://chromium-review.googlesource.com/c/1396302Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Commit-Queue: Nasko Oskov <nasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#620094}
-
Jason Guo authored
Bug: 867194 Change-Id: Ia32daa689317612438f4bab35eb3d0546df72de9 Reviewed-on: https://chromium-review.googlesource.com/c/1372480Reviewed-by:
Jared Saul <jsaul@google.com> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Reviewed-by:
Evan Stade <estade@chromium.org> Commit-Queue: Jason Guo <jiahuiguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#620093}
-
Tom Anderson authored
This is a reland of 1a874fe6 Original change's description: > Roll buildtools and enable in-tree libc++ on Android > > Buildtools changelog: > https://chromium.googlesource.com/chromium/buildtools/+log/7d88270de197ebe8b439ab5eb57a4a2a0bb810e0..0e1cbc4eab6861b0c84bf2ed9a3c4b7aa2063819 > > BUG=767901 > R=thakis > > Change-Id: I96fdafca5e228cbfe7a0909170c0235e7845bbde > Reviewed-on: https://chromium-review.googlesource.com/c/1385021 > Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> > Commit-Queue: Nico Weber <thakis@chromium.org> > Reviewed-by: Nico Weber <thakis@chromium.org> > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > Cr-Commit-Position: refs/heads/master@{#618035} Bug: 767901 Change-Id: I17d2e4fe9661cfe3470fce0fc1099f73d801bd32 Reviewed-on: https://chromium-review.googlesource.com/c/1394229 Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#620092}
-
Roger McFarlane authored
This CL removes expires-after="M73" for the following histograms: Autofill.Upload.BackoffDelay Autofill.Upload.HttpResponseOrErrorCode Autofill.Upload.RequestDuration These histograms continue, and will continue, to be of value and should not expire. In particular, these histograms will be of use when comparing the autofill canary server environment users with the prod environment control group. Bug: 915888 Change-Id: I99d56ca36997c38f4bb691c601fdb18f10289554 Reviewed-on: https://chromium-review.googlesource.com/c/1396328Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Commit-Queue: Roger McFarlane <rogerm@chromium.org> Cr-Commit-Position: refs/heads/master@{#620091}
-
Josh Nohle authored
Add protos that will be needed for the CryptAuth v2 Enrollment protocol. These are copies of files already used by the CryptAuth backend. Bug: 899080 Change-Id: I0ad036e37bce9104130c9aaf72edea635f67b50d Reviewed-on: https://chromium-review.googlesource.com/c/1395812Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Commit-Queue: Josh Nohle <nohle@chromium.org> Cr-Commit-Position: refs/heads/master@{#620090}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/e4109f27136d..9db8df4c3e6e git log e4109f27136d..9db8df4c3e6e --date=short --no-merges --format='%ad %ae %s' 2019-01-04 thakis@chromium.org Slightly simplify .def file use. Created with: gclient setdep -r src/third_party/angle@9db8df4c3e6e The AutoRoll server is located here: https://autoroll.skia.org/r/angle-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: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=syoussefi@chromium.org Change-Id: Idee8fc80a2fed8f510a16bce31b43f33acc7c33a Reviewed-on: https://chromium-review.googlesource.com/c/1395824Reviewed-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@{#620089}
-
Antoine Labour authored
Some previous changes left pp_macros.h in an inconsistent state. Also fixup the generator so that il makes git cl format a noop on it. Bug: 918951 Change-Id: I0f9bac70831b95e9a1a6ee7b9ba47dd62a88baa4 Reviewed-on: https://chromium-review.googlesource.com/c/1396609Reviewed-by:
Bill Budge <bbudge@chromium.org> Commit-Queue: Antoine Labour <piman@chromium.org> Cr-Commit-Position: refs/heads/master@{#620088}
-