The platform provides a system clipboard. The term editable context means any element that is either an editing host, a textarea element, or an input element with its typeĪttribute set to any of "text", "search", "tel", To occur in the underlying browser to ensure that the clipboard content is setĬorrectly (with any metadata added by the browser during copy). While the reader can display content andĪllow the user to interact with it, actions like clipboard copy need To be able to trigger clipboard actions in the user agent.Īs an example, consider a screen reader application that provides a more accessible Trigger Clipboard ActionsĪpplications that provide an alternate interface to a user agent sometimes need Whenever it is updated, and then send the new clipboard data to the remote device. Listen for clipboardchange events, read() from the clipboard To copy the local clipboard data to a remote device, a web application would One important aspect of this use case is that it requires access to theĬlipboard in the absense of a user gesture or interaction. To be kept in sync between the two devices. Or remote shell applications), there is often a need for the clipboard data The XML source could also be placed in theĬlipboard with the appropriate transformation occurring at paste time.įor web applications that communicate with remote devices (e.g., remote access MathML often needs to be transformed to be copied as plain text, forĮxample to make sure "to the power of" is shown with the caret "^" sign It into another application generally leads to most of the semantics being
Mathematical information With content such as mathematics, simply copying rendered text and pasting. Mechanism that allows for copying more than just the rendered content. Text, or of graphic content such as, it is useful to provide a Graphics with built-in semantics In order to make web applications which allow the manipulation of rich. It is often useful to be able to reformat the content to preserve Rich content editing When copying text which contains hyperlinks or other structure,. Metadata When copying text from a repository of documents, it can be useful for theĬopied text to include metadata about the source of the copied content. There are many scenarios where it is desireable to change the default clipboard Since this is considered to be a powerful feature,Īccess to this API is controlled by a permission. Operations of cutting, copying and pasting so that web application canĪsync Clipboard API - This API provides direct access to read and write theĬlipboard data. There are two general APIs described in this specification:Ĭlipboard Event API - This API provides a way to hook into the common clipboard This specification defines how the system clipboard is exposed to web applications. 11.2.1 Privacy and Clipboard Permission. 11.2 Privacy and the Asychronous Clipboard API. 
11.1 Privacy and the Clipboard Event API. 5.3.5 Event listeners that modify selection or focus. 5.3.3 Integration with rich text editing APIs. 5.3.2 Event handlers that are allowed to read from clipboard. 5.3.1 Event handlers that are allowed to modify the clipboard. 5.3 Integration with other scripts and events. 2.1 Changing Default Clipboard Operations. This document is governed by the 15 September 2020 W3C Process Document. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group that page also includes instructions for disclosing a patent. This document was produced by a group operating under the W3C Patent Policy. It is inappropriate to cite this document as other than work in progress. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. Publication as a Working Draft does not imply endorsement by the W3C Membership. Please use GitHub issues Historical discussions can be found in the archives. This document was published by the Web Applications Working Group as a Working Draft.įeedback and comments on this specification are welcome. This document is intended to become a W3C Recommendation.Ĭhanges to this document may be tracked at. This document was published by the Web Applications Working Group as a Working Draft. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at. Other documents may supersede this document. This section describes the status of this document at the time of its publication.
0 kommentar(er)
