16.1. References

16.1.1. Overview

On the Internet, resources are identified usingURLs(Internationalized Resource Identifiers). Forexample, an SVG file called someDrawing.svg located athttp://example.com might have the followingURL:

http://example.com/someDrawing.svg

AnURL can also address a particular element within an XMLdocument by including anURL fragmentidentifier as part of theURL. AnURL which includes anURL fragment identifier consists of an optional baseURL, followed by a "#" character,followed by theURL fragment identifier. For example, thefollowingURL can be used to specify the element whose ID is"Lamppost" within file someDrawing.svg:

http://example.com/someDrawing.svg#Lamppost

16.1.2. Definitions

URL reference

An URL reference is an Internationalized Resource Identifier, as defined inInternationalized Resource Identifiers [rfc3987]. SeeReferences andReferences and the‘defs’ element.

URL reference with fragment identifier

An Internationalized Resource Identifier [rfc3987] that can include an <absoluteURL> or <relativeURL> and a identifier of the fragment in that resource. SeeReferences and the‘defs’ element. URL reference with fragment identifiers are commonly used to referencepaint servers.

external file reference

AURL reference orURL reference with fragment identifier which refers to a resource that is not part of the current document.

same-document URL reference

AURL reference with fragment identifier where the non-fragment part of the URL refers to the current document.

data URL

AURL reference to an embedded document specified using the"data" URL scheme [rfc2397]. Data URL references are neitherexternal file references norsame-document URL references.

circular reference

URL references that directly or indirectly reference themselves are treated as invalid circular references. What constitutes a circular reference will depend on how the referenced resource is used, and may include a reference to an ancestor of the current element.

unresolved reference

A reference that is still being processed, and has not yet resulted in either an error or an identified resource.

invalid reference

Any of the following are invalid references:

• A circular reference.
• AURL reference that results in an error duringprocessing.
• AURL reference that cannot be resolved.
• AURL references to elements which are inappropriate targets for the given reference shall be treated as invalid references (seeValid URL targets for appropriate targets). For example, theclip-path property can only refer to‘clipPath’ elements. The property settingclip-path:url(#MyElement) is an invalid reference if the referenced element is not a‘clipPath’.

Invalid references may or may not be an error (seeError processing), depending on whether the referencing property or attribute defines fallback behavior.

16.1.3. URLs and URIs

Internationalized Resource Identifiers (URLs) are a more generalizedcomplement to Uniform Resource Identifiers (URIs). AnURL is a sequenceof characters from the Universal Character Set [UNICODE].A URI is constructed from a much more restricted set of characters. All URIs arealready conformantURLs. A mapping fromURLs to URIs is defined bytheURL specification, which means that URLs can be used instead of URIsin XML documents, to identify resources.URLs can be converted to URIsfor resolution on a network, if the protocol does not supportURLsdirectly.

Previous versions of SVG, following XLink, defined an URL reference typeas a URIor as a sequence of characters which must result in an URL after aparticular escaping procedure was applied. The escaping procedure was repeated in theXLink 1.0 specification [xlink], and in theW3C XML Schema Part 2: Datatypes specification [xmlschema-2].This copying introduced the possibility of error and divergence, but was donebecause theURL specification was not yet standardized.

In this specification, the correct termURL is used for this "URI or sequence of charactersplus an algorithm" and the escaping method, which turns URLs into URIs, is defined by reference to theURL specification [rfc3987],which has since become an IETF Proposed Standard. Other W3C specifications areexpected to be revised over time to remove these duplicate descriptions of theescaping procedure and to refer toURL directly.

16.1.4. Syntactic forms: URL and <url>

In SVG, most structural relationships between two elementsare specified using a URL value in an‘href’ attribute.However, manypresentation attributes allow both URLs and text strings as content.To disambiguate a text string from a relative URL, the<url>production is used for presentation attributes,and their corresponding CSS properties [css-values].This is simply a URL delimited with a functional notation.

SVG makes extensive use ofURL references, both absolute and relative,to other objects.For example, a‘linearGradient’ elementmay be based on another gradient element,so that only the differences between the two need to be specified,by referencing the source gradient with a URL in the‘href’ attribute:

<linearGradient>...</linearGradient><linearGradient                href="#SourceGradient">...</linearGradient>

To fill a rectangle with that gradient,the value of the rectangle'sfill property may be set so as toinclude a URL reference to the relevant‘linearGradient’ element;here is an example:

<rect fill="url(#MyGradient)"/>

16.1.5. URL reference attributes

URL references are normally specified with an‘href’ attribute.The value of this attribute forms a reference for the desired resource (orsecondary resource, if there is a fragment identifier).The value of the‘href’attribute must be a URL.

Because it is impractical for any application to check thata value is anURL reference, this specification follows the leadof theURL Specificationin this matter and imposes no such conformance testingrequirement onSVG authoring tools.An invalid URL does not make an SVG document non-conforming.SVG user agents are only required to process URLs when needed,as specified inProcessing of URL references.

16.1.6. Deprecated XLink URL reference attributes

In previous versions of SVG, the‘href’attribute was specified in the XLink namespace [xlink] namespace.This usage is now deprecated and insteadURL references should bespecified using the‘href’ attribute withouta namespace.

For backwards compatibility, the deprecated‘xlink:href’ attributeis defined below along with the‘xlink:title’ attribute which has alsobeen deprecated.

Attribute definitions:

Name	Value	Initial value	Animatable
xlink:href	URL[URL]	(none)	(see below)

For backwards compatibility, elements with an‘href’ attribute also recognize an‘href’ attribute in the XLink namespace [xlink].

When the‘href’ attribute is present inboth the XLink namespace and without a namespace, the value of the attribute without a namespace shall be used. The attribute in the XLink namespace shall be ignored.

Aconforming SVG generator must generate‘href’ attributes without a namespace. However, it mayalso generate‘href’ attributes in the XLink namespace to provide backwards compatibility.

This attribute isAnimatable if and only if the corresponding‘href’ attribute is defined to be animatable.

Name	Value	Initial value	Animatable
xlink:title	<anything>	(none)	no

Deprecated attribute to describe the meaning of a link or resource in a human-readable fashion. New content should use a‘title’ child element rather than a‘xlink:title’ attribute.

The use of this information is highly dependent on the type of processing being done. It may be used, for example, to make titles available to applications used by visually impaired users, or to create a table of links, or to present help text that appears when a user lets a mouse pointer hover over a starting resource.

The‘title’ attribute, if used, must be in the XLink namespace. Refer to theXML Linking Language (XLink) [xlink].

When using the deprecated XLink attributes‘xlink:href’ or‘xlink:title’ an explicit XLink namespace declaration must be provided[xml-names],One simple way to provide such an XLink namespace declarationis to include an‘xmlns’ attributefor the XLink namespace on the‘svg’ element for content that usesXLink attributes. For example:

<svg xmlns:xlink="http://www.w3.org/1999/xlink" ...>  <image xlink:href="foo.png" .../></svg>

16.1.7. Processing of URL references

URLs are processed to identify a resource at the time they are needed, as follows:

• For the‘href’ attribute of the‘a’ element, at the time the link is activated by the user.
• For all other‘href’ attributes, at the time the element isconnected to a document, or at the time when the attribute is set, whichever is later.
• For source URLs on embedded HTML media elements, as required based on source selection rulesin the HTML specification [HTML].
• For all presentation attributes and style properties, at the time the property is required for rendering an element.

Legacy‘xlink:href’ attributes are processed at the time a corresponding‘href’ attribute would be processed, but only if no such‘href’ attribute exists on the element.

Processing a URL involves three steps: generating the absolute URL; fetching the document (if required); identifying the target element (if required).

A URL reference isunresolved until processing either results in aninvalid reference or in the identification of the target resource. Unresolved references in the non-presentation attributes ofstructurally external elements prevent theload event from firing. User agents may place time limits on the resolution of references that are notsame-document URL references, after which the reference is treated as a network error (and therefore as aninvalid reference).

Forsame-document URL references in a dynamic document, modifications or animations of attributes or properties, or removal of elements from the DOM, may cause an URL reference to return to theunresolved state. The user agent must once again attempt to resolve the URI to identify the referenced resource.

16.1.7.1. Generating the absolute URL

If theURL reference is relative, its absolute version must be computed before use.The absolute URL should be generated using one of the following methods:

• as described inCSS Values and Units if the reference occurs in a CSS file or in apresentation attribute[css-values]
• as described inXML Base before use [xmlbase] if the reference occurs in any other attribute in an XML document
• as described in theHTML specification if the reference occurs in a non-presentation attribute in an HTML document that is not an XML document [HTML]

The‘xml:base’ attribute will only have an effect in XML documents; this includes SVG documents and XHTML documents but not HTML documents that are not XML. In contrast, abase element affects relative URLs in any SVG or HTML document, by altering thedocument base URL.

If the protocol, such as HTTP, does not supportURLs directly,theURL must be converted to a URI by the user agent, as describedin section 3.1 of theURL specification [rfc3987].

After generating the absolute URL:

• If the URL is being processed following the activation of a link, the user agent must follow thealgorithm for navigating to a URL described in the HTML specification [HTML]. The outcome of this algorithm varies depending on the‘target’ browsing context and security restrictions between browsing contexts, and on whether the link is to the same document as is currently contained in that browsing context (in which case the fragment is navigated without reloading the document). If the document that was navigated was an SVG document, then adjust the target behavior as described inLinking into SVG content.

• If the URL being processed is onlyvalid if it refers to a complete document file (such as the‘href’ attribute of an‘image’ and‘script’ element), continue as indicated inFetching the document (regardless of whether the URL is to the same document or not).

• In all other cases, the URL is for a resource to be used in this SVG document. The user agent must parse the URL to separate out the target fragment from the rest of the URL, and compare it with the document base URL. If all parts other than the target fragment are equal, this is asame-document URL reference, and processing the URL must continue as indicated inIdentifying the target element with the current document as the referenced document.

• Otherwise, the URL references a separate document, and the user agent must continue processing the URL as indicated inFetching the document.

As defined inCSS Values and Units, a fragment-only URL in a style property must be treated as asame-document URL reference, regardless of the file in which the property was declared.

16.1.7.2. Fetching the document

SVG properties and attributes may reference other documents. When processing such a URL, the user agent should fetch the referenced document as described in this section, except under the following conditions:

• If the URL reference is from thehref attribute onSVG animation elements, onlysame-document URL references are allowed [svg-animation]. A URL referring to a different document is invalid and the document must not be fetched.

• If the document containing the reference is being processed insecure static mode orsecure animated mode,external file references are disallowed. Unless the reference is adata URL, the user agent must treat the reference as if there was a network error, making this aninvalid reference.

• If any other security restrictions on the browsing context or user agent prevent accessing the external file, then the user agent must treat the reference as if there was a network error.

When fetching external resources from the Internet, user agents must use apotentially CORS-enabled request as defined in HTML [HTML] with thecorsAttributeState as follows:

• For an‘href’ reference on an‘image’ element or‘script’ element, the CORS state specified by the‘crossorigin’ attribute.
• For a reference from a style property or presentation attribute, the "anonymous" state.
• For all other references, the "no-cors" state.

The request'sorigin is computed using thesame rules as HTML, with an SVG‘script’ element treated like an HTMLscript element, and an SVG‘image’ element treated like an HTMLimg element. Thedefault origin behaviour must be set totaint.

A future SVG specification may enable CORS references on other SVG elements with‘href’ attributes.

If the fetching algorithm results in an error or an empty response body, the reference URL is treated as aninvalid reference.

If a valid response is returned, and thevalid URL targets for the reference include specific element types, the user agent must continue byProcessing the subresource document. Otherwise (if only entire-document the URL references are valid), then the fetched document is the referenced resource.

16.1.7.3. Processing the subresource document

Otherwise, the subresource must be parsed to identify the target element. If the fetched document is a type that the user agent can parse to create a document object model, it must process it insecure static mode (meaning, do not fetch any additional external resources and do not run scripts or play animations or video). The document model generated for an external subresource reference must be immutable (read-only) and cannot be modified.

If a document object model can be generated from the fetched file, processing the URL must continue as indicated inIdentifying the target element with the parsed subresource document as the referenced document. The user agent may commence the target-identification process prior to completely parsing the document.

User agents may maintain a list of external resource URLs and their associated parsed documents, and may re-use the documents for subsequent references, so long as doing so does not violate the processing mode, caching, and CORS requirements on the resource.

16.1.7.4. Identifying the target element

For URL references to a specific element, whether the reference is valid depends on whether the element can be located within the referenced document and whether it is of an allowed type.

Using the referenced document identified in previous processing steps (either an external subresource document or the current document), the target element is identified as follows:

• If the URL does not specify a specific element in a target fragment, the target element is the root element of the referenced document.

• Otherwise, the URL targets a specific element. If a matching element currently exists in the referenced document, then it is the target element.

• Otherwise, there is no currently matching element. If the referenced document is immutable, then the URL reference isinvalid. An external subresource document is always immutable once fully parsed; the current document is also immutable once parsed if it is being processed in any mode other thandynamic interactive mode.

• Otherwise, observe mutations to the referenced document until the URL can be successfully resolved to define a target element, or until the document becomes immutable (e.g., a non-dynamic document finishes parsing).

The target element provides the referenced resource if (and only if) it is avalid URL target for the reference.

16.1.7.5. Valid URL targets

The valid target element types for‘href’ (or‘xlink:href’) attributes are based on the element that has the attribute, as follows:

• the‘a’ element can reference any local or non-local resource
• the‘image’ element must reference a document that can be processed as an image
• the‘linearGradient’ element must reference a different‘linearGradient’ or‘radialGradient’ element
• the‘pattern’ element must reference another‘pattern’ element
• the‘radialGradient’ element must reference a‘linearGradient’ or another‘radialGradient’ element
• the‘script’ element must reference an external document that provides the script content
• the‘textPath’ element must reference an element type that implements theSVGGeometryElement interface
• the‘use’ element must reference either an SVG-namespaced element or an HTML-namespaced elementthat may be included as a child of an SVG container element

The valid target element types for style properties defined in this specification are as follows:

• thefill property (seeSpecifying paint for reference rules)
• themarker,marker-start,marker-mid andmarker-end properties must reference a‘marker’ element.
• theshape-inside andshape-subtract properties must reference an element type that implements theSVGGeometryElement interface, or a document that can be processed as an image
• thestroke property (seeSpecifying paint for reference rules)

For references that allow either a reference to a target element, or to an image file (such as theshape-inside,shape-subtract, andmask properties), the user agent must identify the target element and determine whether it is a valid target. If the resolved target element is not an allowed element type, the referenced resource is the entire document file; the target fragment is used in processing that file as with any other image.

In all other cases, if the resolved target element type (or document type) is not allowed for the URL reference, it is aninvalid reference.

<?xml version="1.0" standalone="no"?><svg width="5cm" height="3cm" viewBox="0 0 5 3" version="1.1"     xmlns="http://www.w3.org/2000/svg">  <desc>Example link01 - a link on an ellipse  </desc>  <rect x=".01" y=".01" width="4.98" height="2.98"         fill="none" stroke="blue"  stroke-width=".03"/>  <a href="http://www.w3.org">    <ellipse cx="2.5" cy="1.5" rx="2" ry="1"             fill="red" />  </a></svg>

Example link01

View this example as SVG (SVG-enabled browsers only)

16.3.1. SVG fragment identifiers

To link into a particular view of an SVG document, theURL reference with fragmentidentifier needs to be a correctly formedSVGfragment identifier. An SVG fragment identifier defines themeaning of the "selector" or "fragment identifier" portion of URLs thatlocate resources of MIME media type "image/svg+xml".

An SVG fragment identifier can come in the following forms:

• Shorthandbare name form of addressing (e.g.,MyDrawing.svg#MyView). This form of addressing, which allows addressing an SVG element by its ID, is compatible with the fragment addressing mechanism for older versions of HTML.
• AnSVG view specification (e.g.,MyDrawing.svg#svgView(viewBox(0,200,1000,1000))). This form of addressing specifies the desired view of the document (e.g., the region of the document to view, the initial zoom level) completely within the SVG fragment specification. The contents of the SVG view specification are defined inSVG fragment identifiers definitions section.
• Basic media fragments identifiers of type spatial or temporal (e.g.,MyDrawing.svg#xywh=0,200,1000,1000 or MyAnimation.svg#t=10)) as defined in [Media Fragments URI 1.0 (basic)] and possibly combined using the & sign (e.g.MyDrawing.svg#xywh=0,200,1000,1000&t=10).

16.3.2. SVG fragment identifiers definitions

An SVG fragment identifier is defined as follows:

SVGFragmentIdentifier ::= BareName *( "&"timesegment ) |                          SVGViewSpec *( "&"timesegment ) |spacesegment *( "&" timesegment ) |timesegment *( "&" spacesegment )BareName ::= XML_NameSVGViewSpec ::= 'svgView(' SVGViewAttributes ')'SVGViewAttributes ::= SVGViewAttribute |                      SVGViewAttribute ';' SVGViewAttributesSVGViewAttribute ::= viewBoxSpec |                     preserveAspectRatioSpec |                     transformSpec |                     zoomAndPanSpecviewBoxSpec ::= 'viewBox(' ViewBoxParams ')'preserveAspectRatioSpec = 'preserveAspectRatio(' AspectParams ')'transformSpec ::= 'transform(' TransformParams ')'zoomAndPanSpec ::= 'zoomAndPan(' ZoomAndPanParams ')'

where:

• ViewBoxParams corresponds to the parameter values for the‘viewBox’ attribute on the‘view’ element. For example,viewBox(0,0,200,200).
• AspectParams corresponds to the parameter values for the‘preserveAspectRatio’ attribute on the‘view’ element. For example,preserveAspectRatio(xMidYMid).
• TransformParams corresponds to the parameter values for thetransform property that is available on many elements. For example,transform(scale(5)). Currently additional tranform styles and parameters (e.g. transform-origin, perspective) are not supported.
• ZoomAndPanParams corresponds to the parameter values for the‘zoomAndPan’ attribute on the‘view’ element. For example,zoomAndPan(magnify).

SVG view box parameters are applied in order, as defined inCSS Transforms specification (e.g. SVG view is transformed as defined inViewBoxParams,then as defined inTransformParams).

Spaces are allowed in fragment specifications. Commasare used to separate numeric values within an SVG view specification(e.g.,#svgView(viewBox(0,0,200,200)))and semicolons are used to separate attributes (e.g.,#svgView(viewBox(0,0,200,200);preserveAspectRatio(none))).

The four types ofSVGViewAttribute may occurin any order, but each type may only occur at most one time in a correctlyformedSVGViewSpec.

When a source document performs a link into an SVG document, for examplevia anHTML anchor element([HTML]; i.e.,<a href=...> element in HTML) or anXLink specification [xlink], thenthe SVG fragment identifier specifies the initial view into the SVG document,as follows:

• If no SVG fragment identifier is provided (e.g, the specified URL did not contain a "#" character, such asMyDrawing.svg), then the initial view into the SVG document is established using the view specification attributes (i.e.,‘viewBox’, etc.) on theoutermost svg element.
• If the SVG fragment identifier addresses aspace segment (e.g.,MyDrawing.svg#xywh=0,0,100,100),then the initial view into the SVG document is established using the view specification attributes on theoutermost svg element where the 'viewBox' is overriden by the x, y, width and height values provided by the fragment identifier.
• Media fragments can be specified as "pixel:" (default) and "percent:". In the latter case the resulting 'viewBox' transformation is calculated against referenced SVG resolved size (width and height). When the host document cannot resolve the width and height of the SVG document, the used values for width and height should be calculated accorting to CSS rules forcalculating width and ratio for inline replaced elements.
• If the SVG fragment identifier addresses atime segment (e.g.,MyDrawing.svg#t=10),then the initial view into the SVG document is established as if no fragment identifier was provided. The rendering of the SVG Document shall be as if the setCurrentTime method on the SVG Document element had been called with the begin time value from the fragment identifier. Additionally, if an end time value is provided in the fragment identifier, the effect is equivalent to calling the pauseAnimations method on the SVG Document when the document time reaches the end time of the fragment identifier.
• If the SVG fragment identifier addresses a‘view’ element within an SVG document (e.g.,MyDrawing.svg#MyView) then the root‘svg’ element is displayed in the SVG viewport. Any view specification attributes included on the given‘view’ element override the corresponding view specification attributes on the root‘svg’ element.
• If the SVG fragment identifier addresses specific SVG view (e.g.,MyDrawing.svg#svgView(viewBox(0,200,1000,1000))), then the document fragment defined by the root‘svg’ element is displayed in the SVG viewport using the SVG view specification provided by the SVG fragment identifier. Parameters of the svgView specification override the parameters defined on the root‘svg’ element of the referenced document. Unspecified parameters of the svgView specification don't reset the values defined on the root‘svg’ element of the referenced document.
• If the SVG fragment identifier addresses a combination of the above non-time related identifiers with a time-related identifier (ie. a timesegment), the behavior of each identifier is applied.

Categories:

None

Content model:

Any number of the following elements, in any order:

• animation elements —‘animate’,‘animateMotion’,‘animateTransform’,‘discard’,‘set’
• descriptive elements —‘desc’,‘title’,‘metadata’

script,style

Attributes:

• aria attributes —‘aria-activedescendant’,‘aria-atomic’,‘aria-autocomplete’,‘aria-busy’,‘aria-checked’,‘aria-colcount’,‘aria-colindex’,‘aria-colspan’,‘aria-controls’,‘aria-current’,‘aria-describedby’,‘aria-details’,‘aria-disabled’,‘aria-dropeffect’,‘aria-errormessage’,‘aria-expanded’,‘aria-flowto’,‘aria-grabbed’,‘aria-haspopup’,‘aria-hidden’,‘aria-invalid’,‘aria-keyshortcuts’,‘aria-label’,‘aria-labelledby’,‘aria-level’,‘aria-live’,‘aria-modal’,‘aria-multiline’,‘aria-multiselectable’,‘aria-orientation’,‘aria-owns’,‘aria-placeholder’,‘aria-posinset’,‘aria-pressed’,‘aria-readonly’,‘aria-relevant’,‘aria-required’,‘aria-roledescription’,‘aria-rowcount’,‘aria-rowindex’,‘aria-rowspan’,‘aria-selected’,‘aria-setsize’,‘aria-sort’,‘aria-valuemax’,‘aria-valuemin’,‘aria-valuenow’,‘aria-valuetext’,‘role’
• core attributes —‘id’,‘tabindex’,‘lang’,‘xml:space’,‘class’,‘style’
• global event attributes —‘oncancel’,‘oncanplay’,‘oncanplaythrough’,‘onchange’,‘onclick’,‘onclose’,‘oncuechange’,‘ondblclick’,‘ondrag’,‘ondragend’,‘ondragenter’,‘ondragexit’,‘ondragleave’,‘ondragover’,‘ondragstart’,‘ondrop’,‘ondurationchange’,‘onemptied’,‘onended’,‘onerror’,‘onfocus’,‘oninput’,‘oninvalid’,‘onkeydown’,‘onkeypress’,‘onkeyup’,‘onload’,‘onloadeddata’,‘onloadedmetadata’,‘onloadstart’,‘onmousedown’,‘onmouseenter’,‘onmouseleave’,‘onmousemove’,‘onmouseout’,‘onmouseover’,‘onmouseup’,‘onmousewheel’,‘onpause’,‘onplay’,‘onplaying’,‘onprogress’,‘onratechange’,‘onreset’,‘onresize’,‘onscroll’,‘onseeked’,‘onseeking’,‘onselect’,‘onshow’,‘onstalled’,‘onsubmit’,‘onsuspend’,‘ontimeupdate’,‘ontoggle’,‘onvolumechange’,‘onwaiting’
• document element event attributes —‘oncopy’,‘oncut’,‘onpaste’
• ‘viewBox’
• ‘preserveAspectRatio’
• ‘zoomAndPan’

DOM Interfaces:

• SVGViewElement

We have resolved to remove viewTarget attribute.

Resolution: Paris 2015 F2F Day 3.

Owner: BogdanBrinza.

16.4.1. Interface SVGAElement

AnSVGElement object represents an‘a’ element in the DOM.

[Exposed=Window]interfaceSVGAElement :SVGGraphicsElement {  [SameObject] readonly attributeSVGAnimatedStringtarget;  attribute DOMStringdownload;  attribute USVStringping;  attribute DOMStringrel;  [SameObject, PutsForward=value] readonly attributeDOMTokenListrelList;  attribute DOMStringhreflang;  attribute DOMStringtype;  attribute DOMStringtext;  attribute DOMStringreferrerPolicy;};SVGAElement includesSVGURIReference;SVGAElement includesHTMLHyperlinkElementUtils;

Thetarget,download,ping,rel,hreflang,type, IDL attributesreflect the content attributes of the same name.

TherelList IDL attributereflects the‘rel’ content attribute.

ThereferrerPolicy IDL attributereflects the‘referrerpolicy’ content attribute,limited to only known values.

Thetext IDL attribute, on getting, must return the same value as thetextContent IDL attribute on the element, and on setting, must act as if thetextContent IDL attribute on the element had been set to the new value.

16.4.2. Interface SVGViewElement

AnSVGViewElement object represents a‘view’ element in the DOM.

[Exposed=Window]interfaceSVGViewElement :SVGElement {};SVGViewElement includesSVGFitToViewBox;SVGViewElement includesSVGZoomAndPan;