"Thanks for filing the issue!

@Reporter: Could you please share a sample test file with consistent reproducible steps which helps us to triage the issue in a better way from TE end."

Hm, this is a request for documentation. What would a test file look like? 🤔

All i need is something like

"The cloned node copy is completely ready when element.cloneNode(true) returns."

Or something else that tells me what the rules are.

Thank you for providing more feedback. Adding requester "vamshi.kommuri@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This is the document (spec) that describes how cloneNode() should
behave:
https://dom.spec.whatwg.org/#dom-node-clonenode
https://dom.spec.whatwg.org/#concept-node-clone

To answer your question, when you obtain the returned value
(which is a cloned node), the clone operation should be complete,
and synchronous.

Do you have any test case that demonstrates Blink's implementation
exposes any asynchronity, please file a new bug with a test case.

Thanks, that saves me a lot of trouble. :-)

I'm a bit surprised that you refer to whatwg, but I am pleased not having to read the W3C spec.

Since you refer to whatwg I tried to search for documentation about innerHTML and async/sync there. I just wanted to compare documentation since I have noticed innerHTML is async (sometimes). I would be glad for comments about that too.

I am really sorry to reopen this issue, but it still not clear to me: Where does the spec define it as synchronous?
I have read it, yet I could not find it crystal clear in this regard.
The case I am interested in is for an ImageElement node. When cloneNode returns, should the new object be loaded and fully functional? e.g., possible to draw in a canvas.