smaug----
smaug----
MutationObserver.observe() certainly requires at least one argument.
oh yeah, the API certainly has higher nativeJS overhead. With events you often just check the type and then do the rest in JS. Calling preventDefault() or .stopPropagation() might happen,...
Yes, that event handling through Observable operators.
I am having trouble to understand why one would need transient activation for this. At least I wouldn't implement this before there is some telemetry data about the current usage.
right, and then I wouldn't use that site again. Sites can do many annoying things. Do we have any telemetry data whether this is actually web compatible?
I think I'd still prefer to call this thing something else than "event group". It is more like a wheel transaction or some such. And sorry being late here. Getting...
What would optional mean in this context? And yes, capturing the stack every time fetch() or weblock is triggered might be quite overkill for performance.
Hmm, so what does LoAF actually expose? @noamr you say only source URL, but the APIs have fields for more. @rubberyuzu have you done any performance measurements on this stuff?
I wouldn't expect experiments to find the possible performance issues. I was thinking actual performance profiling.
Looks performance might be good enough if done like what LoAF does. > We can start by capturing source locations for `fetch`, `weblock` and `websocket` and add the source location...