Re: [EXTERNAL] Re: [blink-dev] Web-Facing Change PSA: Write `image/svg+xml` content in UTF-8 format on Windows.

pboard spec, since it seems to be needed for programs to be interoperable? Thanks, Jeffrey On Wed, Jun 12, 2024 at 11:43 AM 'Anupam Snigdha' via blink-dev mailto:blink-dev@chromium.org>> wrote: Contact emails sni...@microsoft.com<mailto:sni...@microsoft.com> sa...@microso

Re: [EXTERNAL] Re: [blink-dev] Web-Facing Change PSA: Write `image/svg+xml` content in UTF-8 format on Windows.

ms to be interoperable? Thanks, Jeffrey On Wed, Jun 12, 2024 at 11:43 AM 'Anupam Snigdha' via blink-dev mailto:blink-dev@chromium.org>> wrote: Contact emails sni...@microsoft.com<mailto:sni...@microsoft.com> sa...@microsoft.com<mailto:sa...@microsoft.com> Specification h

[blink-dev] Web-Facing Change PSA: Write `image/svg+xml` content in UTF-8 format on Windows.

Contact emails sni...@microsoft.com sa...@microsoft.com Specification https://w3c.github.io/clipboard-apis/#optional-data-types-x Design docs None. See summary. Summary On Windows, popular native apps [1] use UTF-8 format to read/write SVG

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Clipboard API: Svg

romium.org<mailto:etiennen...@chromium.org> mailto:etiennen...@chromium.org>>; Sanket Joshi (EDGE) mailto:sa...@microsoft.com>> Subject: Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Clipboard API: Svg On Fri, Feb 23, 2024 at 7:40 PM Daniel Bratell mailto:bratel..

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Clipboard API: Svg

t;mailto:etiennen...@chromium.org> mailto:etiennen...@chromium.org>>; Sanket Joshi (EDGE) mailto:sa...@microsoft.com>> Subject: Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Clipboard API: Svg On Fri, Feb 23, 2024 at 7:40 PM Daniel Bratell mailto:bratel...@gmail.com>> wrot

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Clipboard API: Svg

@gmail.com>> wrote: LGTM Not sure if it's LGTM2 or LGTM4 since that depends on if the 2021 LGTMS still apply, but this still seems ready to ship. /Daniel On 2024-02-23 19:14, Chris Harrelson wrote: My LGTM still stands, and have recorded it in the tool. On Fri, Feb 23, 2024 at 10:01

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Clipboard API: Svg

this still seems ready to ship. /Daniel On 2024-02-23 19:14, Chris Harrelson wrote: My LGTM still stands, and have recorded it in the tool. On Fri, Feb 23, 2024 at 10:01 AM 'Anupam Snigdha' via blink-dev mailto:blink-dev@chromium.org>> wrote: Gentle p

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Clipboard API: Svg

Gentle ping.. Received signoffs for all review gates for this feature. From: Anupam Snigdha Sent: Monday, February 12, 2024 10:37 AM To: Thomas Steiner ; Chris Harrelson Cc: Evan Stade ; Anupam Snigdha ; 一丝 ; blink-dev ; sligh...@chromium.org ; svo...@gmail.com

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Clipboard API: Svg

I've made some changes to address the loss of styles and other formatting issues during write. During read, if the authors have added `image/svg+xml` to the `un

[blink-dev] Intent to Prototype: Delayed clipboard rendering

Contact emails ansol...@microsoft.com, sni...@microsoft.com, sa...@microsoft.com Explainer https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/DelayedClipboard/DelayedClipboardRenderingExplainer.md S

[blink-dev] Re: Web-Facing Change PSA: Do not delete File kind objects in dataTransfer.clearData()

Making few edits in TAG review and status of Webkit. This change has already shipped in both Firefox and Safari. From: Anupam Snigdha Sent: Monday, January 8, 2024 1:54 PM To: blink-dev@chromium.org Cc: Sanket Joshi (EDGE) ; Palak Bhatia Subject: Web-Facing Cha

[blink-dev] Web-Facing Change PSA: Do not delete File kind objects in dataTransfer.clearData()

Contact emails sni...@microsoft.com, sa...@microsoft.com, est...@chromium.org, palakbha...@microsoft.com Specification https://html.spec.whatwg.org/multipage/dnd.html#dom-datat

Re: [EXTERNAL] Re: [blink-dev] Web-Facing Change PSA: Async Clipboard API: Write well-formed HTML document.

Change PSA: Async Clipboard API: Write well-formed HTML document. You don't often get email from vmp...@google.com. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> On Mon, Dec 11, 2023 at 6:05 PM 'Anupam Snigdha' via blink-dev mailto:blink-de

Re: [EXTERNAL] Re: [blink-dev] Re: Web-Facing Change PSA: Async Clipboard API: Write well-formed HTML document.

we work on a migration story? Thanks, Rick On Mon, Dec 11, 2023 at 5:47 PM 'Anupam Snigdha' via blink-dev mailto:blink-dev@chromium.org>> wrote: Fixing typos and formats. From: Anupam Snigdha Sent: Monday, December 11, 2023 2:42 PM To: b

[blink-dev] Web-Facing Change PSA: Async Clipboard API: Write well-formed HTML document.

Contact emails sni...@microsoft.com, sa...@microsoft.com, est...@chromium.org Specification https://w3c.github.io/clipboard-apis/#dom-clipboard-write Design docs https://docs.google.com/document/d/1rTEg2I-hMPXGiLrEMqKJz2Ycu6GRjlM3uvakOe84m8Q/edit?usp=sharing Summary The Async clipboard writ

[blink-dev] Re: Web-Facing Change PSA: Async Clipboard API: Write well-formed HTML document.

Fixing typos and formats. From: Anupam Snigdha Sent: Monday, December 11, 2023 2:42 PM To: blink-dev@chromium.org Cc: Sanket Joshi (EDGE) ; Evan Stade ; Ana Sollano Kim Subject: Web-Facing Change PSA: Async Clipboard API: Write well-formed HTML document. Conta

[blink-dev] Web-Facing Change PSA: Async Clipboard API: Write well-formed HTML document.

Contact emails sni...@microsoft.com, sa...@microsoft.com, est...@chromium.org Specification https://w3c.github.io/clipboard-apis/#dom-clipboard-write Design docs https://docs.google.com/document/d/1rTEg2I-hMPXGiLrEMqKJz2Ycu6GRjlM3uvakOe84m8Q/edit?usp=sharing Summary The Async clipboard writ

[blink-dev] Intent to Ship: Async Clipboard API: Read unsanitized HTML format

Resending the I2S with all the updates and a summary of discussion that happened in a different I2S thread. Contact emails sni...@microsoft.com, sa...@microsoft.com, est...@chromium.org, j

[blink-dev] Intent to Implement and Ship: Async Clipboard API: Allow empty ClipboardItem during read

Contact emails sni...@microsoft.com, est...@chromium.org, sa...@microsoft.com, jsb...@google.com Explainer https://docs.google.com/document/d/1OLVOESy3zecxY_6jMKdKVxeIGS2Q6mDmzc85rUNrRIE/edit?usp=sharing Specification https://w3c.github.io/clipboard-apis/#dom-clipboard-read Design docs https

Re: [EXTERNAL] Re: [blink-dev] Intent to Implement and Ship: Feature detection for supported clipboard formats

s approved by the editing WG, but we also need wider TAG review for features, and WebKit and Gecko would like to see signals requests go through their official process. On Tue, Sep 19, 2023 at 9:25 AM 'Anupam Snigdha' via blink-dev mailto:blink-dev@chromium.org>> wrote: Why

[blink-dev] Re: [EXTERNAL] Re: Intent to Ship: Async Clipboard API: Read unsanitized HTML and write well-formed HTML format.

We decided to split the proposal into two separate changes as read involves a change in the web API, but write doesn't. So, we're going to ship the unsanitized read first, before we ship the changes in behavior for the write method. I'll edit the Chrome status entry to reflect this change. Thank

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Async Clipboard API: Read unsanitized HTML and write well-formed HTML format.

The code expects `text/html` at the first position of the array, but the explainer says "If text/html representation is present in the ClipboardItem and text/html is present in the unsanitized list", which suggests any position would be fine. Maybe make the explainer say what the code says or vi

Re: [EXTERNAL] Re: [blink-dev] Intent to Ship: Async Clipboard API: Read unsanitized HTML and write well-formed HTML format.

Any answer on the other question regarding what the expected outcome of a call like below would be? Currently we're throwing a JS exception

[blink-dev] Intent to Ship: Async Clipboard API: Read unsanitized HTML and write well-formed HTML format.

The I2S thread was incorrectly merged into another I2S that I sent for a completely different feature. I'm creating a new thread and merging replies. Sorry for the inconvenience. As the author of the web custom formats article

Re: [EXTERNAL] Re: [blink-dev] Intent to Implement and Ship: Feature detection for supported clipboard formats

editing WG, but we also need wider TAG review for features, and WebKit and Gecko would like to see signals requests go through their official process. On Tue, Sep 19, 2023 at 9:25 AM 'Anupam Snigdha' via blink-dev mailto:blink-dev@chromium.org>> wrote: Why is it not applicable? Not

[blink-dev] Re: Intent to Ship: Async Clipboard API: Read unsanitized HTML and write well-formed HTML format.

(edited the subject line) From: Anupam Snigdha Sent: Thursday, October 5, 2023 4:22 PM To: blink-dev@chromium.org Cc: Sanket Joshi (EDGE) ; Evan Stade ; jsb...@google.com ; Ana Sollano Kim Subject: Intent to Implement and Ship: Async Clipboard API: Read unsani

[blink-dev] Intent to Implement and Ship: Async Clipboard API: Read unsanitized HTML and write well-formed HTML format.

Contact emails sni...@microsoft.com, sa...@microsoft.com, est...@chromium.org, jsb...@chromium.org, asu...@chromium.org, ansol...@microsoft.com

Re: [EXTERNAL] Re: [blink-dev] Intent to Implement and Ship: Feature detection for supported clipboard formats

ocess. On Tue, Sep 19, 2023 at 9:25 AM 'Anupam Snigdha' via blink-dev mailto:blink-dev@chromium.org>> wrote: Why is it not applicable? Note that this API is already in the clipboard spec and was approved by the EditingWG members<https://github.com/w3c/clipboard-apis/issues/170

Re: [EXTERNAL] Re: [blink-dev] Intent to Implement and Ship: Feature detection for supported clipboard formats

fication> Interesting problem, never thought about this ergonomic problem. On Sep 19, 2023, at 2:12, 'Anupam Snigdha' via blink-dev wrote:  Contact emails sni...@microsoft.com<mailto:sni...@microsoft.com>, sa...@microsoft.com<mailto:sa...@microsoft.com>,

[blink-dev] Intent to Implement and Ship: Feature detection for supported clipboard formats

Contact emails sni...@microsoft.com, sa...@microsoft.com, est...@chromium.org, jsb...@chromium.org, asu...@chromium.org Explainer https://github.com/w3c/

RE: [EXTERNAL] Re: [blink-dev] Intent to prototype: Align async API read/write HTML format with DataTransfer API

The unsanitized option being proposed here is only for the well-known HTML format. It could be extended to other well-known formats, but for now we are focusing on the HTML format. Web custom format is unsanitized by design, so this option doesn’t affect the existing web custom formats. From: T

RE: [EXTERNAL] Re: [blink-dev] Intent to prototype: Align async API read/write HTML format with DataTransfer API

Just to clarify some of the points in the explainer. This proposal introduces an `unsanitized` option only in the navigator.clipboard.read() method. For write() we will always write unsanitized HTML content to the clipboard. This will align the behavior of async APIs with the DataTransfer APIs a

RE: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Pickling for Async Clipboard API

edt mailto:foo...@chromium.org>>; Daniel Bratell mailto:bratel...@gmail.com>>; Yoav Weiss mailto:yoavwe...@chromium.org>>; blink-dev mailto:blink-dev@chromium.org>>; Alex Russell mailto:slightly...@chromium.org>>; Abhishek Rathi mailto:rath...@gmail.com>>; s

RE: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Pickling for Async Clipboard API

; mailto:svoi...@gmail.com>>; ajayra...@google.com<mailto:ajayra...@google.com> mailto:ajayrahate...@google.com>>; Bo Cupp mailto:pc...@microsoft.com>>; m...@google.com<mailto:m...@google.com> mailto:m...@google.com>>; Joshua Bell mailto:jsb...@chromium.org>

RE: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Pickling for Async Clipboard API

mailto:ajayrahate...@google.com>>; Bo Cupp mailto:pc...@microsoft.com>>; m...@google.com<mailto:m...@google.com> mailto:m...@google.com>>; Joshua Bell mailto:jsb...@chromium.org>>; Victor Costan mailto:pwn...@chromium.org>>; Scott Low mailto:sc...@micros

RE: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Pickling for Async Clipboard API

eiss ; blink-dev ; Alex Russell ; Abhishek Rathi ; svo...@gmail.com ; ajayra...@google.com ; Bo Cupp ; m...@google.com ; Joshua Bell ; Victor Costan ; Scott Low Subject: Re: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Pickling for Async Clipboard API On Wed, Jan 5, 2022 at 9:01 PM '

RE: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Pickling for Async Clipboard API

chromium.org>>; Victor Costan mailto:pwn...@chromium.org>>; Scott Low mailto:sc...@microsoft.com>> Subject: Re: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Pickling for Async Clipboard API Hi Anupam, Happy new year. When you say "article" in WICG or EditingW

RE: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Pickling for Async Clipboard API

oard API Hi Anupam, Happy new year. When you say "article" in WICG or EditingWG do you mean spec? If so, that sounds fine. On Fri, Dec 17, 2021 at 1:21 PM 'Anupam Snigdha' via blink-dev mailto:blink-dev@chromium.org>> wrote: Hi Philip, Yes, https://github.com/w3c

Re: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Pickling for Async Clipboard API

ship things while spec PRs are open sometimes, when there's no expectation that the PR can be merged, I think we need to find an alternative place for it. Best regards, Philip On Wed, Dec 15, 2021 at 7:02 PM 'Anupam Snigdha' via blink-dev mailto:blink-dev@chromium.org>> wrote:

RE: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Pickling for Async Clipboard API

Re origin trial: We did discuss about origin trials, but we are not anticipating any changes to the web API. Note that `unsanitized` option is a member of `ClipboardItemOptions` dictionary and we are not changing the shape of the existing read/write methods. Also, since this feature would benefi

[blink-dev] RE: [EXTERNAL] Re: Intent to Ship: Pickling for Async Clipboard API

Hi Yoav, That comment is specifically for adding the `unsanitized` option to the clipboard API spec to which Apple opposed as they don't want to support(at least currently) reading/writing custom format or unsanitized well-known format if it's not within the same origin. That means, exchanging

RE: [EXTERNAL] Re: [blink-dev] Intent to Ship: Pickling for Async Clipboard API

writing both text/plain and custom payload, and what then happens if pasting that with and without opting into the custom format. Can these tests be made more elaborate? Best regards, Philip On Thu, Nov 18, 2021 at 10:30 PM 'Anupam Snigdha' via blink-dev mailto:blink-dev@chromium.org>> w

[blink-dev] Intent to Ship: Pickling for Async Clipboard API

Contact emails sni...@microsoft.com, m...@chromium.org, pc...@microsoft.com Explainer https://github.com/w3c/editing/blob/gh-pages/docs/clipboard-pickling/explainer.md#pickling-for-async-clipboard-api Specificati

RE: [EXTERNAL] Re: [blink-dev] Intent to Implement and Ship: Add support for Promise to Blobs in clipboard item

1db47%7C1%7C0%7C637710865544845110%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=2yOeLmCZZ5MVbKbev0Ic4HGmkpFzIRpOLFRNGMfsRE0%3D&reserved=0> suggests that read operations return "a copy of the system clipboard data", w

Re: [blink-dev] RE: [EXTERNAL] Re: Intent to Implement and Ship: Feature policy for Keyboard API

upport this kind of improvement to the platform, not only for this case but in general whenever we introduce ergonomic permissions policy-based delegation for any feature. On Fri, Oct 15, 2021 at 6:00 PM 'Anupam Snigdha' via blink-dev wrote: getLayoutMap() can already be accessed

Re: [EXTERNAL] Re: [blink-dev] Intent to Implement and Ship: Add support for Promise to Blobs in clipboard item

y'all help me understand what our model is here? And what the model ought to be, if it diverges from what we've currently implemented? -mike On Wed, Oct 27, 2021 at 8:07 PM 'Anupam Snigdha' via blink-dev mailto:blink-dev@chromium.org>> wrote: Thanks Daniel for rais

RE: [blink-dev] RE: [EXTERNAL] Re: Intent to Implement and Ship: Feature policy for Keyboard API

is on the renderer side, so a compromised renderer can request the keyboard map. dave. On Wed, Oct 27, 2021 at 4:53 PM 'Anupam Snigdha' via blink-dev mailto:blink-dev@chromium.org>> wrote: Created an issue to get feedback from TAG: https://github.com/w3ctag/design-review

RE: [blink-dev] RE: [EXTERNAL] Re: Intent to Implement and Ship: Feature policy for Keyboard API

o the platform, not only for this case but in general whenever we introduce ergonomic permissions policy-based delegation for any feature. On Fri, Oct 15, 2021 at 6:00 PM 'Anupam Snigdha' via blink-dev mailto:blink-dev@chromium.org>> wrote: getLayoutMap() can already be accessed

RE: [EXTERNAL] Re: [blink-dev] Intent to Implement and Ship: Add support for Promise to Blobs in clipboard item

Thanks Daniel for raising this concern. I have opened an issue to discuss with the Editing WG: https://github.com/w3c/clipboard-apis/issues/161. In the current implementation, I think verifying whether the Document is active or not after the promises have been resolved should mitigate some of th

RE: [EXTERNAL] Re: [blink-dev] Intent to Implement and Ship: Add support for Promise to Blobs in clipboard item

LGTM1 to ship conditional that y'all continue to work on PR #158

RE: [EXTERNAL] Re: [blink-dev] Intent to Implement and Ship: Add support for Promise to Blobs in clipboard item

Gentle ping as the branch cutoff date for 97 is pretty close. While I agree that the issues related to clipboard API spec need to be addressed, I don't think this feature needs to be blocked on that. It's not a breaking change i.e. sites can continue to use Blobs if they want to(although I don't

[blink-dev] RE: [EXTERNAL] Re: Intent to Implement and Ship: Feature policy for Keyboard API

getLayoutMap() can already be accessed by the top level browsing context and I believe it does have fingerprinting concerns: a site can gain knowledge of the keyboard layout of the user even before the user has typed anything. Try this site switching between French and English keyboard layouts:

[blink-dev] RE: [EXTERNAL] Re: Intent to Implement and Ship: Feature policy for Keyboard API

Can you clarify what the current situation is? getLayoutMap() which is part of the Keyboard API can only be accessed in the top browsing context which cuts off access from same and cross origin iframes. With this permission policy based solution, the default value would be "Self" that grants acce

[blink-dev] Intent to Implement and Ship: Feature policy for Keyboard API

Contact emails sni...@microsoft.com Explainer https://github.com/WICG/keyboard-map/issues/38 Specification https://wicg.github.io/keyboard-map/#permissions-policy Summary getLayoutMap() used in conjunction with code solves the problem of identifying the actual k

RE: [EXTERNAL] Re: [blink-dev] Intent to Implement and Ship: Add support for Promise to Blobs in clipboard item

Yep, I'll address the feedback from Anne and mbrodesser (from Mozilla). Thanks for all your help Anne and Yoav! From: Yoav Weiss Sent: Thursday, October 7, 2021 12:03 AM To: Anupam Snigdha Cc: ann...@annevk.nl; blink-dev@chromium.org; m...@chromium.org; Bo Cupp Subject: Re: [EXTERNAL] Re: [bli

RE: [EXTERNAL] Re: [blink-dev] Intent to Implement and Ship: Add support for Promise to Blobs in clipboard item

Here is a WIP PR to address the spec issue: https://github.com/w3c/clipboard-apis/pull/158. From: Anupam Snigdha Sent: Monday, October 4, 2021 10:45 AM To: 'Yoav Weiss' ; Anne van Kesteren Cc: blink-dev ; Marijn Kruisselbrink ; Bo Cupp Subject: RE: [EXTERNAL] Re: [blink-dev] Intent to Implemen

RE: [EXTERNAL] Re: [blink-dev] Intent to Implement and Ship: Add support for Promise to Blobs in clipboard item

For #1: I don't think we would want to diverge from the spec. There is a reason why we have promises to Blobs and not just Blobs in the ClipboardItem because, well, not having promises defeats the purpose of having an async API. Also waiting for the Blob data synchronously without triggering the

RE: [EXTERNAL] Re: [blink-dev] Intent to Implement and Ship: Add support for Promise to Blobs in clipboard item

4:54 AM To: Anupam Snigdha mailto:sni...@microsoft.com>> Cc: blink-dev mailto:blink-dev@chromium.org>>; Marijn Kruisselbrink mailto:m...@chromium.org>>; Bo Cupp mailto:pc...@microsoft.com>> Subject: [EXTERNAL] Re: [blink-dev] Intent to Implement and Ship: Add support for

RE: [EXTERNAL] Re: [blink-dev] Intent to Implement and Ship: Add support for Promise to Blobs in clipboard item

lbrink ; Bo Cupp Subject: [EXTERNAL] Re: [blink-dev] Intent to Implement and Ship: Add support for Promise to Blobs in clipboard item On Wed, Sep 29, 2021 at 3:02 AM 'Anupam Snigdha' via blink-dev mailto:blink-dev@chromium.org>> wrote: Contact emails sni...@microsoft.

[blink-dev] Intent to Implement and Ship: Add support for Promise to Blobs in clipboard item

Contact emails sni...@microsoft.com, m...@chromium.org Explainer https://www.w3.org/TR/clipboard-apis/#typedefdef-clipboarditemdata Specification https://www.w3.org/TR/clipboard-apis/#typedefdef-clipboarditemdata Summary Add promise sup