Moving async-append to WICG


#1

We have been discussing the ability to construct and append DOM asynchronously so that the render lifecycle does not jank the page. See explainer at https://github.com/drufball/async-append.

At TPAC there seemed to be generally positive signals around the problem space and the general structure of the API. Should we move the repo to WICG for easier collaboration/iteration?


#2

Sounds great! Do you have notes/minutes indicating said positive signals from other browser vendors or community members?


#3

At TPAC, Microsoft Edge’s request was for the work to be transferred to the WICG so we could participate in a full review/discussion of the proposal. The problem space making the web asynchronous is important for all of us to be involved with.


#4

The repository has just been moved to WICG:

Feel free to file issues and start improving! :slight_smile:

/cc @iank @esprehn @tabatkins @domenic