Re: [whatwg/dom] Minor textContent / string replace all optimization (Issue #1106)

> We still have that optimization. We just made it not run when it's observable.

@rniwa can you add some detail about how you do that, ideally with a link to code? I assume it's just checking that there aren't any MutationObservers or synchronous event listeners on the node or containing tree?

I'd be up for trying to remove the optimization **when it's observable**, assuming that's relatively straightforward. There is some (hopefully small?) web compat risk, since the behavior is currently observable.

Generally, I think it'd be odd to try to spec the observable part of this behavior, since it's confusing for developers to have such a special case. (I don't think we need to worry about unobservable optimizations like this, of course.)

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/1106#issuecomment-1235706314
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/dom/issues/1106/1235706314@github.com>