Elliott Sprehn

@domfarolino I don't understand what you mean by `With respect to subscribe(), Observables are "async":`, the subscribe callback can emit synchronously (the firehose situation). That's what I'm pushing back on,...

> In more than a decade of this type, the lack of async emission has hardly ever been the issue. I disagree with this statement. It's not been my experience,...

Wouldn't custom element callbacks run inside the operation making all the intermediate states visible? I don't think we can skip running the constructors or attached callbacks and do a layout,...

I like the spirit of this, though I think you'd need to make the events uncancellable per the top comment and the default action happen in the past for this...

@smaug---- Chrome/WebKit at least have a concept of "finished parsing children": https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/html/forms/html_select_element.cc;l=1328;drc=48ee6c4ee320c1bcc4f7d01d5c293e6d41ecf648 In Chrome's implementation of `` it seems to discard and clone the contents every time the MutationObserver on...

This change was made in Chrome relatively recently (early 2023) apparently because they thought it followed the spec better: https://source.chromium.org/chromium/chromium/src/+/766274f6af98374883d2c30ca2dc0fc116f407ad Collection of all documents is here: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/page/page_animator.cc;l=102;drc=4268052f5025da8b928c9e59a04493b396acaad3 It used to...

Oh I see, yeah it looks like chrome did this on purpose on a spec violating optimization: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/page/page_animator.cc;l=153;drc=4268052f5025da8b928c9e59a04493b396acaad3 I think they should probably revert that optimization.

@rniwa that was the part of the spec I was saying Safari does not implement. It walks the tree in every step: https://github.com/WebKit/WebKit/blob/64f40e1806635d78dfe9a758585b5598d8793034/Source/WebCore/page/Page.cpp#L3997

@emilio yeah you're right, I re-read the Chrome code and edited my comment. My bad for the confusion there.

I don't think what Chrome's doing qualifies for that step, because if your iframe has mutated content (ex. appended new text, updated styles) Chrome will consider that document for updating...