Raphael Schweikert

> From the references, `/` as delimiter might only be needed for [`border-image`](https://developer.mozilla.org/en-US/docs/Web/CSS/border-image) and not any other property. I think we introduced it because we wanted to parse `font: Helvetica...

So that means I should use the static weaving bundle version 1.1.x even though my bundle was built with the tool version 1.3.7 and there actually is a static weaving...

Or is the problem that the static weaving bundle at its POM version 1.3.7 mistakenly exports the package also at version 1.3.7 when it should export 1.1.x? 

> This seems the more likely culprit, but you’ll need one of the current maintainers to confirm. Ah, that also makes sense. I changed the PR to do that instead....

> We can follow what browsers do: https://developer.mozilla.org/en-US/docs/Web/CSS/@charset Yes good idea. Though browsers have a `Content-Type` header that may include a `charset=` specifier that we don’t have (as well as...

> * Determining whether the next item is a rule or a nested declaration block is slightly tricky: > > * The next characters of interest that would determine which...

> Also, I'm not sure normalizing the color format should be a responsibility of the CSS parser. IMHO, a parser should return the CSS as it is and not transform...

> You can work around this by commenting out `::1 localhost` in /etc/hosts. Not the best solution, but better than nothing.. This did not work for me. I suspect the...