- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Tue, 26 Jul 2011 12:28:16 -0700
- To: Brian Kardell <bkardell@gmail.com>
- Cc: Daniel Glazman <daniel.glazman@disruptive-innovations.com>, www-style@w3.org
On Tue, Jul 26, 2011 at 12:00 PM, Brian Kardell <bkardell@gmail.com> wrote: > That would go a long way IMO. > You could let through all of the dash-prefixed properties and not limit it > to web-* right? If so, you could allow the method that accesses it to > provide a prefix filter. What do you want to do with the other prefixed properties? > This might be too much to ask, but I think it would be possible to create a > way for people who really did want to "experiment" as you are saying with > true innovation with a CSS-like grammar in a way that couldn't mix with > CSS... All that would be necessary would be to allow allow the parser > "parse" but not respect a file via a mime type pattern or something (say > like type="text/css-xxx"). Then could never overlap but people could take > advantage of a good / fast native parser. > This last approach, actually, could solve both problems fairly well and > without much change - it would just require people to keep the "new" stuff > in a separate sheet and use feature detection or something to determine > which ones to shim (not unlike today). This can be done currently by using a preprocessor to transform the experimental syntax into vanilla CSS. Is there a problem with that? ~TJ
Received on Tuesday, 26 July 2011 19:29:10 UTC