Guillaume

I do not have a personal interest for this feature (I came across this issue to report the following potential oversights) but it seems a bit unfortunate to me to...

Right, sorry! The unit is parsed as an *an ident sequence* (string) and it must match `` (or ``, as suggested).

Can I assume the expected changes (in CSS Backgrounds 3) are as follows? ```diff If three values are given, the missing offset is assumed to be zero. + + Serializing...

Then is there any reason to keep serializing 1-value inputs with 2 values? ***edit:*** never mind, 3-value is specific to `` whereas 1-value is common to all position-like syntaxes and...

Hi @ScriptedAlchemy, can you please elaborate on this? > The universal component is effectively dead on webpack 5. If this is true, you can mark this package as deprecated, isn't...

Can't reproduce the issue with webpack v4.43.2 or v5.3.2, though I had this issue in a fork of this repository bundled with Rollup.

Yes, but if you're using it, `babel-plugin-universal-import` requires [this small change](https://github.com/faceyspacey/babel-plugin-universal-import/pull/143).

> [CSS-wide keywords] are treated specially in custom properties. I think they probably shouldn't be allowed in the initial value of a registered property. Sorry, but I am missing how...

To clarify my understanding: - in the first rule, `initial-value: var(1)` makes the descriptor invalid and ignored - in the second rule, `initial-value: var(--initial)` makes the rule invalid because it...

Indeed, I missed something. `initial-value` must be computationally independent only when `syntax` is `*`.