Re: Path to polyfilling CSS functions?

|  But from a
|  browser perspective, that's a footprint issue. Why do you want a browser
|  based on Gecko to store "-webkit-foo: blah" if there is nothing it can
|  do with it? Polyfilling based on the browser's parser would be
|  extremely expensive in memory.

If the solution to this problem is to use variables or a custom parser, this 
is what we will get anyway. 

Received on Tuesday, 7 August 2012 06:19:17 UTC