- 10 Jan, 2020 40 commits
-
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/079a14224dd1..3f1bd1b88a31 Created with: gclient setdep -r src-internal@3f1bd1b88a31 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC jbudorick@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: chromium:1010717 Tbr: jbudorick@google.com Change-Id: I81b8a6846ce4dd210dd7102ab633c4eee9c8eed3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995224Reviewed-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@{#730148}
-
Mikel Astiz authored
With this patch TrustedVaultClient.Backend has the ability to notify native code that the keys in the vault may have changed. This notification makes its way via TrustedVaultClientAndroid to ultimately SyncServiceCrypto, where refetching logic is triggered. This is expected to be an effective means for resolving encryption issues transparently without user action and without having to restart the browser. The very same method is also used upon relevant user action such as triggering the retrieval flow, in case the keys within the vault have changed since the last fetch (e.g. if the backend failed to or does not support broadcasting change notifications). Bug: 1012659 Change-Id: I985db773fe5b18f107a8c8731d31dbd80aaf599c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1978005Reviewed-by:
Boris Sazonov <bsazonov@chromium.org> Commit-Queue: Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#730147}
-
Monica Basta authored
This CL adds tests for communicating the sWAA bit in sync setup settings. Bug: 1035421 Change-Id: I40f3c5304b04e433a2cac571a715299459a565c4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1991624 Commit-Queue: Monica Basta <msalama@chromium.org> Reviewed-by:
Dan Beam <dbeam@chromium.org> Cr-Commit-Position: refs/heads/master@{#730146}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/4b6df1777cba..56452dd17bac git log 4b6df1777cba..56452dd17bac --date=short --first-parent --format='%ad %ae %s' 2020-01-10 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision aa827d65..54a7cb4b (729982:730109) Created with: gclient setdep -r src/third_party/webrtc@56452dd17bac If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I24e8d14bb2fd1576508df7df884f1fe5b21d613d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995223Reviewed-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@{#730145}
-
Olivier Li authored
Set browser state builder dir to avoid file leaks in ios tests in /ios/chrome/browser/ui/location_bar This cl is generated with 'git cl split' This CL was uploaded by git cl split. R=stkhapugin@chromium.org Bug: 546640 Change-Id: If47000191d0170327c9e74d270c7b6cb0506367a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1991752Reviewed-by:
Stepan Khapugin <stkhapugin@chromium.org> Commit-Queue: Stepan Khapugin <stkhapugin@chromium.org> Auto-Submit: Oliver Li <olivierli@chromium.org> Cr-Commit-Position: refs/heads/master@{#730144}
-
Vasilii Sukhanov authored
TBR=foolip@chromium.org Bug: 1040912 Change-Id: Ie273a75c2f6f7efc1f0b17d9f8325eaaa6e8facf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994296Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Cr-Commit-Position: refs/heads/master@{#730143}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/63dded1f4d55..033f08c5a865 git log 63dded1f4d55..033f08c5a865 --date=short --first-parent --format='%ad %ae %s' 2020-01-10 primiano@google.com probes: workaround for missing NUL in /proc/pid/cmdline Created with: gclient setdep -r src/third_party/perfetto@033f08c5a865 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Please CC perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Bug: chromium:147438623 Tbr: perfetto-bugs@google.com Change-Id: I8310f1a402b5a8bb0a3d09922a1b42f3301c6e2b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994083Reviewed-by:
-
Gyuyoung Kim authored
This CL cleans up redundant Create() factory methods in //third_partyb/blink/renderer only when it meets the policy of removing Create() so that we support only one of Create() methods or public constructors in a class. Then, this CL makes all callers use MakeGarbageCollected<Foo> instead. This CL removes below Create() functions, - CSSConicGradientValue::Create - PaymentManager::Create - RTCIceCandidatePlatform::Create Bug: 939691 Change-Id: I17f79f7478aa4491ee1995ac22593142731c0260 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994541Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com> Cr-Commit-Position: refs/heads/master@{#730141}
-
Corentin Wallez authored
This reverts commit 7cb3f403. Reason for revert: Make TabCaptureApiPixelTest.EndToEndThroughWebRTC fail consistently on Win10 FYI x64 Release (Intel HD 630) Original change's description: > Fix issue where DXGI_FORMAT_R16G16B16A16_FLOAT gets used even when unsupported by hardware > > Issue backtrace: > - video_device_->CreateVideoProcessorOutputView(...) in > DXVAVideoDecodeAccelerator::CopyTextureOnDecoderThread() fails because > DXGI_FORMAT_R16G16B16A16_FLOAT is not supported by client's hardware. > - in DXVAVideoDecodeAccelerator::Initialize, use_fp16_ = true due to > "Issue 592074: Add support for different VP9 profiles". > - DXGI_FORMAT_R16G16B16A16_FLOAT is in fact not supported, and > CheckOutputFormatSupport(DXGI_FORMAT_R16G16B16A16_FLOAT) > DXVAVideoDecodeAccelerator::CreateDX11DevManager() reflects that, > and use_fp16_ = false. > > Proposed fix: > - Make use_fp16_ an enum to reflect the fact that its non-binary states. > - Because intent to use fp16 is expressed in DXVAVideoDecodeAccelerator::Initialize, > which can be called before or after support for fp16 is determined, let use_fp16_ be > set to kUsing for all states except kUnsupported. kUsing can be reversed later > when hardware support is queried. > > Bug: 1032438 > Change-Id: I113f26b126fdc1e0131a2362cbf19629f268f3eb > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1974761 > Reviewed-by: Frank Liberato <liberato@chromium.org> > Reviewed-by: Ted Meyer <tmathmeyer@chromium.org> > Commit-Queue: Vi Nguyen <ving@microsoft.com> > Cr-Commit-Position: refs/heads/master@{#730012} TBR=sandersd@chromium.org,liberato@chromium.org,tmathmeyer@chromium.org,ving@microsoft.com Change-Id: I5071f5b78391ba4479d04132402f728799821ffa No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1032438 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995167Reviewed-by:
Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org> Cr-Commit-Position: refs/heads/master@{#730140}
-
Anatoliy Potapchuk authored
app data Change-Id: I372946839db9523e76c3f1c6c6165087c2e8e4ff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993822Reviewed-by:
Ivan Šandrk <isandrk@chromium.org> Commit-Queue: Anatoliy Potapchuk <apotapchuk@chromium.org> Cr-Commit-Position: refs/heads/master@{#730139}
-
Markus Handell authored
This change fixes a problem where MediaStreamVideoTrack would would CHECK-fail when the source has been cleared or deallocated AND a call to either SetEnabled, AddEncodedSink or RemoveEncodedSink occurs. The change also includes a new unit test for this case which was previously uncovered. Change-Id: Iab02df69277b2d2a287e2505977ce94345afb848 Bug: 1013590 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993291Reviewed-by:
Henrik Boström <hbos@chromium.org> Commit-Queue: Markus Handell <handellm@google.com> Cr-Commit-Position: refs/heads/master@{#730138}
-
Markus Handell authored
This change fixes a crash in RequestRefreshFrame and also a few other potential cases found during code inspection. Bug: 1040626 Change-Id: I1cdeaa76b530b833dbdad8ab239ae66ee08bac60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994287Reviewed-by:
-
Olya Kalitova authored
Adds failure details in case default Crostini configuration using Ansible has failed. TEST: deployed on DUT and checked that logs are present Bug: 1000287 Change-Id: I4215bb117ed82fe8829ea5375767000645326915 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1991561Reviewed-by:
Nic Hollingum <hollingum@google.com> Commit-Queue: Olya Kalitova <okalitova@chromium.org> Cr-Commit-Position: refs/heads/master@{#730136}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/a104a789f873..f6f813d450e5 git log a104a789f873..f6f813d450e5 --date=short --first-parent --format='%ad %ae %s' 2020-01-10 khokhlov@google.com [py_trace_event] Support clock snapshots in proto trace format Created with: gclient setdep -r src/third_party/catapult@f6f813d450e5 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/catapult-autoroll Please CC crouleau@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md 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 Bug: chromium:990304 Tbr: crouleau@google.com Change-Id: Ie00fda30a7af9b9330a96400879c164e0d846f08 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994084Reviewed-by:
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/72ee5754..e195519d 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: I5c29cdd5bb0f59a1f365f9983832fffda65ec8f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993763Reviewed-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@{#730134}
-
Gauthier Ambard authored
This CL adds the UIAccessibilityTraitNotEnabled to the search engine cells when they are not interactable. Fixed: 1040497 Change-Id: Iec65f625d7bf3d7f738d82ab86b204c3c58a6099 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994284 Commit-Queue: Gauthier Ambard <gambard@chromium.org> Commit-Queue: Robbie Gibson <rkgibson@google.com> Auto-Submit: Gauthier Ambard <gambard@chromium.org> Reviewed-by:
Robbie Gibson <rkgibson@google.com> Cr-Commit-Position: refs/heads/master@{#730133}
-
Vasilii Sukhanov authored
TBR=erikchen@chromium.org Bug: 989810 Change-Id: I45c6ba5ddc575e8c5202ca32db5165169de1421b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994289Reviewed-by:
-
Mikel Astiz authored
It reuses a screenshot previously uploaded for IDS_SYNC_ERROR_PASSWORDS_USER_MENU_TITLE. Bug: 1036454 Change-Id: I4388b36516d040b4314197f9b4f642d9577c3523 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995160 Auto-Submit: Mikel Astiz <mastiz@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Commit-Queue: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#730131}
-
Anders Hartvoll Ruud authored
BUG=545324 Change-Id: Ib7c79ad352a8d68a7815ca992f25280e5c980561 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1986797 Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by:
Xiaocheng Hu <xiaochengh@chromium.org> Cr-Commit-Position: refs/heads/master@{#730130}
-
Alex Danilo authored
Quickview loads image previews by calling decode() on the <img> element after its 'src' attribute is set. When the image is finished decoding it should replace the previous decoded image. Changes decode() failures to send a message to the container that decode failed and in turn, set the contentURL to '' which in turn unloads the webview and displays the 'no preview available' icon. Bug: 645021 Tests: browser_tests --gtest_filter="*QuickViewBrokenImage" Change-Id: Ie1d19f1a4f1014486eaaec9581007f25d4c7f165 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992954 Commit-Queue: Noel Gordon <noel@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#730129}
-
Clemens Backes authored
We plan to run a finch trial on mobile chrome to test different compilation strategies. For this, we need to separate enabling Liftoff from enabling tiering. The finch config could then enable Liftoff but disable tiering - a configuration which is not possible currently. Note that this CL does not change the default configuration. On Desktop, we enable both Liftoff and tiering. On mobile platforms, Liftoff is disabled, so the tiering flag has no effect. R=ahaas@chromium.org, jochen@chromium.org Bug: 1040030, 1040061 Change-Id: I7cd0a8907d84388d15cb49663d18fe4c5c81dd83 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1988360 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
Jochen Eisinger <jochen@chromium.org> Reviewed-by:
Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#730128}
-
Monica Basta authored
This CL implements communicating the sWAA to |chrome://settings/syncSetup| as part of the friendly settings project. The sWAA bit will be fetched and shown in the sync section. Its value depends on the following factors: 1- Data is encrypted with custom passphrase or not. If yes, Google has no access to the data and can not use history to provide personalized experience. In that case, sWAA is 'Off'. 2- History sync is On/Off. This pref is set per device which means history from this device can not be used for personalization. We show 'Off' as well. 2- History recording is enabled/disabled in |Web and Activity| in the Activity control page. If the user does not have encryption and history sync is On, then sWAA will be On if history recording is enabled and Off otherwise. The sWAA can be in one of the following states: 1- Not fetched: On startup, sync is off, feature |kSyncSetupFriendlySettings| is disabled. In that case, no changes is reflected in the UI. 2- Fetching: we show a spinner. The request is pretty fast and the spinner is almost not visible. 3- Failed: If we fail for any reason to fetch the sWAA bit. Also, in that case no changes to the UI. 4- On: We show sWAA state 'On' + hint to reflect how will this affect the user experience. 5- Off: We 'Off' + hint to indicate the reason why Google can not use history to provide personalized experience whether it's because of encryption or history sync off or history recording toggled off. To guarantee we show the most up to date value, we refresh sWAA on the following events: On navigation to page, Sync turned on, Encryption, History sync toggled, sync pref changes in case we previously failed to fetch (fetch failures sometimes are due to sync service not active yet) and page is visible. Bug: 1035421 Change-Id: I0577b0ff76bfd7d66415416fdfba5f91f4e34316 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973915 Commit-Queue: Monica Basta <msalama@chromium.org> Reviewed-by:
Mihai Sardarescu <msarda@chromium.org> Reviewed-by:
Nicolas Ouellet-Payeur <nicolaso@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
-
Vasilii Sukhanov authored
TBR=eirage@chromium.org Bug: 1040874 Change-Id: Iec6b2cc5a72e1b3256d66b8acf09f515e8a0b250 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995164Reviewed-by:
-
Richard Knoll authored
The P2PSocketManager resolves host names in GetHostAddress and responds with the supplied callback. That callback is dropped in the destructor which can happen if there is a mojo connection error. We need to close the pipe to the mojom::P2PSocketManager before doing that as mojo will check if the connection is still active when dropping a callback. Bug: None Change-Id: I2a1e411f5aba21a375e33bd242b67f64c9362a8e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1991560Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Commit-Queue: Richard Knoll <knollr@chromium.org> Cr-Commit-Position: refs/heads/master@{#730125}
-
Alice Wang authored
This CL tests and refactors the SignOutDialogFragment. Bug: 967374 Change-Id: Ibe0af76022877305b38513d5855e238465635469 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1982557 Commit-Queue: Alice Wang <aliceywang@chromium.org> Reviewed-by:
Tanmoy Mollik <triploblastic@chromium.org> Reviewed-by:
-
Vasilii Sukhanov authored
This reverts commit d140b7a4. Reason for revert: Broke crashpad_tests reliably https://ci.chromium.org/p/chromium/builders/ci/Win10%20Tests%20x64%20%28dbg%29/12597 Original change's description: > Enable init_stack_vars for non-official Debug Windows builds > > Debug build is fixed with: crrev.com/c/1973353 > > Bug: 977230, 1030261 > Change-Id: Idcb24d092247f6bc7438c74b6405b4b93539507d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1970852 > Commit-Queue: Vitaly Buka <vitalybuka@chromium.org> > Reviewed-by: Vitaly Buka <vitalybuka@chromium.org> > Reviewed-by: Hans Wennborg <hans@chromium.org> > Cr-Commit-Position: refs/heads/master@{#728840} TBR=hans@chromium.org,vitalybuka@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 977230, 1030261 Change-Id: Iad7d92e12299365b4a45a5237c3bc5e371e33dbe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993964Reviewed-by:
-
Richard Knoll authored
The latest beta of 10.15.3 fixed the issue where an XPC service could not show notifications. This removes the workaround we put in place in https://crrev.com/c/1883648 for macOS 10.15.3+ but keeps it for earlier versions of 10.15. Bug: 1007418 Change-Id: I928dac7366c9e7faee793dd72d282b031e535092 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1991637 Commit-Queue: Richard Knoll <knollr@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#730122}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/9dbcda838560..a104a789f873 git log 9dbcda838560..a104a789f873 --date=short --first-parent --format='%ad %ae %s' 2020-01-10 dberris@chromium.org Fix dispatch routing Created with: gclient setdep -r src/third_party/catapult@a104a789f873 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/catapult-autoroll Please CC crouleau@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md 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 Bug: chromium:1035930 Tbr: crouleau@google.com Change-Id: I895bd006cf70d17e86fc254e5382c50f708cbe76 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994259Reviewed-by:
-
Eric Seckler authored
Replaces SyncChannel::Send, RenderProcessHostImpl::Send, and GpuChannelHost::Send trace events with typed trace events. Also adds a utility to convert the IPC class ID to a corresponding protobuf enum. Corresponding proto buffer definitions for these events were added in aosp/1180211. Typed trace events will allow inclusion of the event arguments in slow reports data in the future. The trace format is protocol-buffer based under the hood already (see docs.perfetto.dev for details), this patch adds strong typing for the arguments of the respective events only. TBR: sunnyps@chromium.org Bug: 644264 Change-Id: I91c71230e62161b08faec889bf9eb70639ae0b5e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1950986 Commit-Queue: Eric Seckler <eseckler@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Reviewed-by:
Ken Rockot <rockot@google.com> Cr-Commit-Position: refs/heads/master@{#730120}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/c83d5e24..72ee5754 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: Iaa8b427cf8b0d55d57713ff008eca12ecf809f08 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993762Reviewed-by:
-
Stepan Khapugin authored
Since UIRefresh had long been the only option, remove references to it in constant names. Bug: none Test: none Change-Id: Ifb3cdb5fec82ad4ea015014c098685010b04e81e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1991455 Auto-Submit: Stepan Khapugin <stkhapugin@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/9b289b2c2973..4b6df1777cba git log 9b289b2c2973..4b6df1777cba --date=short --first-parent --format='%ad %ae %s' 2020-01-10 thomasanderson@chromium.org Update Linux documentation links Created with: gclient setdep -r src/third_party/webrtc@4b6df1777cba If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I6d041aea175da5de05ec33c24756cce67befcaa8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995141Reviewed-by:
-
Anders Hartvoll Ruud authored
BUG=545324 Change-Id: Ic90b7e417accdbf64b110f70db41369e2edec0cb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1986831Reviewed-by:
-
Steve Anton authored
Linux limits the thread name to 15 characters which was cutting off the signaling/worker distinction. Bug: None Change-Id: Ibbbfdf1cedd0add91a8c3aa5c5b5cac6a06d4168 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994050 Auto-Submit: Steve Anton <steveanton@chromium.org> Reviewed-by:
Harald Alvestrand <hta@chromium.org> Commit-Queue: Harald Alvestrand <hta@chromium.org> Cr-Commit-Position: refs/heads/master@{#730115}
-
Raphael Kubo da Costa authored
web-platform-tests has recently gained the ability to set the permission associated to a permission type via test_driver.set_permission(), in a similar fashion to Blink's testRunner.setPermission(). This is CL #1 of a few, and the ultimate goal is to add an implementation of set_permission() to testdriver-vendor.js, so that we can replace uses of testRunner.setPermission(), and consequently move more Blink-specific tests to WPT. This CL adds a new .mojom file to third_party/blink/public/mojom/permissions that allows setting the permission associated with a given permission type, in a similar fashion to testRunner.setPermission(). This API is only intended for use in tests, so the new PermissionAutomation interface is added to a separate file that is part of the blink.test.mojom module, and it is only implemented by content_shell. It then plugs it into the internals object. While in the short term it adds another way to achieve the same thing in layout tests, this was done for a couple of reasons: * test_driver.set_permission() takes a PermissionDescriptor (from the Permissions API) rather than a string that does not necessarily match the permission name as specified in the Permissions API. It makes sense to use standardized APIs, so rather than adding code to convert a PermissionDescriptor into a string accepted by testRunner's setPermission(), internals.setPermission() also takes a PermissionDescriptor. * Since testRunner is implemented entirely in //content/shell, we cannot have its code call Blink to convert a JS value representing the descriptor into a blink::mojom::PermissionDescriptorPtr. By Onion Soup'ing the code to set permissions, we can do all the PermissionDescriptor parsing in Blink and just call the PermissionAutomation implementation in content shell's browser side. For this, we change the internals object in Blink and bypass testRunner altogether. * The new API also gives us more flexibility: it returns a promise so that we can be sure the permission changes really have an effect before executing the rest of the code in a test. A few layout tests have been converted to the new API to show it works. Once existing uses of testRunner.setPermission() are converted, we can remove it altogether, and have internals.setPermission() be part of the implementation of testdriver.js' set_permission() call. Bug: 1030663 Change-Id: I3f40a9facd521ac41c4506b4043ecd5c831586fd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1958117Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Balazs Engedy <engedy@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Reviewed-by:
Mounir Lamouri <mlamouri@chromium.org> Commit-Queue: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> Cr-Commit-Position: refs/heads/master@{#730114}
-
Jérôme Lebel authored
Removing SigninAccountSelectorViewController class. It was used to select an account before Unity UI. This class should have been removed with crrev.com/c/1778868. And renaming -[ChromeSigninViewController signinCompletedWithUnity] into -[ChromeSigninViewController signinCompleted]. Bug: 951313 Change-Id: I7012595fdd6de754ed60ac4bb17d0dd9951affbe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1991454 Commit-Queue: Jérôme Lebel <jlebel@chromium.org> Auto-Submit: Jérôme Lebel <jlebel@chromium.org> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#730113}
-
chromium-autoroll authored
Roll ChromeOS orderfile from 81-3987.18-1577705382-benchmark-81.0.4013.0-r1 to 81-3987.18-1577705382-benchmark-81.0.4016.0-r1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/cros-orderfile-chromium Please CC c-compiler-chrome@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Tbr: c-compiler-chrome@google.com Change-Id: I2f7962cd02def14c638147afcb8c3e0610c89536 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995144Reviewed-by:
-
Takashi Toyoshima authored
cors::CheckAccessInternal() ensures if the HTTP response status is set to a non-zero value. This code was originally introduced in Blink side, but it's out-of-spec implementation. CORS preflight response expects an ok status for CORS checks and our implementation implicitly rejects the status 0. Actual response does not have such CORS specific status code check, and fetch() or XHR can receive an error status as long as the response has a right access control headers. But since 0 is not used in HTTP, we don't need such check in CORS code. So, let's remove this stale check and relevant test, WebAssociatedURLLoaderTest. CrossOriginWithAccessControlFailureBadStatusCode. This was added by https://codereview.chromium.org/110273006/, but the original change's intention does not help developers today. Also note that usual server applications such as Apache converts this kind of invalid status from CGI to 500 to assume such situation as an internal server error. This patch also integrate the ok status check into the cors::PreflightAccessCheck so to minimize exposed functions. Bug: 1039174 Change-Id: Ib8f8d84e200a01884daab9d726ac52b38e36a591 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1983696 Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
-
Ionel Popescu authored
*** SHERIFFS: if this CL triggers a flaky layout test, PLEASE do not *** revert this CL. Instead, please disable the offending test(s) and *** add them to the crbug.com/1035582 section of TestExpectations. I *** will then take care of them as I fix up the remainder of these *** tests. Feel free to cc me if you create a bug. Thanks. This CL updates the focus ring to be made of two borders which have a 2:1 ratio. The new width of the focus ring is 3px: 2px nearly black (#101010), followed by 1px white. If the element has a border large enough to have an inset outline (width >= 1px) then we are going to inset the focus ring by 1px as we want it to be partially drawn over the border to avoid clipping or strange alignment issues caused by increasing the width to 3px. For elements that have not been styled and that have an appearance, the border radius of the focus ring is updated to be the same as the one used for drawing the element. For all other cases the current behavior is maintained: border radius = outline width. Tests are added to validate the new focus ring for multiple scenarios (see controls-refresh/focus-rect) Bug: 1026553 Change-Id: Ibe05cf6b7336198bd9513174493f51da5108339a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1975072 Commit-Queue: Ionel Popescu <iopopesc@microsoft.com> Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Reviewed-by:
Mason Freed <masonfreed@chromium.org> Cr-Commit-Position: refs/heads/master@{#730110}
-
Takuto Ikuta authored
chrome_public_test_apk passes now. https://luci-milo-dev.appspot.com/p/chromium/builders/ci/Android%20N5X%20Swarm/10131 This was introduced in crrev.com/3400947e Bug: 955013, 731759 Change-Id: I4b73a7efcf5052d83df66021580a233ece3e66fe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993002 Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Reviewed-by:
Yoshisato Yanagisawa <yyanagisawa@google.com> Commit-Queue: Takuto Ikuta <tikuta@chromium.org> Cr-Commit-Position: refs/heads/master@{#730109}
-
