Simplify/change time container association for <svg> fragments |
|||||
Issue descriptionCurrently we have one SMIL time container per <svg>. This allows fine-grained control since each one can be paused independently et.c. Simple demo: https://jsfiddle.net/kxv17u2o/2/ Gecko appears to have one per outermost root. Another option might be to have one per document (I think that would be more in-line with CSS/Web Animations - at least without animations groups? Not really sure.)
,
Aug 17 2016
This is what the SVG spec used to say (1.1; now section 2.3 in https://svgwg.org/specs/animations/): "SMIL Animation requires that the host language define the meaning for document begin and the document end. Since an ‘svg’ is sometimes the root of the XML document tree and other times can be a component of a parent XML grammar, the document begin for a given SVG document fragment is defined to be the exact time at which the ‘svg’ element's load event is triggered. The document end of an SVG document fragment is the point at which the document fragment has been released and is no longer being processed by the user agent. However, nested ‘svg’ elements within an SVG document do not constitute document fragments in this sense, and do not define a separate document begin; all times within the nested SVG fragment are relative to the document time defined for the root ‘svg’ element."
,
Aug 17 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 17 2017
,
Aug 20
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 20
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by f...@opera.com
, Aug 17 2016