The W3C has published a Working Draft of the clipboard API that supports common clipboard operations including cutting, copying and pasting in your Web applications.
According to the draft document, the specification also makes it possible that the clipboard actions
‘can be adapted to provide advanced functionalities’,
The road to getting a standard clipboard API has been long and difficult, partly because of the very different techniques supported by the different browsers. Even as late as the major draft in 2011, Firefox needed a configuration change before opening up the clipboard to JavaScript, while Opera needed an add-on, and the Chrome extension was still "experimental".
The current situation has improved, but support is still far from ideal as revealed in this table:
In summary, IE, Chrome, Safari and Opera offer partial support, Firefox offers full support, and other browsers offer some or no support.
The website says that partial support in IE refers using a non-standard method of interacting with the clipboard, while for other browsers it refers to not supporting the ClipboardEvent constructor.
The clipboard API lets you access the clipboard using the setData, getData and clearData methods that are defined in HTML5’s DataTransfer interface. The new draft also adds beforecopy, beforecut, and beforepaste events that let you carry out actions such as setting up what state user interface controls should be in before the user can initiate a copy or cut.
The fact that even the Clipboard API is still being argued about and the patchy implementation gives you a clear idea of what is still wrong with HTML5 approaches to building apps. There are still too many missing features.
According to a report that originated with CNBC and has been widely circulated, Intel completely eliminated the group concerned with wearables earlier this month.
