- 06 Feb, 2020 27 commits
-
-
Sujie Zhu authored
We add FIDO auth toggle on Clank Autofill Payment settings page. The toggle is shown only when 1) autofill is enabled 2) sync is enabled 3) feature flag is enabled. The requirement check is accomplished by adding one more PersonalDataManager bridge function. We reuse FIDOAuthEnabled preference to show current user's status and record user's intention (intent to opt in/out). The preference is exposed to Java side in order to get/set the preference via PrefServiceBridge. Local tested video (Googlers only): https://drive.google.com/a/google.com/file/d/1nJ1pSJZu1e5oV6qle_Piog6-a-v7kmZs/view?usp=sharing For more detailed background (Googlers only): go/autofill-auth-clank-settings Bug: 949269 Change-Id: Iefad4c953eee4dc00ec54627810b135c1eec6206 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029255 Commit-Queue: Sujie Zhu <sujiezhu@google.com> Reviewed-by:
sebsg <sebsg@chromium.org> Reviewed-by:
Manas Verma <manasverma@google.com> Reviewed-by:
Natalie Chouinard <chouinard@chromium.org> Reviewed-by:
Jared Saul <jsaul@google.com> Cr-Commit-Position: refs/heads/master@{#738766}
-
Ehimare Okoyomon authored
Implement a bridge to connect Java UI to the CookieControlsService for a consistent backend with the web implementation. Bug: 1040091 Change-Id: I023e96d39c14aad20d3d82ff46e560916e595115 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2035894 Commit-Queue: Ehimare Okoyomon <eokoyomon@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Christian Dullweber <dullweber@chromium.org> Reviewed-by:
-
shrekshao authored
Bug: 1013369 Change-Id: I04a8ce5ce11fb6a5d67acc782c2e297224b8685b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029236 Commit-Queue: Shrek Shao <shrekshao@google.com> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#738764}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/01005814aa9a..2fe6351af3c1 git log 01005814aa9a..2fe6351af3c1 --date=short --first-parent --format='%ad %ae %s' 2020-02-05 John.Emau@microsoft.com Console: fix no scroll bug in context selector 2020-02-05 Rob.Paveza@microsoft.com Mismatched SASS source maps cause Performance recording to fail 2020-02-05 aerotwist@chromium.org [e2e] Updates separaters 2020-02-05 aerotwist@chromium.org [e2e] Moves hosted mode server to JS side 2020-02-05 tvanderlippe@chromium.org Remove hello world e2etest 2020-02-05 tvanderlippe@chromium.org Add remaining console startup tests 2020-02-05 khamu@microsoft.com High contrast fix in Console tools panel 2020-02-05 aerotwist@chromium.org [e2e] Moves shared logic out of e2e 2020-02-05 aerotwist@chromium.org [e2e] Fix exit code and paths for bots. 2020-02-05 rayankans@google.com [BackgroundService] Show tooltip over `other domains` checkbox Created with: gclient setdep -r src/third_party/devtools-frontend/src@2fe6351af3c1 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/+/master/autoroll/README.md Bug: chromium:1040254,chromium:1047671,chromium:1048378,chromium:1048978,chromium:1049155 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: If4a5055ceddfc99536987fbf78148ee9a6befa39 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2040250Reviewed-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@{#738763}
-
Isabella Scalzi authored
Add a test that tests deleting an item from Quick View that is part of a check selection. Bug: 803259 Change-Id: Icf9c77eee2fbeb400a981a0ecbe481addffaae2d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2038295 Commit-Queue: Isabella Scalzi <isabellascalzi@google.com> Reviewed-by:
Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#738762}
-
Avery Musbach authored
They were for OverviewController::OnOverviewButtonTrayLongPressed which was moved to SplitViewController in https://chromium-review.googlesource.com/c/chromium/src/+/2024447 Bug: None Change-Id: Id1e0b88c50f05d292040a7a9f04d83bd762c2d1b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2040382Reviewed-by:
Sammie Quon <sammiequon@chromium.org> Commit-Queue: Avery Musbach <amusbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#738761}
-
Livvie Lin authored
When navigating to an error page and then to an error page, going backwards to the first error page does not trigger ErrorRetryStateMachine::DidFailProvisionalNavigation, which breaks the page functionality. This likely occurs since the page is getting loaded from cache, so prevent the breakage by reloading. Bug: 1044768 Change-Id: If1ac325a175fc529086490f3064ec5199cc4ee38 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032185 Commit-Queue: Livvie Lin <livvielin@chromium.org> Reviewed-by:
Carlos IL <carlosil@chromium.org> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#738760}
-
rbpotter authored
Add preprocess=true for some Polymer 3 Web UI/settings files that use <if expr>. Bug: 1026426 Change-Id: If89264703c33983570e4733d4ea4a5927effb81f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2040530Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#738759}
-
Isabella Scalzi authored
Add a test that opens a file with Quick View in single-select mode and deletes it. Checks that the file is deleted, and that Quick View closes. Bug: 803259 Change-Id: I65200e1aac35d86c64c188e9cc30cc0fa9f73ef1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026553 Commit-Queue: Isabella Scalzi <isabellascalzi@google.com> Reviewed-by:
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/d28c5fe2b8b8..6c23cd33e6fe git log d28c5fe2b8b8..6c23cd33e6fe --date=short --first-parent --format='%ad %ae %s' 2020-02-05 brucedawson@chromium.org Fix duplicate header file entry 2020-02-05 brianosman@google.com Stop using Skia's specialized min/max functions 2020-02-05 tsepez@chromium.org Remove stray CJX_Object::InstanceManager_{Set,Move}Instances() decls. 2020-02-05 tsepez@chromium.org Cover CJX_InstanceManager methods from javascript tests. Created with: gclient setdep -r src/third_party/pdfium@6c23cd33e6fe If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pdfium-autoroll Please CC pdfium-deps-rolls@chromium.org 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:1048779 Tbr: pdfium-deps-rolls@chromium.org Change-Id: I1ce1dfa948cd87e8332e014d4bdeae98d888c935 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2040015Reviewed-by:
-
Renjie Tang authored
https://quiche.googlesource.com/quiche.git/+log/4c93e8d76db8..75bbf98f4e18 2020-02-01 bnc Change default QuicStream priority when using IETF QUIC. 2020-01-31 wub gfe-relnote: In QUIC, check nonretransmittable_frames, instead of packet length, to determine if a serialized packet is a MTU probe or not. Protected by --gfe2_reloadable_flag_quic_better_mtu_packet_check. 2020-01-31 wub gfe-relnote: If batch writer is used in a QuicConneciton, flush it right after a MTU probe is sent. Protected by --gfe2_reloadable_flag_quic_batch_writer_flush_after_mtu_probe. 2020-01-30 bnc Sent PRIORITY_UPDATE frame when priority changes. 2020-01-30 wub gfe-relnote: Check handshake timeout before idle timeout in QuicConnection. Protected by --gfe2_reloadable_flag_quic_check_handshake_timeout_before_idle_timeout. Created with: roll-dep src/net/third_party/quiche/src src/third_party/quic_trace/src Change-Id: Id057ddca51b6bb8f5c219285a444023a7c08a071 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2037636 Commit-Queue: Renjie Tang <renjietang@chromium.org> Reviewed-by:
Bence Béky <bnc@chromium.org> Cr-Commit-Position: refs/heads/master@{#738756}
-
Khushal Sagar authored
Buffer allocation for the display compositor is currently done before overlay processing. This order is incorrect since we need to know whether buffers used by the compositor need to support alpha and this is not known until overlay processing. If a quad is promoted to an underlay then the display compositor buffers will need to support alpha. R=dcastagna@chromium.org,ccameron@chromium.org Bug: 946360 Change-Id: Ibb854cdb7764d4f6f6f41e490012416f9f0497ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026968 Commit-Queue: Khushal <khushalsagar@chromium.org> Reviewed-by:
ccameron <ccameron@chromium.org> Reviewed-by:
Andres Calderon Jaramillo <andrescj@chromium.org> Cr-Commit-Position: refs/heads/master@{#738755}
-
Demetrios Papadopoulos authored
This is to avoid specifying the same rewrites over and over again, during the Polymer 3 migration. Bug: 1026426 Change-Id: If866cd3e8c5be2d3a2344a20ead7cdaaae3a43ed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2040431 Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org> Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#738754}
-
Kazuhiro Inaba authored
This CL plumbs the address change event to the Web UI dialog, so that it can listen all the necessary events even after the address has changed, and take appropriate response (like automatically closing the dialog after the pairing is established.). BUG=1045310 TEST=ARC++ CTSVerifer BLE Secure Client test (see the bug for the detail) Change-Id: I023404adf561d6da2ac1148470a15b9e57b8ea1a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016775Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
Ryan Hansberry <hansberry@chromium.org> Commit-Queue: Kazuhiro Inaba <kinaba@chromium.org> Auto-Submit: Kazuhiro Inaba <kinaba@chromium.org> Cr-Commit-Position: refs/heads/master@{#738753}
-
bttk authored
https://source.chromium.org/chromium/chromium/src/+/d5c435e0b76ef29580d018cdbe8717fefd2ddd03 Bug: 1048429 Change-Id: Iaa866a5414324ba380d7d8fbc5fcc21ed1aa7ca0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2037050Reviewed-by:
Sky Malice <skym@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Commit-Queue: Yaron Friedman <yfriedman@chromium.org> Auto-Submit: bttk <bttk@chromium.org> Cr-Commit-Position: refs/heads/master@{#738752}
-
Ben Pastene authored
According to the comment in the code, disabling this test disables all benchmark smoke checks in telemetry_perf_unittest. That seems like a critical set of tests to lose coverage for. So this re-enables them. Also increases the shard count of telemetry_perf_unittest's on the chromebook tester since this increases its runtime significantly. Bug: 1041328 Change-Id: I849a04c57c8f9ac4eb687e93b85322b67cb47cfd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032325Reviewed-by:
Achuith Bhandarkar <achuith@chromium.org> Reviewed-by:
Caleb Rouleau <crouleau@chromium.org> Commit-Queue: Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#738751}
-
Michael Thiessen authored
Also adds a presubmit to ensure we don't add new java URI usage. Change-Id: I4df1b96fd737f19b8d632140d0899377ba8cc63a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002743 Commit-Queue: Michael Thiessen <mthiesse@chromium.org> Reviewed-by:
-
Kevin Marshall authored
Fixes the naming of "web_runner.cmx" and "cast_runner.cmx", which were previously being suffixed with the release channel name (e.g. "web_runner-beta.cmx"). Bug: 1049378 Change-Id: Ic60203e31e1bf694fc6696d9c948d74fa0822020 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2040386Reviewed-by:
James Robinson <jamesr@chromium.org> Commit-Queue: Kevin Marshall <kmarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#738749}
-
Christopher Cameron authored
Change gfx::DisplayColorSpaces to be a class instead of a struct, and hide its members (except to mojo serialization). Include a gfx::BufferFormat for each configuration. This will be needed - On Android to indicate that we can use 565 formats for opaque content. - On CrOS to indicate that we should use 1010102 formats for HDR - On macOS to indicate that we should use f16 formats for HDR - On Windows to indicate that we should use f16 or 1010102 for HDR This will eventually need to be plumbed through viz::OutputSurface::Reshape, gl::GLSurface::Resize, and glResizeCHROMIUM. Those function take a "has alpha" argument, the value of which will be able to be inferred from the buffer format. Bug: 1049334 Change-Id: I9bc8f2258496808de603a35cf6c0356bce5ff102 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2038077Reviewed-by:
Khushal <khushalsagar@chromium.org> Reviewed-by:
-
Connie Wan authored
See the attached bug for the related crash. I wasn't able to repro the crash, but a -1 index seems like a likely candidate. The previous code did catch it: https://chromium-review.googlesource.com/c/chromium/src/+/1999088/10/chrome/browser/ui/views/tabs/tab_strip.cc#b1081 So I added a check in here for a -1 index, to see if that fixes the issue. Bug: 1049240 Change-Id: I670ae27d0fe3899e2985575eeb395bfbb68f4cef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2040060Reviewed-by:
Taylor Bergquist <tbergquist@chromium.org> Commit-Queue: Connie Wan <connily@chromium.org> Cr-Commit-Position: refs/heads/master@{#738747}
-
Jinsuk Kim authored
This CL addresses a crash (CHECK_EQ being hit) on desktop when a RenderProcessHost instance is still alive while the associated ProfileDestroyer is on its way to destruction. This started happening after https://crrev.com/c/1971031 landed to fix other crash on Android by delaying the destruction the off-the-record profile, which would have destroyed the RPH before hitting the CHECK_EQ. This CL moves the off-the-record profile destruction task where it was but uses |DestroyOffTheRecordProfileNow| instead. This change takes care of the desktop crash but also makes sure the clean up task required for the Android issue comes before the profile destruction. Bug: 1040839 Change-Id: Iabab0a304a802d1bd64adec255e88d81b6987cde Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032385 Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org> Reviewed-by:
Mihai Sardarescu <msarda@chromium.org> Cr-Commit-Position: refs/heads/master@{#738746}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/4dc7c627..d2d1b4e4 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: Ic90962bddeca474d4f08a1533d12d2451ea0eebd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2039830Reviewed-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@{#738745}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/a0eb8359beb5..7e44d3cbb30e Created with: gclient setdep -r src-internal@7e44d3cbb30e 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:1024588,chromium:1045987,chromium:973101 Tbr: jbudorick@google.com Change-Id: Ic5e4cf0bed1dbb939c4ba5efa17cd03a4f5483c0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2040045Reviewed-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@{#738744}
-
Philip Rogers authored
These signals were for an experiment to reduce compositing under memory pressure. This project is no longer being pursued because it is not clear the benefits of the intervention are worth the cost. The design doc has more information, including the raw numbers: https://docs.google.com/document/d/1oOebUZfMbW1lxgPifANu8BfPDN9BzRxXBRbvxZxnK8Q/view Bug: 1031634 Change-Id: I3700bd6d3c85dc1d187c79d7fd2b1b5d81d8c798 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028752Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Philip Rogers <pdr@chromium.org> Auto-Submit: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#738743}
-
Rachel Wong authored
Bug: 1014839 Change-Id: Ie568d00cd2a40b104ea204b6e73e6a73f8cb5e3a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029389Reviewed-by:
Tony Yeoman <tby@chromium.org> Commit-Queue: Rachel Wong <wrong@chromium.org> Cr-Commit-Position: refs/heads/master@{#738742}
-
Sinan Sahin authored
Bug: 1048972 Change-Id: I3f06cf95efc9e96679326a41ccf29caa38f0bc9c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2039594 Commit-Queue: Sinan Sahin <sinansahin@google.com> Reviewed-by:
Matthew Jones <mdjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#738741}
-
Xiaoqian Dai authored
According to the new spec, we enforce a 96dp minimum drag distance no matter whether the drag starts within the snap region. The window has to drag either inside 16dp from the screen edge or a minimum 96dp distance into the snap region to be snapped. Bug: 1049158 Change-Id: I9102acd772f3e8ae27078998225f6efcc34f2a9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2039140 Commit-Queue: Xiaoqian Dai <xdai@chromium.org> Reviewed-by:
-
- 05 Feb, 2020 13 commits
-
-
Andrew Moylan authored
Adding config before experiment/rollout to Beta in M81. Bug: 937063 Change-Id: I6cfd07ff8e79b6dd7162344e1505ce11f2cbca63 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2037301 Auto-Submit: Andrew Moylan <amoylan@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Commit-Queue: Andrew Moylan <amoylan@chromium.org> Cr-Commit-Position: refs/heads/master@{#738739}
-
Markus Handell authored
This change fixes a problem where the WebmMuxer will produce duplicate timestamps leading to audio gaps or jerky video in WebM files, provided both audio and video is recorded, and timestamps of all incoming frames are not monotonically increasing. This resulted in the WebmMuxer rewriting apparently older frames' timestamps as the newest one encountered. With this change we now normally don't change the incoming timestamps, but always output a sorted sequence of frames to the underlying Matroska muxer. Timestamps are exceptionally changed when it's found that each stream's timestamps aren't monotonically increasing. Additionally, the webm_muxer got it's unit tests updated. Bug: 873963 Change-Id: I6b81ef32f0f7f1034a56da3bca07186221fefaea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2033253 Commit-Queue: Markus Handell <handellm@google.com> Reviewed-by:
Miguel Casas <mcasas@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#738738}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/4777e3addec4..ebc00f97fab1 git log 4777e3addec4..ebc00f97fab1 --date=short --first-parent --format='%ad %ae %s' 2020-02-05 egdaniel@google.com Revert "Change refPinnedTextureProxy to return a view instead." 2020-02-05 egdaniel@google.com Change refPinnedTextureProxy to return a view instead. 2020-02-05 herb@google.com Add a mutex to SkStrike to regulate multithreaded access 2020-02-05 fmalita@chromium.org [skottie] Add support for ADBE Pro Levels2 effect 2020-02-05 jlavrova@google.com Make assert less sensitive to rounding errors 2020-02-05 herb@google.com Remove search of desperation 2020-02-05 brianosman@google.com Add comment explaining memset in ArithmeticFPInputs 2020-02-05 westont@google.com Add ccache_linux cipd package. 2020-02-05 brianosman@google.com Ensure that ArithmeticFPInputs is fully initialized 2020-02-05 egdaniel@google.com Update bicubic effect factories to take a view. Created with: gclient setdep -r src/third_party/skia@ebc00f97fab1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC scroggo@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-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: None Tbr: scroggo@google.com Change-Id: Iad5a4bcbf83d06509d53043b179dbb5559ba0681 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2040046Reviewed-by:
-
Sammie Quon authored
First use case will be a tast-test for dragging into overview. Cros-side change: https://chromium-review.googlesource.com/c/chromiumos/platform/tast-tests/+/2036615 Test: manual Bug: 1048248 Change-Id: I5b6ad968377b318ddf5082410054141a2f0480db Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036480Reviewed-by:
Alex Newcomer <newcomer@chromium.org> Reviewed-by:
Xiaoqian Dai <xdai@chromium.org> Commit-Queue: Sammie Quon <sammiequon@chromium.org> Cr-Commit-Position: refs/heads/master@{#738736}
-
behdad authored
Main_30fps_impl_60fps story in representative perf test is marked as a control test, so that if this test fails as a result of high noise, it would invalidate the failure of other tests and would result in less false positives. Bug: chromium:1029846 Change-Id: I50c8e41108d584f2f5cbcf095be50dc09228406b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2025510 Commit-Queue: Behdad Bakhshinategh <behdadb@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Reviewed-by:
-
Ionel Popescu authored
Prior to this CL the focus ring color wasn't impacted by the system accent color. The new behavior is that if the system accent color is changed then it is going to be used as the focus ring color. Not being able to use the default system accent color as the focus ring color is a known trade-off we're taking for having a consistent default black & white focus ring across all platforms. Bug: 1022120 Change-Id: Iacd35404530e190b45e5866c7a11cf86d5001ffb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2031863 Commit-Queue: Ionel Popescu <iopopesc@microsoft.com> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Reviewed-by:
Mason Freed <masonfreed@chromium.org> Cr-Commit-Position: refs/heads/master@{#738734}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/02b17a5507ae..703a5d76d9ba git log 02b17a5507ae..703a5d76d9ba --date=short --first-parent --format='%ad %ae %s' 2020-02-05 trevor.axiom@gmail.com Reland "Reland "Reland "Implemented screen enumeration and selection for desktop capture under X11 using the X Resize and Rotate extension version 1.5.""" 2020-02-05 hta@webrtc.org Cleanup: remove unused sctp_content_name 2020-02-05 ilnik@webrtc.org Make RtpEncodingParameters to not reverse active flags order Created with: gclient setdep -r src/third_party/webrtc@703a5d76d9ba 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: chromium:396091 Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: Iea7da4ca7d1972ac01b8df38e70ea068da0dfc4f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2040043Reviewed-by:
-
Robert Flack authored
This test is failing on mac with a persistent use after free error. TBR=ellyjones@chromium.org Bug: 1049284 Change-Id: I90023aa1017a48400e5ae09aa93d07b397370acb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2040057 Commit-Queue: Robert Flack <flackr@chromium.org> Reviewed-by:
Robert Flack <flackr@chromium.org> Cr-Commit-Position: refs/heads/master@{#738732}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/8e8e1d0dd729..dd48b7e2d06e git log 8e8e1d0dd729..dd48b7e2d06e --date=short --first-parent --format='%ad %ae %s' 2020-02-05 amaiorano@google.com Fix MSAN LLVM jit false positives 2020-02-05 bclayton@google.com Disable new gcc 9 warning [init-list-lifetime] Created with: gclient setdep -r src/third_party/swiftshader@dd48b7e2d06e If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Please CC swiftshader-team+autoroll@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_chromium_msan_rel_ng;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: None Tbr: swiftshader-team+autoroll@google.com Change-Id: I4f2d15a26a92a212de405bef9c92ee6b650bb2e5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2039990Reviewed-by:
-
Lan Wei authored
We used to use a timer to send fake mouse move events when updating hover for scrolling or layout change. We changed to another way of doing it by setting a state at scroll end and layout change, and sending a fake mouse move event at the next frame to update hover. The new change has been landed for few months, now we remove the flag "UpdateHoverAtBeginFrame" and clean the code. Bug: 1016560 Change-Id: Ia4e2775f55b3b53b1bba7d3df187f11b7a226a6a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032414Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
Navid Zolghadr <nzolghadr@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Lan Wei <lanwei@chromium.org> Cr-Commit-Position: refs/heads/master@{#738730}
-
Natalie Chouinard authored
Move Developer Settings alongside other tracing code. Bug: 1047357 Change-Id: Iae70854b966607321a661d58e7680cb154c99178 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036516 Commit-Queue: Natalie Chouinard <chouinard@chromium.org> Reviewed-by:
Eric Seckler <eseckler@chromium.org> Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Cr-Commit-Position: refs/heads/master@{#738729}
-
Matt Jones authored
The BottomSheet previously attempted to check the state of find-in-page by looking up its view. Not only does this not work correctly, but there does not appear to be any poor interaction between the widget and find-in-page. This code has been removed. Bug: 1002277 Change-Id: Idd9f39605365c177c72a98d82a84407bb801c8d8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2040172Reviewed-by:
-
Tom Anderson authored
This CL adds 3 new bots: * Linux Ozone Tester (Wayland) on chromium.linux - Triggered by linux-ozone-rel - All tests have --ozone-platform=wayland * Linux Ozone Tester (X11) on chromium.linux - Triggered by linux-ozone-rel - All tests have --ozone-platform=x11 * linux-ozone-x11-and-wayland-rel - Trybot that is a combination of the above 2 bots and linux-ozone-rel - Eventually, linux-ozone-rel (trybot) will inherit this bot's config and this bot will be removed. Requires tools/build change: https://chromium-review.googlesource.com/c/chromium/src/+/1962128 BUG=1043896 R=estaab Change-Id: I4b3575526ba485f80d2fb03cfed677aa943b47b2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032518 Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:Aaron Gable <agable@chromium.org> Cr-Commit-Position: refs/heads/master@{#738727}
-
