JakeQZ

Related: https://github.com/w3c/csswg-drafts/issues/7218

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.

> > 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...

> In the case of `font-*`, I can't think of a value component that might contain a comma apart from a typeface name, in which case it would surely need...

> Battle plan as discussed in our call right now: > > 1. 8.x We add a `consumeWhiteSpaceWithComments` > 2. 8.x `consumeWhiteSpace` redirects to `consumeWhiteSpaceWithComments`, redirect it to the new...

#173 has finally been fixed by #1169; however, the suggestions here seem good for consideration moving forwards.

So I am thinking that the logging should be taking place where the exceptions are handled (if the conditional `bLenientParsing` comes into play), rather than where they are thrown. Though...

In the meantime, I've had another brief look. I think the use of `LoggerAwareInferface`, `LoggerAwareTriat`, etc., looks perfect: exact;ly what we want. (I just noticed you had a bunch of...

> Can the logging be done downstream, using the data from the exception where it is caught? This would have to be reviewed on a case-by-case basis. Sorry, I haven't...

Can wie have the introduction of the logger interfaces in solo, without any actual logging, as a separate initial pre-PR? I feel there should be some unit testing for that,...