Guillaume

Might be fixed by #134.

I read your post(s) about it. It sounds very interesting. I didn't realize it could fill this space (code transformers). I'm not sure if I can take any new responsibilities...

Since I spent some time on this plugin, maybe I can try to help you if you provide a reproduction repo.

I believe that the suggested change will break chunk names flushing, and that adding an example in the README isn't a good idea since it's the RUC responsibility to provide...

I believe it's resolved by https://github.com/faceyspacey/react-universal-component/pull/99 and this issue can be closed.

How do you prevent an SVG which has a viewBox, no width/height, and is a flex *column* item, to expand the width of its (flex) container in Firefox? Eg.: a...

I created this [codepen](https://codepen.io/creativewave/pen/YzZzORr?editors=1100) to visualize the differences between browsers, if it can help anyone figure out the issues that still stuck me for hours, 2 years after my previous...

If it can save someone's time who would have wished to fix this... * [Fix PR](https://github.com/browserify/resolve/pull/224) (work in progress) * Related: #255

> Going further, maybe we should disallow reordering the values? There is precedent to have the `*-name` first: the `container` shorthand has the `container-name` first and then the container-type. `animation`...

After reading [this thread](https://lists.w3.org/Archives/Public/www-style/2012Sep/0393.html), I wonder if `none` could not be further restricted to be used alone in `transition` and `view-timeline`. > First, animation-name: none is basically a special value...