commit | 04aebf0ae47f89d92ecf8fb7021d6479c19497d4 | [log] [tgz] |
---|---|---|
author | Rohan Raja <roraja@microsoft.com> | Thu Mar 27 05:46:15 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Mar 27 05:46:15 2025 |
tree | 601379e30766754eda22b24a8e0bd73c8868318e | |
parent | c561427036726671258160772f987d136a786156 [diff] |
[ClipboardChange event] - Extend ClipboardMonitor, adds Windows listener Changes: https://imgur.com/a/clipboardchange-event-cl-1-teFSu1N 1. Extends ClipboardMonitor to be able to notify classes generating the events (Clipboard implementations in all OS) to start/stop listening to clipboard especially in case listening to clipboard is not trivial like on MacOS. 2. In ClipboardWin, listen to clipboard changes using OS APIs. On clipboard change detected from platform, notify clipboardmonitor. 3. Added unit test which is an interactive_ui_test i.e. it creates an actual window on which it listens to clipboardchange using OS API. The test validates if the ClipboardMonitor is being notified about the clipboard changes coming from platform. Please refer to below design doc for a class level diagram. Design doc: https://docs.google.com/document/d/1bY2pzV6PSX56fiFcrXEgOjpFen07xaxmnsM5dqXFE1U/edit?tab=t.0 Complete clipboardchange event API implementation for reference: https://chromium-review.googlesource.com/c/chromium/src/+/6328739 Bug: 41442253 Change-Id: I3b2210f73bd661e3ff31890a339f9c8afac8192e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6329858 Reviewed-by: Dan Clark <daniec@microsoft.com> Reviewed-by: Sambamurthy Bandaru <sambamurthy.bandaru@microsoft.com> Commit-Queue: Sambamurthy Bandaru <sambamurthy.bandaru@microsoft.com> Cr-Commit-Position: refs/heads/main@{#1438579}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.