Gerald Monaco

Thanks, I'll take a look and get back to you.

@nyoung697 There was an issue with how escaped tokens were being parsed and serialized that I fixed in [796f0cc](https://github.com/GoogleChromeLabs/container-query-polyfill/commit/796f0cc935ec9590f7a87c60e17aa96517c3903b) and verified with your demo. I've gone ahead and published 0.2.1....

This should be addressed by the latest version of the polyfill (currently in alpha). Please give it a try. I'm going to close this issue for now, but I would...

> It would be great if there was some way to try a "fully buffered" version of RSC in the meantime. So that this demo can be compared apples-to-apples to...

Thanks for your suggestion! The way that `em` and `rem` support work today is that the polyfill will read the computed `font-size` property on the appropriate elements to get the...

I think something like that certainly would work in a lot of cases. My concern about brittleness though is mostly that it's really easy to accidentally break in real world...

> `font-weight: thin` does not exist (nor does `light`) Oops, I meant `lighter`. Thanks for the correction. > and an internal font metric like `ch` won't change with font-weight No...

The problem is more that when e.g. `#foo` changes, we don't currently know that the sibling `div` could also be affected. The approach of keeping track of the selectors that...

Apologies for the churn -- I was hoping to get those changes in _before_ you rebased 🙂

#53 was merged, so you should be able to rebase against main now.