- 08 Oct, 2018 40 commits
-
-
Colin Blundell authored
Will be needed by multiple clients for converting away from ProfileOAuth2TokenService. Bug: 882861 Change-Id: Ie648a701a02d34e786703604cb8d1f7f080202bc Reviewed-on: https://chromium-review.googlesource.com/c/1267499Reviewed-by:
David Roger <droger@chromium.org> Commit-Queue: Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/master@{#597558}
-
Henrik Grunell authored
This reverts commit 96b1bcfd. Reason for revert: Broke audio on Win 7 and Win 8. The audio debug recording tests failed here https://ci.chromium.org/buildbot/chromium.webrtc/Win7%20Tester/ and they only broke on Win 7 and 8. When testing ToT build on a Win 7 machine is no audio output. Tested AppRTC, Youtube and onlinemictest.com/sound-test. Canary on the same machine works. This CL is the only in the range that's suspicious. Andrew, let me know if you believe this is incorrect. Original change's description: > Windows 10 low-latency audio API > > Implement the IAudioClient3 interface to allow lower output latency > for use in Web Audio via the latencyHint. Update AudioParameters > adding HardwareCapabilities with min_ and max_frames_per_buffer > representing the min and max buffer sizes supported by the audio > hardware so that requested buffer sizes can be appropriately clamped > in AudioLatency::GetExactBufferSize(). > > Bug: 316908 > 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: Ibafe6d917ec4d57a16092f040b57b4ff27ed54b3 > Reviewed-on: https://chromium-review.googlesource.com/c/1165236 > Reviewed-by: Robert Liao <robliao@chromium.org> > Reviewed-by: Will Harris <wfh@chromium.org> > Reviewed-by: Olga Sharonova <olka@chromium.org> > Reviewed-by: Dale Curtis <dalecurtis@chromium.org> > Reviewed-by: Max Morin <maxmorin@chromium.org> > Commit-Queue: Andrew MacPherson <andrew.macpherson@soundtrap.com> > Cr-Commit-Position: refs/heads/master@{#597497} TBR=dalecurtis@chromium.org,robliao@chromium.org,kerrnel@chromium.org,olka@chromium.org,wfh@chromium.org,maxmorin@chromium.org,ossu@chromium.org,andrew.macpherson@soundtrap.com Change-Id: I7c76029c435b7434463734baa9a2b21469399c8a No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 316908 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 Reviewed-on: https://chromium-review.googlesource.com/c/1268280Reviewed-by:
Henrik Grunell <grunell@chromium.org> Commit-Queue: Henrik Grunell <grunell@chromium.org> Cr-Commit-Position: refs/heads/master@{#597557}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/2e00abc98e59..6a8327fc823d git log 2e00abc98e59..6a8327fc823d --date=short --no-merges --format='%ad %ae %s' 2018-10-08 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision ccb83d4a..0cdd2e3e (597330:597498) 2018-10-08 srte@webrtc.org Reland "Reland "Using units in SendSideBandwidthEstimation."" 2018-10-08 perkj@webrtc.org Changed FakeVp8Encoder to write dimensions in payload. 2018-10-08 srte@webrtc.org Revert "Reland "Using units in SendSideBandwidthEstimation."" 2018-10-08 srte@webrtc.org Reland "Using units in SendSideBandwidthEstimation." 2018-10-08 oprypin@webrtc.org Revert "Using units in SendSideBandwidthEstimation." Created with: gclient setdep -r src/third_party/webrtc@6a8327fc823d 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,chromium:none TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I23b504ce3d525570f708cdb268bd414d9d385fb4 Reviewed-on: https://chromium-review.googlesource.com/c/1267686Reviewed-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@{#597556}
-
Mark Pearson authored
I'm sad it took me so long to prepare this changelist. When I created it, there was a test failure, which I couldn't immediately identify the cause of. And it didn't seem that imperative to finish quickly, so it got postponed again and again. Finally I looked into it. The test failure was due to am inappropriate test, not any problem with the feature. This means I could've launched this months ago if I'd been more attentive. :-( The test scored_history_match_unittest failed because, with the flag enabled, the #hash_component part of a URL now was being parsed as two words ("hash" and "component"). The tests in this file that look at how the word "com" score (for testing for domain name matches) started scoring higher than expected because this new (unexpected) match. I revised the URL to be #hash_fragment to remove this errant (unexpected) match and leave the test continuing to test what it used to. Bug: 783500,364301 Change-Id: Id6c83457605ab30a630f7a4281573d000c4d2afd Reviewed-on: https://chromium-review.googlesource.com/c/1266724Reviewed-by:Justin Donnelly <jdonnelly@chromium.org> Commit-Queue: Justin Donnelly <jdonnelly@chromium.org> Cr-Commit-Position: refs/heads/master@{#597555}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/6d765b07f86f..6f591c9706e6 git log 6d765b07f86f..6f591c9706e6 --date=short --no-merges --format='%ad %ae %s' 2018-10-08 oetuaho@nvidia.com Clean up TCompiler members and style Created with: gclient setdep -r src/third_party/angle@6f591c9706e6 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=fjhenigman@chromium.org Change-Id: I682cd3b9fb1ef07f7748bbe16cabb5f7cc09e937 Reviewed-on: https://chromium-review.googlesource.com/c/1267687Reviewed-by:
-
Colin Blundell authored
This CL extends FakeO2TSDelegate to support taking in transient errors and dropping them; before, it would just update the auth error, which violates the contract of O2TS::GetAuthError() and results in a DCHECK failing inside that class. This better reflects production behavior (e.g., of MutablePO2TSDelegate) and allows an upcoming CL to test proper behavior in the event of a transient error occurring. Bug: 882861 Change-Id: Icbf2020b1b7fd9a0992e0b17fd74fc9b3f0eaf42 Reviewed-on: https://chromium-review.googlesource.com/c/1268017Reviewed-by:
-
Mikel Astiz authored
The recently introduced feature toggle has been experimented with via Finch, suggesting that the new settings cause an important improvement in RAM usage (with early data, ~5 MB for the 50th percentile). In addition, all sync status metrics report no regression, so let's enable the change by default (but keep the kill switch around). Bug: 887068 Change-Id: Ic3d8d1dff09900f0e3f25f75db4bce71572224cb Reviewed-on: https://chromium-review.googlesource.com/c/1268117Reviewed-by:
Jan Krcal <jkrcal@chromium.org> Commit-Queue: Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#597552}
-
Rune Lillesveen authored
Include specificity for compound inside ::slotted(). Intent to ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/gYrR2nR6quI Bug: 888042 Change-Id: Ibe421ce7423ba797cafd354696ff5cf693c52697 Reviewed-on: https://chromium-review.googlesource.com/c/1251421Reviewed-by:
Emilio Cobos Álvarez <emilio@chromium.org> Cr-Commit-Position: refs/heads/master@{#597551}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/5a279e61ff38..ae06125bdbdf Created with: gclient setdep -r src-internal@ae06125bdbdf 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: I406b1a857814409c336f97f999606fc3dbdc22e7 Reviewed-on: https://chromium-review.googlesource.com/c/1267957Reviewed-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@{#597550}
-
Rune Lillesveen authored
Otherwise `:host div` is equally specific to `div`, which seems undesirable and doesn't match any spec. This is only done for Shadow DOM v1 since there are backward compat issues with Polymer and WebUI. Intent to ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/gYrR2nR6quI Bug: 857415 Change-Id: Ieaaf9b835ae7136806ced8f6e72fb30f9adf02af Reviewed-on: https://chromium-review.googlesource.com/c/1250963 Commit-Queue: Rune Lillesveen <futhark@chromium.org> Reviewed-by:
-
Friedrich Horschig authored
This CL applies small fixes th the tests that make them less flaky: * use a small keyboard height but reduce the threshold to make it display-independent * ensure the tab overview is present for tests that need it * dismiss keyboards with a library function instead of the more flaky back press Bug: 857460 Change-Id: Id460847bdc2df7f8bbc0d1a04c96f151e3dff0ae Reviewed-on: https://chromium-review.googlesource.com/c/1225767 Commit-Queue: Friedrich Horschig [CEST] <fhorschig@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Cr-Commit-Position: refs/heads/master@{#597548}
-
Roman Sorokin authored
Also capitalized MACHINE_NAME placeholder for NativePrinters BUG=chromium:875876 Change-Id: I0270db0e970665db155248d75db54da353bd8720 Reviewed-on: https://chromium-review.googlesource.com/c/1245792Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Reviewed-by:
Denis Kuznetsov <antrim@chromium.org> Commit-Queue: Roman Sorokin <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/master@{#597547}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/9fcb424b..d42baee1 Please follow these instructions for assigning/CC'ing issues: https://github.com/v8/v8/wiki/Triaging%20issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_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;luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: Id402e8ea8c8fcd65f8234899137c3559f88f1499 Reviewed-on: https://chromium-review.googlesource.com/c/1267825Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#597546}
-
Greg Daniel authored
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I67e0f6017e84d964af316cef1f912dd58d050ce4 Reviewed-on: https://chromium-review.googlesource.com/c/1264922Reviewed-by:
Eric Karl <ericrk@chromium.org> Commit-Queue: Greg Daniel <egdaniel@chromium.org> Cr-Commit-Position: refs/heads/master@{#597545}
-
jdoerrie authored
This change applies clang-tidy's modernize-use-auto [1] in /content/browser. This change does not rewrite new and cast expressions. Reproduction steps: - run clang-tidy's modernize-use-auto - run git cl format - manually remove unused typedefs due to -Wunused-local-typedef error [1] https://clang.llvm.org/extra/clang-tidy/checks/modernize-use-auto.html This CL was uploaded by git cl split. R=boliu@chromium.org, mkwst@chromium.org Bug: 890902 Change-Id: I06146497aa7a8cba7516eb17497ca33454141b2a Reviewed-on: https://chromium-review.googlesource.com/c/1257909Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org> Cr-Commit-Position: refs/heads/master@{#597544}
-
Manuel Rego Casasnovas authored
The method LayoutBoxModelObject::RelativePositionOffset() was not considering the case of grid items, where the containing block is the grid area. The patch modifies the method so the new code uses OverrideContainingBlockContentLogicalWidth|Height when required. Two new tests are added, the first one does not use percentages and is already passing. The second one has the very same output but using percentages which was not working before this patch. BUG=835607 TEST=external/wpt/css/css-grid/grid-items/grid-items-relative-offsets-001.html TEST=external/wpt/css/css-grid/grid-items/grid-items-relative-offsets-002.html Change-Id: Icb76f4a521566ad36f87924835b21ae450f2cb24 Reviewed-on: https://chromium-review.googlesource.com/c/1238726Reviewed-by:
Javier Fernandez <jfernandez@igalia.com> Commit-Queue: Manuel Rego <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#597543}
-
Noel Gordon authored
The FilesApp QuickView PDF browser test crashes the MSAN bot. Disable the test in MSAN. Tbr: slangley, lucmult No-Presubmit: true Bug: 768070,891150 Change-Id: I262418dd3b79df11824810c42749cd1b6d78edee Reviewed-on: https://chromium-review.googlesource.com/c/1267597Reviewed-by:
Noel Gordon <noel@chromium.org> Commit-Queue: Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#597542}
-
Morten Stenshorne authored
NG needs to produce a rectangle with the block-axis offset relatively to block-start of the container, just like legacy does. Using purely physical coordinates is wrong. This fixes issues with scroll anchoring, and possibly other things too. One test had to be rebaselined, due to a rounding change. LayoutText::DebugRect() calls LinesBoundingBox(), which now flips the block-axis coordinate for vertical-rl. This affects rounding of the size of the rectangle. Bug: 889449 Change-Id: I7053ed7fe05ce443f53a128660d60f27fea7f8b3 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Reviewed-on: https://chromium-review.googlesource.com/c/1264596 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#597541}
-
Douglas Creager authored
This will allow us to add a new implementation that uses data_decoder to safely parse the untrusted JSON headers in a utility process. This patch just adds the new delegate interface and a default implementation that provides the existing behavior of parsing in-process. Bug: 892148, 811485 Change-Id: Ida8027ce44163c7f35535a3327343b7bf94ea854 Reviewed-on: https://chromium-review.googlesource.com/c/1262595 Commit-Queue: Douglas Creager <dcreager@chromium.org> Reviewed-by:
Misha Efimov <mef@chromium.org> Cr-Commit-Position: refs/heads/master@{#597540}
-
Marc Treib authored
This is done for two reasons: 1) It'll allow us to move a Wallet-specific special case from the general datatype-agnostic code into the Wallet-specific controller (once that exists). 2) It's actually less misleading: Directory data types actually ignore this value, i.e. passing CLEAR_METADATA didn't actually clear data for them. Bug: 889941 Change-Id: I4e660e41b17142480eb8b03569077686cedaab6c Reviewed-on: https://chromium-review.googlesource.com/c/1264695Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Reviewed-by:
-
Christopher Lam authored
This CL hides the location bar for System PWAs. It also plumbs better bookmark app manifest validation into ExtensionBrowserTest. Bug: 836128 Change-Id: Ife1ec3962edd57a0f5ea7c44ff359894a9d0d7cf Reviewed-on: https://chromium-review.googlesource.com/c/1256467 Commit-Queue: calamity <calamity@chromium.org> Reviewed-by:
Ben Wells <benwells@chromium.org> Reviewed-by:
Alan Cutter <alancutter@chromium.org> Cr-Commit-Position: refs/heads/master@{#597538}
-
Michael van Ouwerkerk authored
This reflects the implementation of setTopBarView. Bug: 882404 Change-Id: I0c4b39e3db96dd626f2207b87fa0c4a1dd4ecfa2 Reviewed-on: https://chromium-review.googlesource.com/c/1267501Reviewed-by:
Michael van Ouwerkerk <mvanouwerkerk@chromium.org> Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Commit-Queue: Michael van Ouwerkerk <mvanouwerkerk@chromium.org> Cr-Commit-Position: refs/heads/master@{#597537}
-
Boris Sazonov authored
Before this CL, asynchronous methods in AccountManagerFacade were using AsyncTask to avoid blocking the main thread if account list cache hasn't been populated yet. However, this approach has two major drawbacks: 1. Every call to these methods blocks one thread from thread pool until the cache is populated. 2. Even if the cache is already populated, call still creates AsyncTask, incurring unnecessary allocations and thread hops. This CL introduces AccountManagerFacade.runAfterCacheIsPopulated that keeps a list of callbacks to execute after the cache is populated. If the cache has already been populated, this method just posts the callback to the main thread. All asynchronous account-related methods in AccountManagerFacade are reimplemented using runAfterCacheIsPopulated. Bug: 887969 Change-Id: I856b6c7f9395a70857d079dedfbf3f4f6403f901 Reviewed-on: https://chromium-review.googlesource.com/c/1238559 Commit-Queue: Boris Sazonov <bsazonov@chromium.org> Reviewed-by:
Mihai Sardarescu <msarda@chromium.org> Cr-Commit-Position: refs/heads/master@{#597536}
-
Ulan Degenbaev authored
Bug: 878390 Change-Id: I550b09fdfdd3b1a76cb28ddd582002a52e680991 Reviewed-on: https://chromium-review.googlesource.com/c/1264588Reviewed-by:
Juan Antonio Navarro Pérez <perezju@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#597535}
-
Morten Stenshorne authored
TBR=eae@chromium.org Bug: 892817 Change-Id: I5bf3d4caa0637863c329fffda7a8f27175256b12 Reviewed-on: https://chromium-review.googlesource.com/c/1268196Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#597534}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/38537edf5979..2e00abc98e59 git log 38537edf5979..2e00abc98e59 --date=short --no-merges --format='%ad %ae %s' 2018-10-08 yvesg@webrtc.org Reland "[cleanup] Remove useless includes." 2018-10-08 nisse@webrtc.org Move EncodedImage class to api/video/ Created with: gclient setdep -r src/third_party/webrtc@2e00abc98e59 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 TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I29cd4055efe8c6929f37f71d44549214713eb9f4 Reviewed-on: https://chromium-review.googlesource.com/c/1267684Reviewed-by:
-
Ulan Degenbaev authored
Bug: 878390 Change-Id: I7dd274d816f8833bdabe890628b92f701612ffed Reviewed-on: https://chromium-review.googlesource.com/c/1264659Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/9b74746414c7..5a279e61ff38 Created with: gclient setdep -r src-internal@5a279e61ff38 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: I4bf4f83df1456b62db4d022bdea3f5b37f2d9e40 Reviewed-on: https://chromium-review.googlesource.com/c/1267683Reviewed-by:
-
Olga Sharonova authored
This reverts commit 53c52480. Reason for revert: FindIt thinks it caused flakiness of virtual/android/fullscreen/video-fixed-background.html. Speculative revert. Bug:893097 Original change's description: > [Media Controls] Remove overlay play button on desktop > > This CL updates the media controls on desktop to have the standard > play button in the bottom left corner instead of the overlay play > button in the center. > > As part of this change, the play button is given a disabled state > when appropriate, which also applies to the audio player. This fixes > a separate issue where the audio player wasn't giving proper feedback > with a broken source. > > Bug: 890078, 839101 > Change-Id: Ifbc8b3c216d3537c657b04ff6fc53506b886c48f > Reviewed-on: https://chromium-review.googlesource.com/c/1252846 > Reviewed-by: Becca Hughes <beccahughes@chromium.org> > Reviewed-by: Aaron Leventhal <aleventhal@chromium.org> > Commit-Queue: Tommy Steimel <steimel@chromium.org> > Cr-Commit-Position: refs/heads/master@{#597483} TBR=aleventhal@chromium.org,beccahughes@chromium.org,steimel@chromium.org Change-Id: I4f405126f603bd2c8df849c3c210a5d8efedd74e No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 890078, 839101 Reviewed-on: https://chromium-review.googlesource.com/c/1268197Reviewed-by:
Olga Sharonova <olka@chromium.org> Commit-Queue: Olga Sharonova <olka@chromium.org> Cr-Commit-Position: refs/heads/master@{#597530}
-
Morten Stenshorne authored
Corrected ref imported in https://chromium-review.googlesource.com/c/chromium/src/+/1259943 Fixed by aethanyc@gmail.com in https://bugzilla.mozilla.org/show_bug.cgi?id=1495875 TBR=vmpstr@chromium.org Bug: 874124 Change-Id: I58d7b2117217197b6240655a1d4b32b34b120895 Reviewed-on: https://chromium-review.googlesource.com/c/1268137Reviewed-by:
-
Tibor Goldschwendt authored
If the WebView provider is a split APK on Android O, WebView crashes at initialization (see crbug/889954). A considered work around relies on reflection and we are unsure whether that works for all devices. Therefore, measure via UMA if the fields used by reflection exist. Caveat: Only logs for Chrome processes, not for WebView ones. Bug: 891452 Change-Id: Iaecedb061106a67da440ef53039cd6148d64f9cc Reviewed-on: https://chromium-review.googlesource.com/c/1261916 Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Richard Coles <torne@chromium.org> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Cr-Commit-Position: refs/heads/master@{#597528}
-
Henrik Grunell authored
Bug: 807547 Change-Id: Ibf1d9dc10da2b25cd1197020f2301cf8cfeb6552 Reviewed-on: https://chromium-review.googlesource.com/c/1258165Reviewed-by:
Tommi <tommi@chromium.org> Commit-Queue: Henrik Grunell <grunell@chromium.org> Cr-Commit-Position: refs/heads/master@{#597527}
-
Ulan Degenbaev authored
Bug: 878390 Change-Id: If95d9fc73619e626e4e82189a63284706a664ffb Reviewed-on: https://chromium-review.googlesource.com/c/1264586Reviewed-by:
-
Michael Lippautz authored
Work around the problem where second pass callbacks are fired during teardown. Previously, these callbacks where just dropped which is not correct for other reason, e.g., when components keep a state per process and not just per Isolate. Bug: chromium:890631 Change-Id: I1fd66f9ffee86c5c7bff053303c741c4dedefdb0 Reviewed-on: https://chromium-review.googlesource.com/c/1253782Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#597525}
-
Sergio Villar Senin authored
Change-Id: I95ff9e86821169fc1ffccb84dbf32f1e09b1e7a4 Reviewed-on: https://chromium-review.googlesource.com/c/1261202 Commit-Queue: Sergio Villar <svillar@igalia.com> Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/master@{#597524}
-
Philip Jägenstedt authored
Using wpt-import in Chromium 45c36ac2. With Chromium commits locally applied on WPT: 65d72632 "Make DTMF tone change more deterministic" Based on https://chromium-review.googlesource.com/1267823 which failed due to issue 893079. TBR=robertma@chromium.org Bug: 893079 Change-Id: Icb44160333c6949809e8312abb0da2866aab29b6 No-Export: true Reviewed-on: https://chromium-review.googlesource.com/c/1268155Reviewed-by:
Philip Jägenstedt <foolip@chromium.org> Commit-Queue: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#597523}
-
Mirko Bonadei authored
This change only affects component builds. Since //media/webrtc is a component, it will statically link WebRTC code when `is_component_build = true`. WebRTC is going to support Chromium component builds soon, and in order to make it happen WebRTC symbols are being tagged with RTC_EXPORT. This CL temporarily defines WEBRTC_LIBRARY_IMPL also when compiling //media/webrtc in order to avoid to expand RTC_EXPORT to __declspec(dllimport) since WebRTC code is still statically linked into the //media/webrtc component. This will be removed as soon as Chromium will depend on a unique WebRTC component. Bug: webrtc:9419 Change-Id: I731bf55414a64f80bee4dbe276a556a3a289629a Reviewed-on: https://chromium-review.googlesource.com/c/1261398Reviewed-by:
-
Philip Jägenstedt authored
This adapts to "Reject non-thenable values" upstream: https://github.com/web-platform-tests/wpt/pull/12898 This is blocking updating LayoutTests/resources/testharness.js. Bug: 892613 Change-Id: Ifbc91824c0a5687a74cc6f16e02457da60dc4e85 Reviewed-on: https://chromium-review.googlesource.com/c/1264585 Commit-Queue: Philip Jägenstedt <foolip@chromium.org> Reviewed-by:
Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#597521}
-
Rayan Kanso authored
downloadTotal was being updated instead of downlaoded, yielding incorrect values when queried. Change-Id: Id527ed6296081c491d106ef041adedc9260e55dc Reviewed-on: https://chromium-review.googlesource.com/c/1265258Reviewed-by:
Mugdha Lakhani <nator@chromium.org> Commit-Queue: Rayan Kanso <rayankans@chromium.org> Cr-Commit-Position: refs/heads/master@{#597520}
-
Mario Sanchez Prada authored
Migrate from using ProfileOAuth2TokenService and SigninManager to using the IdentityManager instead, and remove the related includes. Bug: 882862 Change-Id: I5fb46927ffba508e6987f615ed22bc1a90155607 Reviewed-on: https://chromium-review.googlesource.com/c/1255624Reviewed-by:
Joshua Bell <jsbell@chromium.org> Reviewed-by:
-
