Skip to content
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

[pull] main from chromium:main #126

Merged
merged 6 commits into from
Dec 17, 2021
Merged

[pull] main from chromium:main #126

merged 6 commits into from
Dec 17, 2021

Conversation

pull[bot]
Copy link

@pull pull bot commented Dec 17, 2021

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

kmoon-work and others added 6 commits December 17, 2021 04:13
Fixes a variety of input-handling bugs discovered by a careful audit of
input event handlers in the PDF viewer:

1. Adds support for relaying input events to Print Preview.
2. Relays the Escape and Tab keys, which are used by Print Preview.
3. Relays additional directional keys: ArrowDown/Up, PageDown/Up.
4. Don't prevent modified arrow keys (used for browser navigation).

This change also distinguishes more carefully between keyboard events
sent through the scripting API, and those sent from the plugin frame,
although the scripting API support apparently is unused
(crbug.com/1279958).

More fixes will be required for presentation mode (crbug.com/1280760).

Fixed: 1279550
Change-Id: Ied3dcdbc77fe73ec66bc4188ecd6731c1c707b9d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3345973
Reviewed-by: Daniel Hosseinian <dhoss@chromium.org>
Commit-Queue: K. Moon <kmoon@chromium.org>
Cr-Commit-Position: refs/heads/main@{#952652}
Bug: 1262373
Change-Id: I0166b9a367d20130470bed9314c75dabbcce66f6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3346103
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Commit-Queue: Mohamad Ahmadi <mahmadi@chromium.org>
Cr-Commit-Position: refs/heads/main@{#952653}
Move mojoms are that are used internally by Ozone platform code from
//ui/ozone/public/mojom target into a new mojom target inside the Ozone
platform folder.

//ui/ozone/platform/scenic/mojom is also used by code in
//ui/ozone/platform/flatland but this is a temporary arrangement.
Eventually there will only be a single Fuchsia Ozone backend.

Bug: 1280386
Change-Id: Ief33d3cddb58c36b928804b0ba6d76126fa1fb86
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3342670
Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Commit-Queue: Kyle Charbonneau <kylechar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#952654}
Added integration testing for Realtime reporting connector in CELab.

Design doc: go/chrome-realtime-event-reporting-integration-testing

Bug: 1279865
Change-Id: I016b8d22ca68696fce4ca9929b7c1edaf7a6541f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3318507
Reviewed-by: Owen Min <zmin@chromium.org>
Commit-Queue: Eswaran Krishnamoorthy <eswarank@google.com>
Cr-Commit-Position: refs/heads/main@{#952655}
https://chromium.googlesource.com/catapult.git/+log/22e558b5843a..a25500bfae56

2021-12-17 fdegans@google.com [code-health] Migrate catapult_build to Python 3

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/catapult-autoroll
Please CC wenbinzhang@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/entry

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/main/autoroll/README.md

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:chromeos-kevin-rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Bug: chromium:1262293
Tbr: wenbinzhang@google.com
Change-Id: I43ae1595a7bf5a2293cff8301431b6208941407a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3346487
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#952656}
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/c2192b8adaae..5d9dcc48106b

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 yoichio@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/main/autoroll/README.md

Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome
Bug: None
Tbr: yoichio@google.com
Change-Id: I056ec495357dfb8f1c5a977a5084218a7024ac34
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3346501
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Bot-Commit: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#952657}
@pull pull bot added the ⤵️ pull label Dec 17, 2021
@pull pull bot merged commit 14ca75d into FairyWorld:main Dec 17, 2021
pull bot pushed a commit that referenced this pull request Jul 20, 2022
…ommits)

https://chromium.googlesource.com/external/github.com/freetype/freetype2-testing.git/+log/fe2eddae6176..1ca0c99d25ae

$ git log fe2eddae6..1ca0c99d2 --date=short --no-merges --format='%ad %ae %s'
2022-05-23 drott Track VisitedSet at top level before colrv1_start_glyph (#127)
2022-01-11 bungeman Unquote cc and cxx when executing. (#126)
2022-01-09 bungeman Quote more strings. (#125)
2022-01-09 bungeman Build bzip2 correctly. (#124)
2022-01-06 bungeman Use CC and CXX, check for clang version. (#123)
2022-01-06 bungeman Allow ubsan with asan or by itself. (#122)
2021-12-29 bungeman Remove CMAKE_x_COMPILER from libcxx build. (#119)
2021-12-24 bungeman Drop support for git <= 2.14. (#112)
2021-12-24 bungeman Make --rebuild work correctly again. (#111)
2021-12-24 bungeman Use sanitize-coverage=0 not no-sanitize-coverage (#115)
2021-12-24 bungeman Choose exactly one of the exclusive fuzzers (#117)
2021-12-24 bungeman Add missing quotes to libcxx.sh (#116)
2021-12-18 bungeman Add trace-pc-guard to no-sanitize-coverage. (#114)
2021-12-16 bungeman Add llvm-project for MemorySanitizer build. (#113)
2021-12-10 bungeman Add MemorySanitizer build option. (#110)
2021-11-09 drott Update corpus files for COLRv1 again (#109)
2021-11-01 drott Update corpus files for COLRv1 (#108)

Created with:
  roll-dep src/third_party/freetype-testing/src

Change-Id: I358febbaa1933d6d56ad655f62702d67e4a6c0c7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3777978
Commit-Queue: Ben Wagner <bungeman@chromium.org>
Reviewed-by: Florin Malita <fmalita@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1026318}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant