Surma
The data is correct in so far as that it reflects what the respective DevTools are showing when running the tests. Engineers from both Webkit and Gecko were just as...
@mstange Help would be greatly appreciated to automate this for Gecko! In case you haven’t seen it: The [`_suite`](https://github.com/GoogleChrome/css-triggers/tree/master/_suite) folder contains the code to generate and run the test suite.
That is very interesting info! And yes, I agree that it is unfortunate that one “edge-case” is distorting the data for Firefox. I’ll try and come up with a different...
I’d love it! PR please?
One big issue is that neither `:unresolved` nor `:defined` (or `:not(:defined)`) seem to be working for me in Chrome. Not sure what’s going on. Either way, one way we could...
Pushed a quick fix so that the build succeeds (needed a `README.md` :) Will take a deeper look soon.
Agreed, where possible, native elements should be used. See 7ca365291863f310c5006a01ec3029c62a485a6b
First paragraph from the README: “They are explicitly NOT a UI library meant to be used in production.” That being said, feel free to use them as a starting point...
It does not do it automatically because every callback requires creating a new proxy that holds on to the proxied value, which is basically a memory leak. If you want...
Yeah, I should have really provided that. Apologies. I dug through the WebAssembly file that triggered the problem for me, and the problematic function name in this case was `"RD4"`:...