Re: [w3c/clipboard-apis] Make async clipboard APIs (read/write) to sanitize interoperably with setData/getData for text/html (#150)

> > Converting CSS rules to inline style is important so that the pasted content won't adversely affect the rest of the document.
> 
> Some native applications and sites like Excel online have a restriction on the HTML payload size, and inlining the styles also bloats the HTML. Maybe copying/pasting small fragments aren't an issue, but if we want to support sites that require high fidelity HTML content (with custom styles etc) inlining may not be ideal. Moreover, there are custom styles being used by sites that get stripped out during this inlining process that breaks functionality. e.g. Custom list styles are written to the clipboard by Word Online to preserve Word specific list semantics.

Sure. This is a trade off between that and user privacy and we chose to value user's privacy more than those concerns. This is precisely why I don't think we should be standardizing the same behavior across browsers.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/clipboard-apis/issues/150#issuecomment-973312161