Glad that you were able to figure it out! And yeah, that can be a
non-obvious requirement of operating in a worker. I'll see if there's any
sensible places for us to surface that to the rest of the community.
--Brandon
On Wed, Aug 2, 2023 at 11:26 PM wenhan chong wrote:
> Hi Brandon,
>
> Thanks
Contact emailsbajo...@chromium.org, cwal...@chromium.org
Explainerhttps://gpuweb.github.io/gpuweb/explainer/
Specificationhttps://www.w3.org/TR/webgpu
Design docs
https://gpuweb.github.io/gpuweb
https://gpuweb.github.io/gpuweb/wgsl
https://gpuweb.github.io/gpuweb/explainer
Summary
This Intent t
hris Harrelson wrote:
>>
>> LGTM1 - this is an easy one :)
>>
>> On Fri, Oct 27, 2023 at 1:21 PM 'Brandon Jones' via blink-dev <
>> blink-dev@chromium.org> wrote:
>>
>>> Contact emails bajo...@chromium.org, cwal...@chromium.org
>>&g
Hi Wenhan!
I [wrote a quick test](https://codepen.io/toji/pen/ZEmVypz) to try this out
and I'm able to see the uncapturederror events in the worker and forward
them on to the main thread for logging.
Is there a reduced version of the code that's producing the issue that you
could share? Because o
The link was previously working for me, but I've updated it just in case.
Thanks!
On Wednesday, August 14, 2024 at 10:32:29 AM UTC-7 Caleb Raitto wrote:
> FYI, in the Chrome status entry (
> https://chromestatus.com/feature/5077077997649920), the link to this
> intent to prototype is broken.
>
