Stefan Krause

I created a folder broken_frameworks and moved incr_dom there. Suggested Policy: For non-keyed frameworks I'd just move frameworks, for keyed-frameworks I'd create an issue and contact the contributor and move...

@LXSMNSYC Would you like to submit a PR for that?

That would be fine. You could just submit a new vanillajs implementation and I'd remove the others when I checked that it's the fastest.

See 2fda7e9f2d464d53e907a9d84f40741bcbedab24 for vanilla-dom-js, 01b07c23cde27cd4a5916ba7a62bd32ac0a1ad98 for pux. Warnings are gone for these frameworks.

@alexfmpe I think the warning for reflex-dom is also due to that missing span. Can you please add it?

Looks good. No more warnings for those benchmarks. I'll leave the issue open for future reference.

This message mattered for older versions of chrome when more than a single paint event really meant that something didn't behave as expected. For newer chrome version this occurs fairly...

I wouldn‘t call it „penalize“. It‘s not an error like #694, it‘s just a note that the implementation might take advantage from a user code event delegation. If that‘s the...

Surely. For the startup benchmark I'm relying on lighthouse and running 4 runs. I just repeated it for lit on my linux razer blade machine and got the following results:...

I tried running lighthouse on the command line and comparing the results: lighthouse http://localhost:8080/frameworks/keyed/lit/index.html --output=json --only-audits=bootup-time | less The results are not really comparable to what the benchmark driver reports,...