Also sprach Tab Atkins Jr.: > > The same will work in this proposal: > > > > .button { > > effect: on-entry change(color, 1s), on-exit change(color, 1s); > > } > > That doesn't seem to work. At no point are you exitting the .button > "state". When you match .button:hover, you still match .button. Right. It works it we say: The effects on a given element trigger when the value of the 'effect' property changes, or when the element changes state. We'll need to define "changes state" carefully, but I think it's doable. > > I agree with you that we need to look at common use cases and compare > > syntax. > > Cool. What did you think of my breakdown of use-cases? Do you see > any additional ones? Anything that should be broken apart or > reorganized? I need to think a little. I'll get back on this -- it's a good way to compare proposals. -h&kon Håkon Wium Lie CTO °þe®ª howcome@opera.com http://people.opera.com/howcomeReceived on Monday, 5 April 2010 21:04:30 UTC
This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:07:44 UTC