This is a first set of patches, which implement clipboard
support for the Ozone platforms.
The flow is asynchronous and based on Requests. That is,
whenever a ClipboardOzone receives a Read/Write/GetMime
call, it forwards it to the AsyncClipboardOzone, which
then creates a request (used for internal usage and holding
data filled by the ClipboardDelegate), calls to the delegate
and start an abort timer to make sure the request is not stalled.
What is more the clipboard data is cached and removed only when another
chunk of data iss written to a system clipboard. And whenever the chromium browser is the
selection owner, the cached data is used.
jkim-julie
commented
5 years ago
This is a first set of patches, which implement clipboard support for the Ozone platforms.
The flow is asynchronous and based on Requests. That is, whenever a ClipboardOzone receives a Read/Write/GetMime call, it forwards it to the AsyncClipboardOzone, which then creates a request (used for internal usage and holding data filled by the ClipboardDelegate), calls to the delegate and start an abort timer to make sure the request is not stalled.
What is more the clipboard data is cached and removed only when another chunk of data iss written to a system clipboard. And whenever the chromium browser is the selection owner, the cached data is used.