Martin Auswöger
Martin Auswöger
I raised the version numbers in 6605892075a1d782f5bcca5811456b978cea4124. The supported browsers for the next release are now: * Firefox 52+ * Opera 48+ * Chrome 49+ * Internet Explorer 11 *...
This should be postponed until more [browsers support](http://caniuse.com/#feat=intrinsic-width) these keywords. Implementing it now would decrease performance (because it needs the original style of the element) with little to no benefit....
From reading the code I don’t see a reason for it to be FOUC-ier than cq-prolyfill. But it depends on how you load the JavaScript and when you call `ContainerQuery.create()`....
I didn’t know that `MutationObserver` works while the HTML document is still downloading, I thought it only observes dynamically injected nodes. Because of that, cq-prolyfill is already FOUC-free. You can...
This is how that process for one of those `div`s looks like in the browser: 1. Receive Data 2. Parse HTML 3. Run Microtasks (cq-prolyfill jumps in) 1. Recalculate Style...
In my tests (with 20x CPU slowdown) the difference was not that big, the sync version took about 1.8 seconds and the defer version 1.6 seconds. But still, the defer...
I created issue #41 for the problem with multiple executions. And regarding your questions: > Does it therefore exhibit the scary performance characteristics that browser folks have foretold, e.g. https://twitter.com/tabatkins/status/866828359308726275...
Yes, _cq-prolyfill_ has to convert the `:container()` parts of the CSS so that the browser can parse it. You can prevent that by using the [PostCSS plugin](https://github.com/ausi/cq-prolyfill/blob/master/docs/postcss.md) or [Sass mixin](https://github.com/ausi/cq-prolyfill/issues/17#issuecomment-183756013)....
@VinSpee sorry, I still had no time to test your _ContainerQueryContainer_. As I don’t know much about React I didn’t really get how your component helps to use cq-prolyfill. What...
One of its goals is definitely to be production ready, but since it didn’t reach version 1.0 yet, there may be breaking changes in the future, see #8 for example....