- From: Samad Aghaei via GitHub <sysbot+gh@w3.org>
- Date: Mon, 16 Dec 2019 23:16:38 +0000
- To: public-houdini-archive@w3.org
@tabatkins I think you went too far. I didn't want the Paint API to be a replacement for HTMLElement, at least at this point. Regardless of Font/Text API, just I wanted to have a "two-way" communication with registered paint class and I think having such a feature is very normal. Currently, there is almost no way to get [any kind of] data back from worklet. Event though the Atomics API are exposed, but there is no way to send sharedArrayBuffer to the worklet. Dynamic modules in worklets are not dynamic even, they are static in fact, only accepting String as input argument and must be defined at the top root of the worklets and not working in eval(). I know you may are concern about cyclic events, but don't you think that preventing it is up to the developers? cyclic event can always happen anywhere but we have to be careful, as we did it for years. -- GitHub Notification of comment by samad-aghaei Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/881#issuecomment-566292235 using your GitHub account
Received on Monday, 16 December 2019 23:16:39 UTC