wicg / async-append Goto Github PK

ex. a library will need to null check the batch and the arguments which is weird.

append(element, batch) means a library like:

doSomething(optional batch = null)

could exist without using apply() and prepending the batch if it's not null.

Can we spec both rest arguments for the start followed by batch?

ex.

asyncAppend(Node... node, DOMBatch = null)

not sure what webidl allows.

@tabatkins @domenic

@tabatkins added a bunch of states that are strings, maybe we should just expose those instead of a boolean for started?

We've heard from developers that async append needs some method to force the operation to become blocking after a certain amount of time. That way rendering can't be indefinitely starved.

@esprehn @bfgeek

This repo hasn't had much activity for a long time... would it be ok to archive this?

https://github.com/drufball/async-append/blob/master/gaming.youtube.com

@wycats has done a lot of investigation into what are the primitive DOM operations necessary to build up a tree, as part of whatwg/dom#270.

This proposal so far has:

• append
• prepend
• remove
• insertBefore

(I think maybe append and prepend could be reduced to insertBefore in theory.)

It is missing the following:

• setAttribute
• removeAttribute
• setTextData (can be semi-emulated by removing the text node and inserting a new one, but that has slightly different semantics)
• attachShadow

There is also the following non-primitive but convenient operation:

• insertAdjacentHTML (can be emulated with <template>.content and insertBefore on the resulting DocumentFragment)