Just want to say thanks for taking this suggestion seriously, i think its an excellent opportunity to extend the abilities of css but at the same time allowing it to work in all browsers.
On Jun 15, 4:50 am, Nathan Weizenbaum <[EMAIL PROTECTED]> wrote: > There are several reasons for keeping functions out of normal CSS. The > first is that it becomes much, much easier to parse; we don't have to > think about the content of the attributes at all. This is a good thing. > A slightly less Nathan-is-lazy reason is that CSS3 defines a lot more > function-like things, including stuff like hsl, and I don't want to > interfere with that at all. > > - Nathan > > s.ross wrote: > > I think you're right about the undefined functions evaluating to CSS. > > That seems like a cool way to treat it. Also, would it be desirable to > > use the quoted form to explicitly coerce something into CSS? > > > Is there a particular reason not to allow functions as an attribute? I > > certainly prefer specifying colors as constants in a block at the top > > of my Sass, but a CSS person might expect that functions would be > > available in that context. > > > Steve --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/haml?hl=en -~----------~----~----~----~------~----~------~--~---
