SVG:Use
		
		
		
		Jump to navigation
		Jump to search
		
Mental Testcases
- svg:use linked to:
- same document displayed content
- same document undisplayed content
- other document
- foreignObject containing HTML form elements (textbox)
 
- dynamic changes
- attribute change within used content
- style change inherited from ancestor of use
- tree structure changes within use
- addition/removal of use itself
- non-DOM content changes (e.g. form contents)
 
- event delivery to shadow instance tree
Implementation Strategies
No Frame Tree
- remove multiple presentations
- Move SVG painting and event handling to content
- ownership of style context also therefore goes to content
 
- Clone content for svg:use
- Let style contexts know they're held by content (bit)
Single Content Tree, Multiple Frame Trees
- leverage multiple presentations
- extend current architecture to support multiple primary frames for an element in the same frame tree
- useful for table header/footers, repeating fixed elements too
 
 
- extend current architecture to support multiple primary frames for an element in the same frame tree
- use existing content-style-frame setup
- SVG elements whose style we need (e.g. gradients) continue to need frames
- hack style system to get inheritance-across-use to work (how?)