Confirmed users
490
edits
CSS Transitions: Difference between revisions
Jump to navigation
Jump to search
m
→Notes from 2008-10-30 Meeting
(Add a section with notes from today's meeting) |
|||
| Line 76: | Line 76: | ||
= Notes from 2008-10-30 Meeting = | = Notes from 2008-10-30 Meeting = | ||
* Decisions: | * Decisions: | ||
** Animated style should be stored in a special per-element rule node | ** Animated style should be stored in a special per-element rule node, which will be kept up-to-date by the SMIL/animation code. | ||
** This rule node fits right in the middle of the CSS cascade (overrides other style, but not <code>!important</code> styles) | ** 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> | ** 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. :) | ** <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") | ** Initially, we won't support transitions on pseudo-elements (e.g. "first-letter") | ||