c380e97ee6
DesktopAndCursorComposer already handles a null MouseCursorMonitor. This CL allows that code-path to be utilized by callers that already have a MouseCursorMonitor, allowing its callbacks to be re-used by this class. This is more efficient, and works around an apparent X Server deadlock on Linux if multiple MouseCursorMonitors are simultaneously active. The intended use-case for this is to allow the host-side cursor to be composited into the desktop image if mouse-lock is active at the client. Bug: chromium:1043325 Change-Id: I7e036850dd8c17fe55e57db252392062a847d10f Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/166581 Reviewed-by: Sergey Ulanov <sergeyu@chromium.org> Commit-Queue: Jamie Walch <jamiewalch@chromium.org> Cr-Commit-Position: refs/heads/master@{#30312}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
Development
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc
- Coding style guide
- Code of conduct