Good lord. You really don't want to be doing actual parsing of CSS here. We already have one CSS parser, having two just means that we'll have twice as many bugs (probably more than twice, since this code won't be tested much).
Does it deal with CSS escapes? CSS comments? etc.
Surely there's a better way to do this.
Good lord. You really don't want to be doing actual parsing of CSS here. We
already have one CSS parser, having two just means that we'll have twice as many
bugs (probably more than twice, since this code won't be tested much).
Does it deal with CSS escapes? CSS comments? etc.
Surely there's a better way to do this.