- 03 Nov, 2020 40 commits
-
-
James Hollyer authored
Pointer Lock Options was not set up to run tests while enabled. This CL fixes that and then fixes the necessary tests so that all runs smoothly when the flag is enabled by default. Bug: 1124396 Change-Id: Ie1d9b431b89a4cce77023d9c3aadad4e2d824be2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2431459Reviewed-by:
Reilly Grant <reillyg@chromium.org> Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Commit-Queue: James Hollyer <jameshollyer@chromium.org> Cr-Commit-Position: refs/heads/master@{#823566}
-
Chris Sharp authored
List the defaults for: AccessibilityImageLabelsEnabled AdsSettingForIntrusiveAdsSites AllowScreenWakeLocks ClientCertificateManagementAllowed CrostiniArcAdbSideloadingAllowed DeviceCrostiniArcAdbSideloadingAllowed Bug: 1139046 Change-Id: Ib9325f5739f1c353356af4fd574d126db3f2042b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2514619 Commit-Queue: Chris Sharp <csharp@chromium.org> Reviewed-by:
Pavol Marko <pmarko@chromium.org> Cr-Commit-Position: refs/heads/master@{#823565}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/33fdba02..ba40ae7e 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,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I2f3e4f59a04026e3030436bec38e7a683ec63fd8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2517140Reviewed-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@{#823564}
-
Peter Kasting authored
Bug: 772945 Change-Id: I44ef7ea9c2e4e7f770860016fc5f1e205e2d1212 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516882 Commit-Queue: Xiyuan Xia <xiyuan@chromium.org> Auto-Submit: Peter Kasting <pkasting@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#823563}
-
Aleks Totic authored
Make all rows share the same TableConstraintSpaceData by replacing it if we are reusing the fragment. Bug: 958381 Change-Id: I7647d69d930218f1dfaac2cefdd8a49ba936ceaf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2511431 Commit-Queue: Aleks Totic <atotic@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#823562}
-
chromium-internal-autoroll authored
Release_Notes: http://go/media_app-x20/relnotes/Main/media_app_202011030600_RC00.html https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/media_app/app/+/W59w4eCMof8bZydvlzS33CNelnDp1ZjryOeIUy5x1Z8C If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/media-app-chromium-autoroll Please CC media-app@grotations.appspotmail.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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: b/162468431,b/170172788 Tbr: media-app@grotations.appspotmail.com Change-Id: Idb89546d3bfe436d6bd94717a2810598af329c2c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516912Reviewed-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@{#823561}
-
Jan Wilken Dörrie authored
This change implements checking a password for weakness after it has been modified in the Desktop Password Check UI. In case the new password is / remains weak, and will be added / kept in the section of weak passwords. Fixed: 1142377 Change-Id: I03ffc9c087059926fe3f12a50594317235f5383b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2514379 Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org> Reviewed-by:
Friedrich [CET] <fhorschig@chromium.org> Cr-Commit-Position: refs/heads/master@{#823560}
-
Denis Kuznetsov authored
Bug: 1144159 Change-Id: I8e945efe328bface5181a3e42155b88801a1c794 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2510134 Commit-Queue: Denis Kuznetsov [CET] <antrim@chromium.org> Reviewed-by:
Renato Silva <rrsilva@google.com> Cr-Commit-Position: refs/heads/master@{#823559}
-
David Van Cleve authored
The CSP data structures in Blink currently use a value of 0 to denote an unspecified or default-valued port in CSP source expressions. However, origins can also have ports explicitly set to 0. In order to resolve behavior inconsistencies between blink::SecurityOrigin, which currently doesn't support port 0, and url::Origin, which does, we're updating blink::SecurityOrigin to distinguish port-0 origins from origins with unspecified (default-valued) ports. This makes SourceListDirectiveTest.GetSources CSP tests fail, because it means that a "self" CSPSource created by ContentSecurityPolicy::SetupSelf from an origin with the default port will no longer have the same port as a CSPSource created by parsing a host-source source expression with no port. To fix this, we update CSPSource's port_ member to have a new default state denoting an unspecified or default-valued port, distinct from the value 0 which now specifically represents port 0. Bug: 1136678 Change-Id: Ic386fc2ba31e13c95676ecf050e24874d4af132e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2477044 Commit-Queue: David Van Cleve <davidvc@chromium.org> Reviewed-by:
Andy Paicu <andypaicu@chromium.org> Cr-Commit-Position: refs/heads/master@{#823558}
-
Vidhan authored
Added tests for inserting the states data consisting of UTf8 strings in AlternativeStateNameMapUpdater. Bug: 1111960 Change-Id: Iee96de3ceb3b6c3726d7bffc685aab29293c23f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2513215Reviewed-by:
Matthias Körber <koerber@google.com> Reviewed-by:
Christoph Schwering <schwering@google.com> Commit-Queue: Vidhan Jain <vidhanj@google.com> Cr-Commit-Position: refs/heads/master@{#823557}
-
Chromium WPT Sync authored
Using wpt-import in Chromium 2c5003d7. Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md Directory owners for changes in this CL: rego@igalia.com: external/wpt/css/selectors NOAUTOREVERT=true TBR=robertma@google.com No-Export: true Cq-Include-Trybots: luci.chromium.try:linux-wpt-identity-fyi-rel,linux-wpt-payments-fyi-rel Change-Id: I6bc3af89ca1ffbb19e1bc550c2822535eba1e2f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2517139Reviewed-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@{#823556}
-
Ben Mason authored
TBR=govind@chromium.org Change-Id: I25cb100a0724ae4d66aa8759f97124d9fcfb3b70 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2515135Reviewed-by:
Ben Mason <benmason@chromium.org> Commit-Queue: Ben Mason <benmason@chromium.org> Cr-Commit-Position: refs/heads/master@{#823555}
-
Caitlin Fischer authored
The status quo test compares the actual header with the header returned by GetClientDataHeaders(). However, as discussed in [1], the important thing to verify is that the GOOGLE_WEB_PROPERTIES_SIGNED_ID-associated VariationID is included in the header when expected. Similarly, update the UserNotSignedIn test to check that the ID is not included in the header. Also, remove CreateTrialAndAssociateId() from the browser test file since it now exists in variations_test_utils.h. [1] https://chromium-review.googlesource.com/c/chromium/src/+/2461906/comment/d6233bfd_454a08ff/ Bug: 1134444 Change-Id: I22101a138f930e2b1cfaf4ba3f74211eb87c9a49 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2508338Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
David Benjamin <davidben@chromium.org> Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Cr-Commit-Position: refs/heads/master@{#823554}
-
Michael Thiessen authored
Part 3 of a 3-sided change to move CriteriaNotSatisfiedException to base/ Bug: 1134178 Change-Id: Ie76869351d8a09bd92205e3aef3ffea65220c01a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2515520Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Commit-Queue: Michael Thiessen <mthiesse@chromium.org> Cr-Commit-Position: refs/heads/master@{#823553}
-
Michael Checo authored
Spec: http://shortn/_O6M4tRc5EQ Screenshot: http://shortn/_mosolq202i Bug: 1059779 Test: browser_tests --gtest_filter=ScanningAppBrowserTest.All Change-Id: Icb29009332fea0de87eefacd82259ab695109a21 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2506302 Commit-Queue: Michael Checo <michaelcheco@google.com> Reviewed-by:
Zentaro Kavanagh <zentaro@chromium.org> Reviewed-by:
Jimmy Gong <jimmyxgong@chromium.org> Cr-Commit-Position: refs/heads/master@{#823552}
-
Peter Marshall authored
We are no longer passing the API key to the frontend to perform the survey so this CL deletes getAPIKey which is not used. The devtools frontend now triggers the existing Chrome HaTS impl to run the survey. CanShowSurvey will be used to determine whether we show the survey link in the devtools frontend, and then ShowSurvey will be used when the link is clicked. Bug: 1112738 Change-Id: Ia456e419c2678cfe6c90976d82af8d37f1ac435f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2509570 Commit-Queue: Peter Marshall <petermarshall@chromium.org> Reviewed-by:
Andrey Kosyakov <caseq@chromium.org> Reviewed-by:
Tom Sepez <tsepez@chromium.org> Cr-Commit-Position: refs/heads/master@{#823551}
-
Rainhard Findling authored
Bug: 1087263 Change-Id: Ie404c10b503f7951007ec6eba445fdffe8ab2a3c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2513655Reviewed-by:
Joe Mason <joenotcharles@chromium.org> Reviewed-by:
Esmael Elmoslimany <aee@chromium.org> Commit-Queue: Rainhard Findling <rainhard@chromium.org> Cr-Commit-Position: refs/heads/master@{#823550}
-
Owen Min authored
When previous real time extension request is generated less than 1 minute or haven't got response from the server, all new requests will be batched and wait. In case of any error, the throttler will stop working until the next successfully upload. In case of policy change, the throllter will be deleted or created. The throttle creation is also behind the feature flag. Bug: 1137964 Change-Id: I6b3e7158163959211abc13a77ae07058c8ef99dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505445Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Commit-Queue: Owen Min <zmin@chromium.org> Cr-Commit-Position: refs/heads/master@{#823549}
-
Dave Tapuska authored
This reverts commit f86eb723. Reason for revert: Rolling back for now due to concerns over Service Workers Original change's description: > Enable disallowdocumentaccess > > Allow the ability to restrict same origin documents. > Approved intent to ship https://groups.google.com/a/chromium.org/g/blink-dev/c/TzuPAx9ZOk0/m/5num2KNACAAJ > > https://chromestatus.com/feature/5648946183536640 > > BUG=961448 > > Change-Id: Ic3996eb5015484fd3d3220b357d5b17d50413d60 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2417099 > Reviewed-by: Philip Jägenstedt <foolip@chromium.org> > Commit-Queue: Dave Tapuska <dtapuska@chromium.org> > Cr-Commit-Position: refs/heads/master@{#809355} TBR=dtapuska@chromium.org,foolip@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 961448 Change-Id: Idaf3961f6dd1ff3449a75ea1b0a2db6dbb9211a6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2514962Reviewed-by:
-
Joe Mason authored
Make WebMemoryAggregator owned by its callback instead of by itself so that it is also deleted if the callback is dropped. R=ulan Bug: 1085129 Change-Id: I4a7dcdd208c1b02933cf9e94cfcc6bd84502b3ba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2515042Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Joe Mason <joenotcharles@chromium.org> Cr-Commit-Position: refs/heads/master@{#823547}
-
Anders Hartvoll Ruud authored
Fixed: 1114808 Change-Id: I75c1afb4158703af75fe53d4b59155730e289e0b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2513601Reviewed-by:
Kevin Ellis <kevers@chromium.org> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#823546}
-
Karandeep Bhatia authored
Currently when an optional property fails to parse and error generation is enabled for the schema, the auto-generated Populate function continues parsing the type but still populates error. This CL changes the code to ensure that we raise an error in these cases. We also don't raise an error on unrecognized keys any longer since we shouldn't be raising an error while returning a parse success: Most consumers currently don't distinguish between the two cases and this can lead to the returned error being a concatenation of unrelated errors, which is not ideal. We now enforce the constraint that Populate only returns an error iff there is a parse failure. We DCHECK the same in the auto-generated FromValue function. This also brings the code more in-line with what we do for auto-generated manifest parsing. Currently only 3 schemas use error generation: - declarative_net_request.idl - extensions_manifest_types.json - manifest_types.json The latter two may be affected by the change. In particular, parsing manifest types declared by them may lead to a hard error when an optional property can't be parsed now. BUG=1113513 Change-Id: I63966389e25f7591b4425815d32d9da59d35c3fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2500425 Commit-Queue: Karan Bhatia <karandeepb@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Cr-Commit-Position: refs/heads/master@{#823545}
-
Stephane Zermatten authored
Before this change, some actions manipulated the Selectors that they were given to add a requirement that the element has a bounding box. This change removes that. Actions use the selectors that were created by the backend, unmodified. This change relies on the backend taking responsibility for generating selector with the appropriate visibility requirement. Bug: b/164956746 Change-Id: Ifeb29d3b61b44b2c0e5a666fc72df79e1da35b96 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2503553 Commit-Queue: Stephane Zermatten <szermatt@chromium.org> Reviewed-by:
Mathias Carlen <mcarlen@chromium.org> Cr-Commit-Position: refs/heads/master@{#823544}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/89cf59f82a6b..9bed95f88a26 2020-11-03 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.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/+doc/master/autoroll/README.md Bug: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I363f2307528226b42d5c305940e5f56df34b552f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516900Reviewed-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@{#823543}
-
Eric Orth authored
Only significant change is to ignore any params received with alias records. Bug: 1138620 Change-Id: I5d30127b07a5347c6215077ebfb49d0dc8f19b1e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2515560 Auto-Submit: Eric Orth <ericorth@chromium.org> Commit-Queue: Dan McArdle <dmcardle@chromium.org> Reviewed-by:
Dan McArdle <dmcardle@chromium.org> Cr-Commit-Position: refs/heads/master@{#823542}
-
Henrik Boström authored
Prior to this CL, the kWebRtcThermalResource feature was enabled by default on all platform, after having been successfully rolled out with .gcl. However, only on macOS did the thermal resource actually receive any signal from the OS about thermal states, so on non-mac injecting a thermal resource into webrtc did not have any observable affects on adaptation. In order to support platform-specific rollout of this feature, this CL changes the default to DISABLED on all platforms except the one we are confident in: macOS. We want to do this because in M88, thermal states was implemented on ChromeOS, and we want to begin a rollout where the default values of the feature is off. TBR=guidou@chromium.org Bug: chromium:1144734 Change-Id: Id1f746013f8a279f5cc4f6b9cd7e48d9a069f70d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516940Reviewed-by:
Henrik Boström <hbos@chromium.org> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Commit-Queue: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#823541}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/ed916ddf61cc..6a4c9bbd5185 2020-11-03 angle-autoroll@skia-public.iam.gserviceaccount.com Roll SPIRV-Tools from f7da52775714 to 5735576f87be (1 revision) 2020-11-03 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Vulkan-Tools from 3f747ee91e3b to 51c1c5ab56d5 (1 revision) 2020-11-03 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Vulkan-ValidationLayers from e46399ddd2c7 to 1b2f8307f21d (7 revisions) 2020-11-03 angle-autoroll@skia-public.iam.gserviceaccount.com Roll SwiftShader from 7751fe38f474 to b5bf82693f85 (7 revisions) 2020-11-03 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Chromium from a64ace71 to ce54b897 (254 revisions) 2020-11-03 syoussefi@chromium.org Vulkan: Use dst access masks to determine if barrier is needed 2020-11-03 xiaoxuan.liu@arm.com Reland "Add support for Linux vulkan backend with VK_KHR_display" 2020-11-03 courtneygo@google.com Allow single threaded CommandProcessor 2020-11-03 jmadill@chromium.org Test Runner: Robustly handle unexpected crashes. 2020-11-03 m.maiya@samsung.com Vulkan: Bug fix in sRGBDecode logic 2020-11-02 jmadill@chromium.org Test Runner: Add ability to retry flaky tests. 2020-11-02 angle-autoroll@skia-public.iam.gserviceaccount.com Roll VK-GL-CTS from e69b9b7294af to 9e07e4424cd4 (5 revisions) 2020-11-02 thomasanderson@chromium.org Remove dependency on //build/config/linux:x11 2020-11-02 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Chromium from f2fabcd1 to a64ace71 (130 revisions) 2020-11-02 jmadill@chromium.org Expand suppression of new EGL test. 2020-11-02 syoussefi@chromium.org Noop clear of non-existing attachments. 2020-11-02 syoussefi@chromium.org Noop empty-scissor clears 2020-11-02 jmadill@chromium.org Revert "Add support for Linux vulkan backend with VK_KHR_display" 2020-11-02 jmadill@chromium.org Tests: Print warning when we hit display reuse limit. 2020-11-02 syoussefi@chromium.org Vulkan: Fix prerotation bug with glInvalidateSubFramebuffer 2020-11-02 amy.liu@arm.com Fix maxShaderAtomicCounters value. 2020-11-02 xiaoxuan.liu@arm.com Add support for Linux vulkan backend with VK_KHR_display 2020-11-02 angle-autoroll@skia-public.iam.gserviceaccount.com Roll SPIRV-Tools from 34ae8a475754 to f7da52775714 (8 revisions) 2020-11-02 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Vulkan-ValidationLayers from f673b4e6ebf3 to e46399ddd2c7 (11 revisions) 2020-11-02 angle-autoroll@skia-public.iam.gserviceaccount.com Roll glslang from 740ae9f60b00 to 142cb87f803d (1 revision) 2020-11-02 angle-autoroll@skia-public.iam.gserviceaccount.com Roll SwiftShader from e6c9497255c6 to 7751fe38f474 (3 revisions) 2020-11-02 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Vulkan-Headers from 320af06cbdd2 to 87451c55aa8b (1 revision) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC courtneygo@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/+doc/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-asan;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: chromium:1066670 Tbr: courtneygo@google.com Test: Test: dEQP-GLES31.functional.shaders.opaque_type_indexing.atomic_counter.*vertex Change-Id: Iab4601f31e54eb61b24d15c309855d3f64896002 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516903Reviewed-by:
-
sauski authored
Changed the flag which controls whether a HaTS v1 or HaTS Next survey is launched to default to launching HaTS Next surveys, instead of HaTS v1. This flag by itself does not change any behavior, and must be combined with a survey feature to deliver a survey. No HaTS v1 surveys are currently running in Chrome, and the service has been deprecated. Bug: 1110888 Change-Id: I49a97cda08e5cd7a79195b4da9ad9f5cca645bfa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2514209 Commit-Queue: Theodore Olsauskas-Warren <sauski@google.com> Reviewed-by:
Sean Harrison <harrisonsean@chromium.org> Cr-Commit-Position: refs/heads/master@{#823539}
-
Sergey Poromov authored
The screen recording part of the new screen capture feature should be connected to the same SCREENSHOT restriction in DLP policy. Tests: New browsertest Bug: 1133324 Change-Id: If43440522edde5b1d4cc51400ec7f501c9d63074 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2510330 Commit-Queue: Sergey Poromov <poromov@chromium.org> Reviewed-by:
Nikita Podguzov <nikitapodguzov@chromium.org> Cr-Commit-Position: refs/heads/master@{#823538}
-
Clemens Backes authored
The inspector fuzzer was added to v8 in https://crrev.com/c/2505722. R=mmoroz@chromium.org CC=ahaas@chromium.org Bug: chromium:1142437 Change-Id: I5d2271f222ce91327eed1c03a548054a190e9c2b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2510132Reviewed-by:
Andreas Haas <ahaas@chromium.org> Reviewed-by:
Max Moroz <mmoroz@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#823537}
-
Ken Buchanan authored
FrameConnectorDelegate was created to provide a delegation interface for RenderWidgetHostViews in content/browser/renderer_host to interact with embedding frames in content/browser/frame_host without breaking layering rules. Since http://crrev.com/805452 and its follow up CLs, frame_host has been merged into renderer_host, making the delegation unnecessary. Change-Id: I2450938c8d48aba8fd35451d9a6dca030a8e8d71 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2515120Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Ken Buchanan <kenrb@chromium.org> Cr-Commit-Position: refs/heads/master@{#823536}
-
Jan Wilken Dörrie authored
This change enables the WellKnownChangePassword feature by default. Bug: 927473 Change-Id: I05f4fdae2fd4364fc5b184c25339244ec0fcaece Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2513216 Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org> Reviewed-by:
-
Mahmoud Gawad authored
cros_healthd had removed two paramters from two battery routines: - |low_mah| and |high_mah| from 'BatteryCapacityRoutine'. - |maximum_cycle_count| and |percent_battery_wear_allowed| from 'BatteryHealthRoutine'. This CL removes the corresponding parameters from the corresponding routines found in TelemetryExtension in both: - Mojo interface exposed to Telemetry SWXs. - WebIDL interface exposed to third-party code. Also removes the dependency on the removed parameters from browser_tests. Bug: b:171327161 Change-Id: Idaa57d0a05986883c26337a151f0c0adfb5f5272 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2507698Reviewed-by:
Oleh Lamzin <lamzin@google.com> Commit-Queue: Mahmoud Gawad <mgawad@google.com> Cr-Commit-Position: refs/heads/master@{#823534}
-
Mason Freed authored
This just changes the wording for the deprecation message for the :unresolved pseudo selector. Instead of "will be removed", it now just says "removed". Bug: 937746 Change-Id: I694bcefabf34f9399000206d30da50b62fbf01b9 Cq-Do-Not-Cancel-Tryjobs: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2514081Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Commit-Queue: Mason Freed <masonfreed@chromium.org> Auto-Submit: Mason Freed <masonfreed@chromium.org> Cr-Commit-Position: refs/heads/master@{#823533}
-
chromium-autoroll authored
Roll Chrome Linux PGO profile from chrome-linux-master-1604382852-89adcc94b5376db481c405a47786acd9d71a0a15.profdata to chrome-linux-master-1604404061-a0e49f41ece3a518deb5950cf222a12f66659bab.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-linux-chromium Please CC pgo-profile-sheriffs@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: Ia62dbdfaf5cd6dc97a01279f8bfcbf940b5b2fbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516906Reviewed-by:
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/ee24eb66d23f..42cafa5696f5 2020-11-03 nisse@webrtc.org Delete legacy stats minWaitingTimeMs and medianWaitingTimeMs from ACM. 2020-11-03 nisse@webrtc.org Replace RWLockWrapper --> Mutex in ScreenCapturerHelper 2020-11-03 natim@webrtc.org Adding total duration and more test cases to VoipStatistics. 2020-11-02 terelius@webrtc.org Fix incorrect ToUnsigned in RTC event log. 2020-11-02 hta@webrtc.org Check for oversized TURN usernames 2020-11-02 nisse@webrtc.org Delete master_timing argument to VCMTiming. 2020-11-02 jakobi@webrtc.org Reland "Reland "Default enable WebRTC-SendSideBwe-WithOverhead."" 2020-11-02 gustaf@webrtc.org Increased high frequency transparency 2020-11-02 jakobi@webrtc.org Use non-null transport for RTCP in AV sync test. 2020-10-30 philipp.hancke@googlemail.com doc: mention video_replay tool for reporting video bugs 2020-10-30 mbonadei@webrtc.org Reformat python files checked by pylint (part 1/2). 2020-10-30 nisse@webrtc.org Delete internal locking in TimestampExtrapolator class. 2020-10-30 hta@webrtc.org Remove obsolete GetRemoteAudioSSL* functions. 2020-10-30 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 2abf60f7..2357c735 (822386:822514) 2020-10-29 deadbeef@webrtc.org Free data if SCTP packet is delivered after transport destruction. 2020-10-29 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 0cbb40a9..2abf60f7 (822259:822386) 2020-10-29 alessiob@webrtc.org AGC2 RNN VAD size_t -> int 2020-10-29 deadbeef@webrtc.org Update set of known root certificates. 2020-10-29 auorion@microsoft.com Add and refactor functionality into rtc_base/win 2020-10-29 alessiob@webrtc.org RNN VAD: Pitch periods as integers and for-if-break optimization 2020-10-29 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision c8ecd260..0cbb40a9 (822116:822259) 2020-10-29 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 28455e96..c8ecd260 (821997:822116) 2020-10-29 ssilkin@webrtc.org Analyze quality of dropped frames in VideoProcessor. 2020-10-29 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision a9d053b9..28455e96 (821860:821997) 2020-10-28 natim@webrtc.org VoipStatistics subAPI and implementation. 2020-10-28 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 3201204f..a9d053b9 (821703:821860) 2020-10-28 ivoc@webrtc.org Reset NetEq simulation step time if a large gap is detected. 2020-10-28 philipel@webrtc.org Removed _completeFrame since we never allow incomplete frames. 2020-10-28 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 5c9a5207..3201204f (821334:821703) 2020-10-28 nisse@webrtc.org Fix locking in RTPFile class 2020-10-27 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 473d43b3..5c9a5207 (821175:821334) 2020-10-27 sprang@webrtc.org Updates how min bitrate is set for VP9 SVC in perf tests. 2020-10-27 ivoc@webrtc.org Remove deprecated PacketArrived method from NetEqController interface. 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/+doc/master/autoroll/README.md Bug: chromium:1127774,chromium:1144646 Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: If0271b1a073b8bab73994f09e702f2bdfecbb071 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516902Reviewed-by:
-
Gayane Petrosyan authored
This reverts commit 3dcbf868. Reason for revert: Msan failure Bug: 1145157 Original change's description: > [CrOS PhoneHub] Add notification metrics. > > We add metrics for PhoneHub notification actions by introducing' a new > PHONE_HUB notification type. This way, metrics will be logged into > existing histograms. > > Additionally, this CL also adds a new Ash.PhoneHub.NotificationCount > histogram counting the number of active PhoneHub notifications. > > BUG=1138137,1106937 > > Change-Id: I4529eb6cc0d861ec9eb720e4eeac5c6d2d6257ce > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505728 > Commit-Queue: Tim Song <tengs@chromium.org> > Reviewed-by: Ilya Sherman <isherman@chromium.org> > Reviewed-by: Yoshiki Iguchi <yoshiki@chromium.org> > Reviewed-by: Kyle Horimoto <khorimoto@chromium.org> > Reviewed-by: Andre Le <leandre@chromium.org> > Cr-Commit-Position: refs/heads/master@{#823474} TBR=yoshiki@chromium.org,khorimoto@chromium.org,isherman@chromium.org,tengs@chromium.org,leandre@chromium.org Change-Id: I523202c3a64f58d267dff229baf69dad1cfe8377 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1138137 Bug: 1106937 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2517241Reviewed-by:
Gayane Petrosyan <gayane@chromium.org> Commit-Queue: Gayane Petrosyan <gayane@chromium.org> Cr-Commit-Position: refs/heads/master@{#823530}
-
Nico Weber authored
For reasons not yet understood, building it on the tot bots makes the tot bots fail. It works fine on the upload bot, so only build it there. This change doesn't affect the clang package we distribute since it's a no-op on the upload bots, and the tot bots don't use the arm64 iossim slice. We still should understand what's going on, since having the tot bots and the upload bots do different things is suboptimal. Bug: 1145151,1138425 Change-Id: Ib8d7a31289ec2caf6ccf2fe6e6ddadb4f908b4c4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2517240Reviewed-by:
Hans Wennborg <hans@chromium.org> Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Cr-Commit-Position: refs/heads/master@{#823529}
-
Tim van der Lippe authored
https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2503953 has landed R=aerotwist@chromium.org Bug: 1143170 Change-Id: I94cee3838e9ba305449b9ce0356f597e13074b7a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2503698 Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org> Reviewed-by:
Paul Lewis <aerotwist@chromium.org> Reviewed-by:
Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#823528}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1604382852-9483a9470fa3ce55e504618f01ab71cbbe527541.profdata to chrome-mac-master-1604404061-6e4b1d6492901c864984b20d97dc0cd527cfcccf.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-mac-chromium Please CC pgo-profile-sheriffs@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:mac-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: Idfa89acd73a3f90ba269a7332e7ce95293055060 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516905Reviewed-by:
-
