Anne van Kesteren wrote: > Quoting Andrew Shellshear <Andrew.Shellshear@research.canon.com.au>: > >>> SVGSVGElement interface has focus related methods(moveFocus(), >>> setFocus()). >>> What happens when a SVG document has nested <svg> element? >>> I think a focus is only one in document, not <svg> fragment. I think >>> Document Interface should have focus related methods. >> >> We put them on SVGSVGElement and not SVGDocument (or Document) >> because there might not be an SVGDocument. This can happen when we >> are in a multi-namespace XML application, and SVG is just one >> component of it, such as in CDF scenarios - here, the root element of >> the XML document isn't the svg element, and there is no SVGDocument. > > How does SVGDocument depend on the root element of the document? It > might very > well be that the document object supports all specialized document > objects. So > the document object has both HTMLDocument and SVGDocument implemented. (I > believe this is the case in some UAs, at least.) It *could* be the case that there is no SVGDocument at all. It's allowed. So we can't put focus-related methods on it. (Sorry if I'm missing the point, here.) > Also, this answer does not say if the second question, regarding > nested svg:svg > elements, is addressed. True. This case applies only to SVG Full, of course - an SVG implementation inside a foreignObject will be a separate entity, and won't interact with the "parent" svg. I suspect in the Full case, any calls to setFocus or moveFocus would not cross the SVGSVGElement boundary - they would only apply to descendants of this SVGSVGElement (stopping at any child SVGSVGElement). SVG Full 1.2 is a work in progress, and we will address this comment before the next published draft. Andrew.Received on Tuesday, 29 November 2005 00:56:01 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 4 September 2006 18:11:42 GMT