- 26 Aug, 2019 40 commits
-
-
Mario Sanchez Prada authored
Convert both the implementation and clients in the browser and renderer processes for the blink.mojom.PresentationReceiver interface, and adapt unit tests. Bug: 955171, 978694 Change-Id: I5b3db354a14cca90841a71df8e67cc778c53a1df Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1764188 Commit-Queue: Mario Sanchez Prada <mario@igalia.com> Reviewed-by:
mark a. foltz <mfoltz@chromium.org> Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
Ken Rockot <rockot@google.com> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Cr-Commit-Position: refs/heads/master@{#690364}
-
Mario Sanchez Prada authored
Convert both the implementation and clients in the browser and renderer processes for the blink.mojom.PresentationController interface, and adapt unit tests. Bug: 955171, 978694 Change-Id: I3dcc608a424d64e456d9b4cc4361bef0ca2c51d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1764130 Commit-Queue: Mario Sanchez Prada <mario@igalia.com> Reviewed-by:
-
Finnur Thorarinsson authored
to UMA logging and UKM. Metrics review: https://docs.google.com/document/d/15na0QNN02V4IhfSphRjBazZJ218OxvmMD2BIgCscec4/edit Bug: 993775, 860467 Change-Id: I5e9be794b5841486edcee44a10c4516b0e498838 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1757940 Commit-Queue: Finnur Thorarinsson <finnur@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Peter Beverloo <peter@chromium.org> Auto-Submit: Finnur Thorarinsson <finnur@chromium.org> Cr-Commit-Position: refs/heads/master@{#690362}
-
Nico Weber authored
This is a reland of 02536c57 In the reland, use just '../' until https://crbug.com/997673 is fixed. Original change's description: > mb: Make check for generated `data` directories work on Win and enable there. > > The line `os.path.normpath(self.PathJoin(build_dir, f))` had two problems > on Windows: > > 1. Since `build_dir` was something like `//out/Release`, on Windows normpath > wouldn't resolve '..' against it, so `//out/Release/../../net/data` > would become `\\out\Release\net\data` > > 2. The slash flipping for `path` made the `path.startswith(build_dir)` always > fail. > > Just remove `path` completely and check if `f` starts with '../../' to find > directories that are not in the build dir instead. > > Also mixing stderr and stdout on Windows produced strange output, so print > the error message to stdout instead. > > The Windows build doesn't have any additional violations, so no new > whitelist entries are needed. > > Bug: 912946 > Change-Id: I4db9850103751b4736e5990caddddc9dd223786d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1769205 > Reviewed-by: Takuto Ikuta <tikuta@chromium.org> > Commit-Queue: Takuto Ikuta <tikuta@chromium.org> > Commit-Queue: Nico Weber <thakis@chromium.org> > Auto-Submit: Nico Weber <thakis@chromium.org> > Cr-Commit-Position: refs/heads/master@{#690259} Bug: 912946,997673 Change-Id: I672ba803530b749fd4f1a6888687360e59444a88 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1769501Reviewed-by:
Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#690361}
-
Mario Sanchez Prada authored
Convert both the implementation and clients in the browser and renderer processes for the blink.mojom.PresentationConnection interface, and adapt unit tests. Bug: 955171, 978694 Change-Id: Ia52a7bf709a1497f84939531064ce17f3a558ab3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1758443Reviewed-by:
Camille Lamy <clamy@chromium.org> Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Reviewed-by:
-
Vasilii Sukhanov authored
external/wpt/css/css-animations/Element-getAnimations.tentative.html external/wpt/css/css-paint-api/custom-property-animation-on-main-thread.https.html TBR=futhark@chromium.org Bug: 626703 Change-Id: I7bdd807e50d1ee4a9c0382448dd216ea28855a51 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1771400Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Cr-Commit-Position: refs/heads/master@{#690359}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/afa3f633..bcfd55ce Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I3c0f57526d0711ca40e7746147e74d6cdf4d29f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1770237Reviewed-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@{#690358}
-
Alexander Hendrich authored
Since the created window has fixed size and is not draggable, multi-window support does not make sense anymore. We only ever expect there to be one login screen extension showing UI at a time. Bug: 957573 Change-Id: I90fcb01d3d8098abe2350c8773df03ce0cdedcfe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768643 Commit-Queue: Alexander Hendrich <hendrich@chromium.org> Reviewed-by:
Zakhar Voit <voit@google.com> Cr-Commit-Position: refs/heads/master@{#690357}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/2ca0b3689f60..6558fa5d64c4 git log 2ca0b3689f60..6558fa5d64c4 --date=short --no-merges --format='%ad %ae %s' 2019-08-26 saza@webrtc.org Reintroduce command line controlled reference data updating for ApmTest.Process 2019-08-26 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 318f298c..004b5082 (688507:690310) Created with: gclient setdep -r src/third_party/webrtc@6558fa5d64c4 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. TBR=webrtc-chromium-sheriffs-robots@google.com Bug: chromium:None Change-Id: I5c9a8c95d4957e0e5c0b43ba6946c464c3e390e5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1771540Reviewed-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@{#690356}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/ef4177b1f655..13847ac79387 Created with: gclient setdep -r src-internal@13847ac79387 The AutoRoll server is located here: https://skia-autoroll.corp.goog/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. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=jbudorick@google.com Bug: chromium:None,chromium:None,chromium:None Change-Id: Ia32b6dff389b3ebedd4bb84ffaf0fb19045c5825 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1771539Reviewed-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@{#690355}
-
Dominic Farolino authored
The blink::ResourceRequest::priority_ member defaults to kUnresolved, which is unexpected by anything beyond ResourceFetcher. blink::ResourceFetcher::EmulateLoadStartedForInspector basically emulates a request from the inspector's point-of-view, however it doesn't set the request's priority. Once the inspector's BuildObjectForResourceRequest is invoked on this path, it calls ResourcePriorityJSON, which DCHECKs on unresolved priorities. This happens on debug builds, when the DevTools window is open, and a page is refreshed whose resources go through the EmulateLoadStartedForInspector path. Bug: 666214 Change-Id: I95d8df7193ab11e96ae210eb127146fb6ce9903c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768607Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Dominic Farolino <dom@chromium.org> Cr-Commit-Position: refs/heads/master@{#690354}
-
Yi Gu authored
The failure on ChromeOS started when VizHitTesting was turned on by default and it should be fixed by crrev.com/c/1693442. Tested locally and the test is no longer failing. Bug: 997676 Change-Id: Ie3b10fc2eb7a176ca2aa0a53cb02cd64c4da082b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1770081 Commit-Queue: Yi Gu <yigu@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#690353}
-
Yi Gu authored
The failure on ChromeOS started when VizHitTesting was turned on by default and it should be fixed by crrev.com/c/1693442. Tested locally and the test is no longer failing. Bug: 997676 Change-Id: I71892e0b1ffb1829f73fac3b5ee6572f770a4021 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1770080 Commit-Queue: Yi Gu <yigu@chromium.org> Reviewed-by:
-
Alexander Hendrich authored
So far the login screen extension UI window's dialog title was in the form of "This authentication service is hosted by <<<EXTENSION_NAME>>>", with <<<EXTENSION_NAME>>> being replaced by the extension's short name. Privacy (yzd@) requested to update the title so that the extension has no control over it, since a compromised extension could just have "Google" as its short name, which would lead to a misleading dialog title. Since the list of extensions being able to display login screen UI is very small, we will just hardcode the respective dialog title per extension. Bug: 997167 Change-Id: Iedd5b469df65cf1e125bcca5c5edc6bb71448e82 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768626Reviewed-by:
-
Vasilii Sukhanov authored
TBR=mrobinson@igalia.com Bug: 981913 Change-Id: I920c8c1fe841c46b6503cf0eace19c06bd3e6e37 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768532Reviewed-by:
-
Guido Urdaneta authored
Prior to this CL, the state of the execution context (destroyed or not) was stored in a boolean field updated when the execution context was destroyed. After UserMediaClient/UserMediaProcessor was moved to Blink, the timing for the stopping of sources changed slightly. Instead of clearing state upon starting a new navigation, it is now cleared when the execution context is destroyed. If the dying context notifies UMC/UMP before notifying the MediaStreamTrack about the destruction it can happen that MediaStreamTrack tries to fire an event on the destroyed context without knowing that the context has already been destroyed. To prevent this from happening, instead of keeping the state of the context in a separate variable updated via ContextLifecycleObserver, we now track the context using a WeakMember. Bug: 996051 Change-Id: I0027c267a0d067ba67ffcf8f508c1bc56f36a72a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768460 Commit-Queue: Guido Urdaneta <guidou@chromium.org> Reviewed-by:
Marina Ciocea <marinaciocea@chromium.org> Cr-Commit-Position: refs/heads/master@{#690349}
-
Kush Sinha authored
|CrOSOAuthDelegate| was renamed to |ProfileOAuth2TokenServiceDelegateChromeOS| but its unit tests were not. Rename the unit tests for consistency. Bug: 967602 Change-Id: I85fd3bc5dd601bea8301dd091194f391a07693b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1771597 Commit-Queue: Kush Sinha <sinhak@chromium.org> Commit-Queue: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Cr-Commit-Position: refs/heads/master@{#690348}
-
Clemens Arbesser authored
This is a reland of 8667827a Original change's description: > [Autofill Assistant] Adds action to use login credentials. > > This CL extends SetFormFieldValueAction such that it can also fill a selector with a previously stored username or password. To this end, the action is refactored to allow for better code reuse and readability. Also, the CL adds unit tests (not just for the new functionality, but for the entire action). > > > Bug: b/128833341 > Change-Id: I43e57bee5681047f1df954040f62265e0ab44f28 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1728560 > Commit-Queue: Clemens Arbesser <arbesser@google.com> > Reviewed-by: Stephane Zermatten <szermatt@chromium.org> > Cr-Commit-Position: refs/heads/master@{#689877} Bug: b/128833341 Change-Id: I87eadf3a335dec9244d5adf94cd004326ed52597 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768422Reviewed-by:
Stephane Zermatten <szermatt@chromium.org> Commit-Queue: Clemens Arbesser <arbesser@google.com> Cr-Commit-Position: refs/heads/master@{#690347}
-
Gabriel Charette authored
This is a reland of 0567f059 Reason for reland: - joelhockey@ fixed the chromeos build in https://chromium-review.googlesource.com/c/chromium/src/+/1767447 Original change's description: > Reland "Reland "Reland [base] Require task posters to specify an explicit destination"" > > This is a reland of d7b74986 > > As usual, if this fails **please** paste the build failure, not just > silent revert, logs can be hard to find in retrospect. > > Reason for reland: > - joenotcharles@ fixed the windows build in > https://chromium-review.googlesource.com/c/chromium/src/+/1764471 > - google chromeos build failure fixed in > https://chromium-review.googlesource.com/c/chromium/src/+/1764256 > > Original change's description: > > Reland "Reland [base] Require task posters to specify an explicit destination" > > > > This is a reland of dd34a877 > > > > Rebased on a few more fixes including a local full build of: > > - Windows + is_chrome_branded > > - ChromeOS + is_chrome_branded > > (except for the libassistant portion which is giving weird errors...) > > > > Original change's description: > > > Reland [base] Require task posters to specify an explicit destination > > > > > > This patch makes it a requirement for all task traits to specify their > > > thread affinity. Previously task traits that did not name a specific > > > thread would implicitly run on the thread pool, which could be > > > surprising. To make this more obvious, thread pool tasks must now use > > > the base::ThreadPool() trait. > > > > > > This is the final reland of > > > https://chromium-review.googlesource.com/c/chromium/src/+/1635827 > > > (will attempt to fix errors that caused original revert before > > > relanding). > > > > > > Bug: 968047 > > > Change-Id: Ice339db270a27815b2be68200930e5bc105e8a96 > > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1759056 > > > Commit-Queue: Gabriel Charette <gab@chromium.org> > > > Reviewed-by: François Doray <fdoray@chromium.org> > > > Cr-Commit-Position: refs/heads/master@{#688782} > > > > Bug: 968047 > > Change-Id: Iccd12e0a9f1535cb10b903777c5004a7d1acb34a > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761362 > > Commit-Queue: Gabriel Charette <gab@chromium.org> > > Reviewed-by: François Doray <fdoray@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#689097} > > Bug: 968047 > Change-Id: Ie338781aba9b5f5990ffe74e02bb85f08fe683d1 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1764398 > Commit-Queue: Gabriel Charette <gab@chromium.org> > Reviewed-by: François Doray <fdoray@chromium.org> > Cr-Commit-Position: refs/heads/master@{#689665} Bug: 968047 Change-Id: Idca1ec9ef83aad51def481b2ed4f8f1baf1385da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1769080Reviewed-by:
François Doray <fdoray@chromium.org> Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org> Cr-Commit-Position: refs/heads/master@{#690346}
-
Vasilii Sukhanov authored
TBR=estade@chromium.org Bug: 997649 Change-Id: I3649c29efaa2343f97b5d27cd5c124a033882a2e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768326Reviewed-by:
-
Friedrich Horschig authored
The spacing around the footer hasn't been consistent across all sheets. This CL generalizes the class that was introduced by two of the three sheets and uses this spacing class in all of them. To fully fix the footer spacing, overscroll is now extended from 8dip to 64dip as shown in the mocks in the linked bug. Bug: 997611 Change-Id: I33f813b174a887f496413240efeebdaea3844426 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768466Reviewed-by:
Jan Wilken Dörrie <jdoerrie@chromium.org> Commit-Queue: Friedrich [CET] <fhorschig@chromium.org> Cr-Commit-Position: refs/heads/master@{#690344}
-
Vasilii Sukhanov authored
TBR=cjamcl@google.com Bug: 997669 Change-Id: I9f3bbb06ebbbed904c82acdb1b89d31d2b7fe09c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1771399Reviewed-by:
-
Chromium WPT Sync authored
Using wpt-import in Chromium 4c811fa7. With Chromium commits locally applied on WPT: 1194775a "Add ability to block same-origin access via document-access feature policy" 5546163a "Temporarily send `Sec-Fetch-*` headers via non-secure transport." 4afcd1a6 "Started implementing the STAPIT algorithm" d7f933bd "Revert "Started implementing the STAPIT algorithm"" d3b97055 "Update simulateUserActivation to match webxr-test-api spec" 6a3beaa9 "[WPT/referrer-policy] Fix races around history.back()" 2d090a27 "[WPT/referrer-policy] Call getRequestURLs() for each subtest" 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 NOAUTOREVERT=true TBR=robertma No-Export: true Change-Id: Ic5573cecf16ebd835e24e6262e36717790ce9bdb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1771497Reviewed-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@{#690342}
-
Takashi Toyoshima authored
This is not required, but set for the non-NetworkService code path that does not exist any more. Change-Id: If282d1c49894302c0da22a7ecda4168afb4277c3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1771370 Auto-Submit: Takashi Toyoshima <toyoshim@chromium.org> Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
-
chromium-autoroll authored
The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-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:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast TBR=cr-fuchsia+bot@chromium.org Change-Id: Ic4266954f4b667d12c38b4b4ebffa46fd28bccd1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1771538Reviewed-by:
-
Antonio Gomes authored
... now that mediastream has been Onion Soup'ed and uses ApplyConstrainsRequests. BUG=704136, 919392 R=guidou@chromium.org, haraken@chromium.org Change-Id: I1a02b3ea294c0a0d161bf4bff2070e96a4e47394 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768779 Commit-Queue: Antonio Gomes <tonikitoo@igalia.com> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#690339}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/40ba72e3..afa3f633 Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I5b7331a747188188468133e9392065d089052e34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1771496Reviewed-by:
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=benmason@chromium.org Change-Id: Iccbef80bb12b1baf684089615470e807989058f6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1769499Reviewed-by:
Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#690337}
-
Antonio Gomes authored
... in renderer/modules/mediastream. WebApplyConstraintsRequest will be removed altogether in a follow up CL. BUG=704136 R=guidou@chromium.org, haraken@chromium.org Change-Id: I06fc9a2ca93f2bcb924b2491676d3457e2dd1067 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768778 Commit-Queue: Antonio Gomes <tonikitoo@igalia.com> Reviewed-by:
-
Vasilii Sukhanov authored
TBR=caseq@chromium.org Bug: 946990 Change-Id: I0ca05b3b30ac2e09f8852a5c24e6cdffa82a7967 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768708Reviewed-by:
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/a2dae38ee772..2ca0b3689f60 git log a2dae38ee772..2ca0b3689f60 --date=short --no-merges --format='%ad %ae %s' 2019-08-26 peah@webrtc.org Correct the handling of sample rates that don't scale well into even 10 ms chunks 2019-08-26 yvesg@webrtc.org [vp9] Array temporal_up_switch wasn't properly initialized. 2019-08-26 nisse@webrtc.org New empty build target api:rtp_parameters 2019-08-23 peah@webrtc.org Use the AEC3 high-pass filter for the whole APM 2019-08-23 peah@webrtc.org Reland "Reland Process 8 kHz audio as 16 kHz internally of the audio processing module" 2019-08-23 artit@webrtc.org Revert "Reland Process 8 kHz audio as 16 kHz internally of the audio processing module" 2019-08-23 kthelgason@webrtc.org Add ObjC interface wrapping new GetImplementations method. 2019-08-23 titovartem@webrtc.org Fix flake in SamplesStatsCounterTest.FullSimpleTest 2019-08-23 kthelgason@webrtc.org Set required alignment to 2 for iOS. 2019-08-23 peah@webrtc.org Reland Process 8 kHz audio as 16 kHz internally of the audio processing module 2019-08-23 nisse@webrtc.org New const method StreamStatistician::GetStats 2019-08-22 jakobi@webrtc.org Save delays in history for 2 seconds instead of fixed 100 packets. 2019-08-22 orphis@webrtc.org Wire the stable target bitrate from GoogCC to the BitrateAllocator 2019-08-22 nisse@webrtc.org Delete unused function MediaTypeFromString 2019-08-22 kron@webrtc.org Don't include duplicated and incomplete frames in stats. 2019-08-22 peah@webrtc.org Reland "Simplification and refactoring of the AudioBuffer code" Created with: gclient setdep -r src/third_party/webrtc@2ca0b3689f60 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. TBR=webrtc-chromium-sheriffs-robots@google.com Bug: chromium:677543,chromium:None,chromium:990317 Change-Id: Iac2af672b63a1d3689dde8f6d29787b2324078a4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1771537Reviewed-by:
-
Kush Sinha authored
With Chrome OS Account Manager enabled, SecondaryGoogleAccountSigninAllowed applies to the unified account list in Chrome OS Account Manager, and not just Chrome content area, as the policy documentation claims. Update the documentation to reflect this fact. Another related policy: AllowedDomainsForApps does not require any change. Bug: 967206 Change-Id: Ifde3d6c8a68fb2ec22006bb4cdcc1b0707f15351 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768464Reviewed-by:
Bartosz Fabianowski <bartfab@chromium.org> Commit-Queue: Kush Sinha <sinhak@chromium.org> Cr-Commit-Position: refs/heads/master@{#690333}
-
Stephen McGruer authored
Bug: 900581 Change-Id: I9cd2582aea4792c6bc0fa68f9bbf20f17a74a90c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768551Reviewed-by:
Xida Chen <xidachen@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#690332}
-
Stephen McGruer authored
Bug: 900581 Change-Id: I3a9a292495b86ddf32ebfd67a1531d5995e5879a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1769314Reviewed-by:
-
Stephen McGruer authored
Bug: 900581 Change-Id: I40b7d6f983d37726b843e82ad5ba794cec9c1214 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768666Reviewed-by:
-
Yi Gu authored
This flaky test was fixed by crrev.com/c/1739386 and is no longer flaky. See https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=webkit_layout_tests&tests=animations%2Fevents%2Fplay-state-initially-paused-start-event.html Bug: 994746 Change-Id: I1beb162bed54c2fef0e88685d03d13358c030786 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1770084Reviewed-by:
-
Friedrich Horschig authored
This CL removes hard-coded heights and paddings. They are superfluous since ChipView enforces its padding and restricts the line height. This means the duplicate paddings (see screenshots in bug) are gone. Bug: 997611 Change-Id: I805792254fced2c25c63fa75b4bc48021ff90fa2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1769440Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/b705a4e15ba7..ef4177b1f655 Created with: gclient setdep -r src-internal@ef4177b1f655 The AutoRoll server is located here: https://skia-autoroll.corp.goog/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. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=jbudorick@google.com Bug: chromium:None Change-Id: I4fe55b9551c97c51f13ad250e7606a9c5bcc0a2b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1771295Reviewed-by:
-
Mohamed Amir Yosef authored
Before this Patch: TwoClientPasswordsSyncTest were exercised against the 4 combinations of USS and non-USS clients. This caused some tests to be flaky. (check the linked bugs). After this patch: Since the plan is to roll out Sync USS Passwords for M77 (where all the 4 combinations have been tested already) we are now restricting the testing to only USS or non-USS to remove the flakiness. In case the rollout doesn't make it to M77, we should rethink about reinstating the tests again. Change-Id: I402f481723541a1a77314a8173a1144a1560cf77 Bug: 984944,980557,915219 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768530Reviewed-by:
-
Vasilii Sukhanov authored
TBR=grt@chromium.org Bug: 997649 Change-Id: Ia928c720c08e56c39fac597e44d2bf2a6256680f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768465Reviewed-by:
-
