Confirmed users
489
edits
CSS Transitions: Difference between revisions
Add a section with notes from today's meeting
m (s/proposed spec/proposed CSS Transitions spec/) |
(Add a section with notes from today's meeting) |
||
| Line 73: | Line 73: | ||
** "Each additive animation adds its effect to the result of all sandwich layers below. A non-additive animation simply overrides the result of all lower sandwich layers." | ** "Each additive animation adds its effect to the result of all sandwich layers below. A non-additive animation simply overrides the result of all lower sandwich layers." | ||
** "The animation first begun has lowest priority and the most recently begun animation has highest priority. When two animations start at the same moment in time, the activation order is resolved as follows: [...]") | ** "The animation first begun has lowest priority and the most recently begun animation has highest priority. When two animations start at the same moment in time, the activation order is resolved as follows: [...]") | ||
= Notes from 2008-10-30 Meeting = | |||
* Decisions: | |||
** Animated style should be stored in a special per-element rule node | |||
** This rule node fits right in the middle of the CSS cascade (overrides other style, but not <code>!important</code> styles) | |||
** We'll detect style-changes that require transitions inside of <code>DidSetStyleContext()</code> | |||
** <code>DidSetStyleContext()</code> will need to know whether it was called due to a "real" style change, or due to a style change from a transition/animation. This will hopefully prevent transitions/animations from triggering new transitions each time they update the style. :) | |||
** Initially, we won't support transitions on pseudo-elements (e.g. "first-letter") | |||