- From: Wenson Hsieh <wenson_hsieh@apple.com>
- Date: Thu, 09 Feb 2023 08:36:25 -0800
- To: public-editing-tf@w3.org
- Message-id: <D14BBD50-6744-41DF-A2A1-F746DE8619FA@apple.com>
[08:10] <whsieh> johanneswilm: first issue — delayed clipboard rendering 417 [08:11] <whsieh> anasollanokim: presented delayed clipboard rendering last time, resolving feedback: does existing API work? [08:12] <whsieh> anasollanokim: been working on that but no resolution yet, since we're unsure how the promises are going to be resolved [08:12] <whsieh> anasollanokim: can't guarantee when the promise will be resolved browser-side [08:13] <whsieh> anupam: need signal that system is trying to read data, exposed to web [08:14] <whsieh> whsieh: that's when promise is called [08:18] <whsieh> text/html => promise1 [08:18] <whsieh> image/png => promise2 [08:18] <whsieh> only promise2 is resolved if you go and paste an image [08:19] <whsieh> johanneswilm: what to do when navigating away? [08:20] <whsieh> johanneswilm: when you navigate away, the promise is gone [08:20] <whsieh> whsieh: (or the promises are all resolved — there are multiple ways to solve this problem) [08:20] <snianu> present+ [08:21] <edgar> present+ [08:22] <whsieh> johanneswilm: let's move on to next issue: issue 414, composition border [08:22] <snianu> We will work with our partners and see if the promise approach works for them. If not, then we can discuss further. [08:22] <GameMaker> present+ [08:22] <whsieh> snianu: sounds good! [08:23] <whsieh> johanneswilm: JS editors can't do anything about IME composition UI until composition is already done [08:23] <whsieh> johanneswilm: proposal: specify composition border around element, composition stays around until element is gone (?) [08:24] <whsieh> johanneswilm: if you try to change the DOM around the composition, it can interrupt the composition [08:25] <whsieh> johanneswilm: if you can mark an element as composition border then you can move elements adjacent to the composition [08:28] <whsieh> johanneswilm: is this a problem worth solving? is this proposal the way we should solve it? [08:28] <whsieh> snianu: preferred approach is to use EditContext [08:30] <whsieh> johanneswilm: Mozilla needed to check on status of VK API [08:31] <whsieh> johanneswilm: (w.r.t. https://github.com/w3c/editing/issues/413) [08:31] == AlexK [~AlexK@a11e3e9c.public.cloak] has joined #editing [08:32] <whsieh> johanneswilm: we need to recharter [08:32] <whsieh> johanneswilm: will contact w3c staff and ask for next steps
Received on Thursday, 9 February 2023 16:37:23 UTC