- From: roraja <notifications@github.com>
- Date: Thu, 21 Aug 2025 00:08:45 -0700
- To: w3c/clipboard-apis <clipboard-apis@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/clipboard-apis/pull/239/review/3139338562@github.com>
@roraja commented on this pull request. > + is not triggered by a user action but rather by changes to the [=system clipboard=] state. + + <div id="clipboardchangeeventinit-idl"> + + <pre class="idl" data-highlight="webidl"> + dictionary ClipboardChangeEventInit : EventInit { + sequence<DOMString> types = []; + DOMString changeId = ""; + }; + </pre> + + : <dfn for="ClipboardChangeEventInit" data-export>types</dfn> + :: A sequence of {{DOMString}} representing the [=mandatory data types=] available on the [=system clipboard=]. + + : <dfn for="ClipboardChangeEventInit" data-export>changeId</dfn> + :: A {{DOMString}} representing a unique identifier for this clipboard change operation. Since the changeID is mostly locally unique and not something that we would need to store in a database or persist, a BigInt indeed might be good enough for us. Though there are less chances of collisions in UUID, still for our use-case this should not be a problem. Though I couldn't find any existing spec where BigInt is used as a local identifier. I will still go ahead and change this ID's type to BigInt to prefer simplicity as you mentioned. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/clipboard-apis/pull/239#discussion_r2290094682 You are receiving this because you are subscribed to this thread. Message ID: <w3c/clipboard-apis/pull/239/review/3139338562@github.com>
Received on Thursday, 21 August 2025 07:08:49 UTC