Quote:
Originally Posted by KevinH
So if the "url()" wrapper is required for a url in a content property we should be able to restrict on that, right?
|
We
should, yes. I'll have to figure a way to restrict the content property to only a content property that uses the url key word.
But right now, I'm trying to figure out what on earth I had in mind with the second half of the urls regex in PerformCSSUpdates. Even if it doesn't match on the url keyword, the second half of the "or" will match pretty-much any character(s) between to matched double or single quotes. I looked back through the history and the change is definitely on me (way back with the original multiple urls in the same property fix), but I can't for the life of me figure out what I was TRYING to capture with the:
Code:
"[\"']([^\\(\\)\"']*)[\"']"
portion of that regexp.