Firefox3.1/SMIL Security Review: Difference between revisions

no edit summary
No edit summary
Line 138: Line 138:
*** So, the number of "begin" vs. number of "end" elements doesn't really matter.  Hopefully this is more clear.
*** So, the number of "begin" vs. number of "end" elements doesn't really matter.  Hopefully this is more clear.
** what if they are misordered? Do they match by index in the given lists or do the begins run until the next specified end?
** what if they are misordered? Do they match by index in the given lists or do the begins run until the next specified end?
*** <b>dholbert</b>: List-order doesn't matter in the begin / end lists -- only temporal order.  Basically, each begin runs until the next specified end, unless we're already past the latest-in-time end value. (See answer to previous question for more detail)
*** <b>dholbert</b>: List-order doesn't matter in the begin / end lists -- only temporal order.  Basically, each "begin" triggers an instance of the animation (with duration "dur"), and the run will be interrupted by any "end" times encountered during it run. (See answer to previous question for more detail)
* integer overflows if images get too big? translated way offscreen?
* integer overflows if images get too big? translated way offscreen?
** SVG keeps things in floating point, cairo's interface is floating point
** SVG keeps things in floating point, cairo's interface is floating point
Confirmed users
489

edits