Re: [w3c/editing] [Delayed Clipboard Rendering] Privacy issue while reading data for web custom types (Issue #439)

Regarding the separate worklet: the issue here is that Excel keeps the data/model/business logic to process the data solely on the server. The "COGS" is _server_ CPU cycles plus bandwidth to send the data to the user's device (several pre-serialized copies, even). @snianu can correct me if I'm misunderstanding/misrepresenting this.

It's not clear to me how many sites use this architecture so I agree that it's important to gather more feedback from a broader range of potential clients of this API, as @smaug---- suggests.

Adobe did [weigh in](https://github.com/w3c/editing/issues/417#issuecomment-1464355663) but it seems that the details, such as limiting delayed rendering to built-in formats, limiting to 5 custom formats, a worklet, etc, may affect whether the API is still considered useful for Photoshop.

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

Message ID: <w3c/editing/issues/439/1852608890@github.com>