-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iridium browser: disable smooth scroll #1
Open
spinalgr1990
wants to merge
945
commits into
iridium-browser:master
Choose a base branch
from
alexkowel:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…044.54-r1 to 81-4044.31-1583149048-benchmark-81.0.4044.55-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-afdo-airmont-chromium-beta 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: I3f933228f56275c4a5ebaaa91fc79b31f1ca2b49 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2091977 Reviewed-by: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/4044@{#696} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
…0.4044.54-r1 to 81-4044.31-1583146927-benchmark-81.0.4044.55-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-afdo-silvermont-chromium-beta 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: I964d0a7208af863c09db898596d2f85afb2b7643 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2092076 Reviewed-by: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/4044@{#697} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
Merged from https://chromium-review.googlesource.com/c/chromium/src/+/2068860 BUG=1046897 TBR=vmpstr Change-Id: I3c7039c2a5bb24d71d0cb4e5a32f1cd9455c98e5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2091719 Reviewed-by: Stefan Zager <szager@chromium.org> Reviewed-by: vmpstr <vmpstr@chromium.org> Commit-Queue: vmpstr <vmpstr@chromium.org> Commit-Queue: Stefan Zager <szager@chromium.org> Cr-Commit-Position: refs/branch-heads/4044@{#698} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
The 'chromium.tests.template' pool is identical to the 'chromium.tests' pool (same bots) but uses swarming task templates. This temporarily moves all ios tests to the new pool while I work on adding templates to the old pool. (cherry picked from commit b655119) Bug: 812428 Change-Id: I4e3cf7b94bd0e8d371bf39ab2f13d56256d27b51 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2083919 Reviewed-by: John Budorick <jbudorick@chromium.org> Reviewed-by: Justin Cohen <justincohen@chromium.org> Commit-Queue: Ben Pastene <bpastene@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#746900} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2090366 Cr-Commit-Position: refs/branch-heads/4044@{#699} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
…mode" This reverts commit b60a778. Reason for revert: we are too close to the stable cut, and the Kohaku attract loop is not ready yet. Holding out on this for Kohaku. Original change's description: > chromeos: hack to check if we are Kohaku when launching demo mode > > This is a change for M81 branch only which will support Kohaku's > custom demo mode attract loop, as demo mode Kohaku devices will never > be updated to M82. > > This is a lot cleaner in M82, but we're 30+ CLs diff from making that > solution work in M81. So just check based on SMBIOS name. > > Bug: 1050671 > Test: Kohaku shows eve demo mode > Change-Id: I3f8a47ab824dac9676c7b0ada88bc0282cde3819 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2076532 > Reviewed-by: Steven Bennetts <stevenjb@chromium.org> > Commit-Queue: Steven Bennetts <stevenjb@chromium.org> > Cr-Commit-Position: refs/branch-heads/4044@{#501} > Cr-Branched-From: a6d9daf-refs/heads/master@{#737173} TBR=stevenjb@chromium.org,jrosenth@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1050671 Change-Id: Iab21a63df98d3871c62b9d0b29f73f203e74be27 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2092129 Reviewed-by: Steven Bennetts <stevenjb@chromium.org> Commit-Queue: Steven Bennetts <stevenjb@chromium.org> Cr-Commit-Position: refs/branch-heads/4044@{#700} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
TBR=govind@chromium.org Change-Id: I4cf63ef9ec34f6df4f5a756d997771e0cffbb6df Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2093014 Reviewed-by: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/4044@{#701} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
TBR=benmason@chromium.org Change-Id: Id902de8e0ead6173dd2a63977ad8cc4562bdf7fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2091224 Commit-Queue: Krishna Govind <govind@chromium.org> Reviewed-by: Krishna Govind <govind@chromium.org> Cr-Commit-Position: refs/branch-heads/4044@{#702} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
SelectionPopupController uses ActionMode.getMenuInflater to instantiate a MenuInflater that uses an appropriately themed context. However this can never work for WebLayer, because it relies on the wrapped context as the only means of accessing its assets/resources. WebLayer cannot rely on the current implementation because reaching the fallback is dependent on the embedding application not having defined a resource with the same ID. WebView, on the other hand, must continue to use the current approach, because it injects its assets and resources into the activity context and can make use of activity themes, but in some cases may have to fall back to the WebContents context because on sokme Android versions and in some circumstances the ActionMode object has a context that has not had webview resources injected. (cherry picked from commit 1e6c60b) Bug: 1057816 Change-Id: I417bea202ffb439fcc3960c3c5e28360b16fe9d9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2083476 Reviewed-by: Bo <boliu@chromium.org> Reviewed-by: Clark DuVall <cduvall@chromium.org> Commit-Queue: Tobias Sargeant <tobiasjs@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#746341} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2093591 Reviewed-by: Tobias Sargeant <tobiasjs@chromium.org> Cr-Commit-Position: refs/branch-heads/4044@{#703} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
…4.54-r1 to 81-4044.31-1583146927-benchmark-81.0.4044.55-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-beta 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 CQ_EXTRA_TRYBOTS= TBR=c-compiler-chrome@google.com Change-Id: I3bec168dcce1cb1e850ac38809422f1d190b0f06 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2093654 Reviewed-by: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/4044@{#704} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
….4044.55-r1 to 81-4044.31-1583147710-benchmark-81.0.4044.56-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-afdo-broadwell-chromium-beta 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: I447b85d915c00742bb1f549ccf6a8959707b0d1f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2093669 Reviewed-by: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/4044@{#705} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
…044.55-r1 to 81-4044.31-1583149048-benchmark-81.0.4044.56-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-afdo-airmont-chromium-beta 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: I8587cd67fb4ab19a0ad1d3c2adee6c21cdb686f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2093772 Reviewed-by: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/4044@{#706} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
…0.4044.55-r1 to 81-4044.31-1583146927-benchmark-81.0.4044.56-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-afdo-silvermont-chromium-beta 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: Ic08a90b480bea206d31df1023dffcd7c0c4fa3f6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2093776 Reviewed-by: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/4044@{#707} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
TBR=cmasso@chromium.org Change-Id: I9b945f6816254603245d09d5cd33b49e3b4b3c34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2092897 Reviewed-by: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/4044@{#708} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
…4.55-r1 to 81-4044.31-1583146927-benchmark-81.0.4044.56-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-beta 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 CQ_EXTRA_TRYBOTS= TBR=c-compiler-chrome@google.com Change-Id: I90498d7688c4a012e8b8a2876b91f2400eaed7f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2093518 Reviewed-by: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/4044@{#709} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
…0.4044.56-r1 to 81-4044.31-1583146927-benchmark-81.0.4044.57-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-afdo-silvermont-chromium-beta 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: Id6bd60aa2979c520a54fe8b584a8e81524150755 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2093522 Reviewed-by: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/4044@{#710} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
….4044.56-r1 to 81-4044.31-1583147710-benchmark-81.0.4044.57-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-afdo-broadwell-chromium-beta 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: I738bb63a099d11daf3ef650ccd539a9ead8dd64e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2093524 Reviewed-by: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/4044@{#711} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
…044.56-r1 to 81-4044.31-1583149048-benchmark-81.0.4044.57-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-afdo-airmont-chromium-beta 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: Iff41e8b3450fe59e4cef7df25d2f7466c54ad434 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2093523 Reviewed-by: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/4044@{#712} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
TBR=mmoss@chromium.org Change-Id: Iccf240cd4f341312a85bad3c7ca2384c0dacfccb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2094458 Reviewed-by: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/4044@{#713} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
…4.56-r1 to 81-4044.31-1583146927-benchmark-81.0.4044.57-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-beta 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 CQ_EXTRA_TRYBOTS= TBR=c-compiler-chrome@google.com Change-Id: I0765c268091334fd2fe5d7c0b9f1e9efe4b90e3f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095415 Reviewed-by: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/4044@{#714} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
This version includes a fix for the crash reported in the attached bug. This change also rolled out to finch, but this will still crash if you build locally with an agsa version earlier than 10.98. (cherry picked from commit 505b4d3) Bug: 1053930 Change-Id: I57f83aa1861aba7e6bef58be5a969d13d15ac078 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2071356 Commit-Queue: Brandon Wylie <wylieb@chromium.org> Reviewed-by: Theresa <twellington@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#745279} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2094244 Commit-Queue: Theresa <twellington@chromium.org> Cr-Commit-Position: refs/branch-heads/4044@{#715} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
TBR=kariah@chromium.org Change-Id: I23068f0d9b8ac3d3c7256ffd8c0167c75f8bebb1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095459 Reviewed-by: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/4044@{#716} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
In r745013 we introduced a case where createPermissionClickCallback() can be called with both a null intentOverride and androidPermissions. This change adds the missing null check. (cherry picked from commit 8f26052) Bug: 1058746 Change-Id: I5971f20b18b193ba664ab8f24a0a03841da32b79 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2090174 Reviewed-by: Ted Choc <tedchoc@chromium.org> Commit-Queue: Reilly Grant <reillyg@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#747477} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095395 Reviewed-by: Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/branch-heads/4044@{#717} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
This CL adds a RemoteCommand field to HeartbeatResponse and make the host restart with a REMOTE_RESTART_HOST offline reason when a RESTART command is received. Some refactoring has been done to make code more readable. Bug: 1058988 Change-Id: I1dec66fd718176fb6cfe6257f86d8d2a3db1fe02 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2090876 Reviewed-by: Joe Downing <joedow@chromium.org> Commit-Queue: Joe Downing <joedow@chromium.org> Commit-Queue: Yuwei Huang <yuweih@chromium.org> Cr-Commit-Position: refs/heads/master@{#747905} (cherry picked from commit 3d0006c) TBR=joedow@chromium.org Change-Id: I1dec66fd718176fb6cfe6257f86d8d2a3db1fe02 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095081 Reviewed-by: Yuwei Huang <yuweih@chromium.org> Reviewed-by: Joe Downing <joedow@chromium.org> Commit-Queue: Yuwei Huang <yuweih@chromium.org> Cr-Commit-Position: refs/branch-heads/4044@{#718} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
This should help limit the number of crashes WebLayer gets. The module is likely to be important if we move forward with WebView and WebLayer in the same process. BUG=1057791 TEST=none TBR=sky@chromium.org (cherry picked from commit 02eaaea) Change-Id: Idf089d7f8babba761f5b28a046f79ddccaf22e62 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2088931 Reviewed-by: Tobias Sargeant <tobiasjs@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#747296} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2094249 Reviewed-by: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/branch-heads/4044@{#719} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
…0.4044.57-r1 to 81-4044.42-1583747064-benchmark-81.0.4044.58-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-afdo-silvermont-chromium-beta 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: I8214846a279bf67e4f21ce9cd20cc2104cf9ae91 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095433 Reviewed-by: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/4044@{#720} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
This reverts commit f03313b. Causes a performance regression in some web applications. BUG=1057747 Original change's description: > Remove the scratch memory in the passthrough command decoder > > The scratch buffer was only used for some queries and it was never > freed. Simply allocate the memory when doing the queries to simplify > tracking. > > BUG=1030835 > BUG=angleproject:4363 > > Change-Id: I105b8891095517d993fa88ba0998b7b8fd6742ae > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028182 > Reviewed-by: Zhenyao Mo <zmo@chromium.org> > Commit-Queue: Geoff Lang <geofflang@chromium.org> > Cr-Commit-Position: refs/heads/master@{#736663} TBR=zmo@chromium.org,geofflang@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1030835, angleproject:4363 Change-Id: I955ff25c40b433f1592e7786045623945c550270 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2091225 Reviewed-by: Geoff Lang <geofflang@chromium.org> Commit-Queue: Geoff Lang <geofflang@chromium.org> Cr-Commit-Position: refs/branch-heads/4044@{#721} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
…044.57-r1 to 81-4044.31-1583751957-benchmark-81.0.4044.58-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-afdo-airmont-chromium-beta 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: I1b68377ce1b2e37fcf9fccff82de1f31a5b913c3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095657 Reviewed-by: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/4044@{#722} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
….4044.57-r1 to 81-4044.31-1583747900-benchmark-81.0.4044.58-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-afdo-broadwell-chromium-beta 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: Ief429b05b44a3418ad8f90a3c7cc0dde2201b378 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095656 Reviewed-by: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/4044@{#723} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
> A display transform pass could be added during capturing when > devices are not in their default orientation. Making the display > transform pass to copy |has_transparent_background| flag from > root renderer pass fixed the problem on Dru. Without the flag > copied, Dru (ARM/Mali) somehow shows the display transform pass > as a black frame and causes the flicker. > > Bug: 1041901 > Change-Id: I9651073cf8f9ab75ae5aaf6bfcd20a25fd4349d0 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2089957 > Commit-Queue: Xiyuan Xia <xiyuan@chromium.org> > Reviewed-by: Khushal <khushalsagar@chromium.org> > Cr-Commit-Position: refs/heads/master@{#747465} (cherry picked from commit b5764c1) Bug: 1041901 Change-Id: Iba071bdaa38f1498d5a9619b49281d22e1b0bf4d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095556 Reviewed-by: Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/branch-heads/4044@{#724} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
This reverts commit 9267226. Reason for revert: https://crbug.com/1045381, https://crbug.com/1057810 TBR=dalecurtis@chromium.org Original change's description: > Merge to M81: WebmMuxer: Do not produce duplicate timestamps. > > 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. > > TBR=mcasas@chromium.org > > (cherry picked from commit 4234d1e) > > 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-Original-Commit-Position: refs/heads/master@{#738738} > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2050369 > Reviewed-by: Markus Handell <handellm@google.com> > Cr-Commit-Position: refs/branch-heads/4044@{#197} > Cr-Branched-From: a6d9daf-refs/heads/master@{#737173} TBR=handellm@google.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 873963 Change-Id: I74f0761c7231052c7f6c222b1f91f7ea6df06088 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2093601 Commit-Queue: Markus Handell <handellm@google.com> Reviewed-by: Markus Handell <handellm@google.com> Cr-Commit-Position: refs/branch-heads/4044@{#725} Cr-Branched-From: a6d9daf-refs/heads/master@{#737173}
Smooth scrolling (while using mousewheel or arrow keys) is a really dumb idea. Text naturally appears as a blur while it moves, and the animation takes that-many milliseconds to finish, so it's a time waster too. Only the fallback setting, which is used on Linux, is changed; on Windows/MacOS, smooth scrolling remains controlled by a system setting.
Why are you wasting time on this when your installation instructions don't even work? |
jengelh
force-pushed
the
master
branch
4 times, most recently
from
March 31, 2022 23:22
419e013
to
38edd99
Compare
yes, they do. But if you want to build it, here are some instructions that he missed out on.
|
jengelh
force-pushed
the
master
branch
3 times, most recently
from
December 4, 2022 11:42
b7ac543
to
ebb8862
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
How to disable smooth scrolling ? I cannot find that option in //flags