- From: snianu <notifications@github.com>
- Date: Mon, 18 Sep 2023 11:34:37 -0700
- To: w3c/clipboard-apis <clipboard-apis@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/clipboard-apis/pull/175/c1724162655@github.com>
Thanks @polx for the review and apologies for the delay! > A web custom format has is custom set to true. => A representation in a web custom format has is custom set to true ? Note that in the spec it's referred to as `[=representation/isCustom=]` > step 1: why is the variable called webCustomFormat ? It should be formats or something universal, right? This is referring to the custom format with a `web ` prefix, so it can be anything. In the below step, we strip out the `web ` prefix: `If |webCustomFormatString| has "web "("web" followed by U+0020 SPACE) prefix, then remove the "web " prefix and store the remaining string in |webCustomFormat|'s {{Blob/type}}'s [=MIME type/essence=], else abort all steps.` > step 2.3: Let payload be the result of UTF-8 decoding item’s underlying byte sequence. : this must be a misunderstanding as it would only apply to text. Maybe the whole section was about text? Then it was not readable This is by-design that we write raw bytes sequence to the clipboard for the custom formats so the reader has to know how to parse its content (which is also by-design). > the steps of “write web custom formats” sound quite solid to me but why is it independent from the previous? This is because we need to perform an additional step to produce a native clipbaord format and insert the key-value pair into the `webCustomFormatMap`. This step is not performed for mandatory data types. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/clipboard-apis/pull/175#issuecomment-1724162655 You are receiving this because you are subscribed to this thread. Message ID: <w3c/clipboard-apis/pull/175/c1724162655@github.com>
Received on Monday, 18 September 2023 18:34:42 UTC