- From: Evan Stade <notifications@github.com>
- Date: Tue, 12 Dec 2023 09:05:32 -0800
- To: w3c/clipboard-apis <clipboard-apis@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 12 December 2023 17:05:38 UTC
Perhaps "deprecated" is too strong a word. "Unfavored"? "overused"? "Rarely the best choice"? It seems that "in parallel" is often an under-specification because it introduces races into any algorithm steps that operate on global state, and is unnecessary in the case of a returned promise. It was applied more widely in older specs. What few specs I have written have gotten by with a [parallel queue](https://html.spec.whatwg.org/multipage/infrastructure.html#parallel-queue), task source, or the use of promises. In the case of the clipboard, Chromium is largely following the letter of the spec (and then some --- I believe the spec algorithms are missing some steps/checks), which causes problems because by the time "in parallel" steps begin to execute, global state may have changed. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/clipboard-apis/issues/202#issuecomment-1852450206 You are receiving this because you are subscribed to this thread. Message ID: <w3c/clipboard-apis/issues/202/1852450206@github.com>
Received on Tuesday, 12 December 2023 17:05:38 UTC