Please note, this is a STATIC archive of website developer.mozilla.org from November 2016, cach3.com does not collect or store any user information, there is no "phishing" involved.
« XUL Reference home [ Examples | Attributes | Properties | Methods | Related ]

Éste elemento debería pertenecer a query ("consulta"). La pregunta en una regla debería enlazar a sólo a un elemento del contenido. Los contenidos deberían tener al atributo uri . Ésto se utiliza para vincular una variable a un nodo de contenido cuando se emparejan. Cuando use un árbol con los atributos flags ("banderas"), establezca dont-build-content, ("no almacenar contenido"), use treeitem en su lugar.

Para más información, se encuentra disponible el tutorial XUL.

Propiedades
tag, uri

Ejemplos

(no son necesarios)

Atributos

Inherited from XUL element
align, allowevents, allownegativeassertions, class, coalesceduplicatearcs, collapsed, container, containment, context, contextmenu, datasources, dir, empty, equalsize, flags, flex, height, hidden, id, insertafter, insertbefore, left, maxheight, maxwidth, menu, minheight, minwidth, mousethrough, observes, ordinal, orient, pack, persist, popup, position, preference-editable, querytype, ref, removeelement, sortDirection, sortResource, sortResource2, statustext, style, template, tooltip, tooltiptext, top, uri, wait-cursor, width

Propiedades

tag
Type: tag name
This may be set to a tag name. If set, the conditions will only match if the template builder is parsing content for an element directly inside this tag. For example, by using a value of treechildren, the condition will only match when placing elements directly inside a treechildren tag. Thus, nested elements will not match because they are directly inside a treeitem. This attribute is useful to provide different rules for outer and inner elements.
uri
Type: ?
Used to specify the variable name for the content. When a rule is evaluated, it scans through each resource in the RDF datasource looking for a match. Each resource is placed in the variable specified in the uri attribute in turn. Then, the other rules are evaluated for a match. This attribute should always be present.

Métodos

Inherited Methods
addEventListener(), appendChild(), blur, click, cloneNode(), compareDocumentPosition, dispatchEvent(), doCommand, focus, getAttribute(), getAttributeNode(), getAttributeNodeNS(), getAttributeNS(), getBoundingClientRect(), getClientRects(), getElementsByAttribute, getElementsByAttributeNS, getElementsByClassName(), getElementsByTagName(), getElementsByTagNameNS(), getFeature, getUserData, hasAttribute(), hasAttributeNS(), hasAttributes(), hasChildNodes(), insertBefore(), isDefaultNamespace(), isEqualNode, isSameNode, isSupported(), lookupNamespaceURI, lookupPrefix, normalize(), querySelector(), querySelectorAll(), removeAttribute(), removeAttributeNode(), removeAttributeNS(), removeChild(), removeEventListener(), replaceChild(), setAttribute(), setAttributeNode(), setAttributeNodeNS(), setAttributeNS(), setUserData

TBD

Document Tags and Contributors

Tags: 
 Contributors to this page: Sheppy, M1k., ethertank, Brettz9, Mgjbot, Ptak82, Dria
 Last updated by: Sheppy,