Action

Should be contained within a rule element. It is used to specify the generated content for each matched node. Within the action, attributes are parsed for resource and variable references.

More information about action


Attributes:

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 ref removeelement sortDirection sortResource
sortResource2 statustext style template tooltip
tooltiptext top uri wait-cursor width

Properties and Methods:

Inherited from XUL Element:

align allowEvents blur boxObject boxObject.element
boxObject.getLookAndFeelMetric boxObject.height boxObject.screenX boxObject.screenY boxObject.width
boxObject.x boxObject.y builder className click
collapsed contextMenu controllers database datasources
dir doCommand flex focus getElementsByAttribute
height hidden id left maxHeight
maxWidth menu minHeight minWidth observes
ordinal orient pack persist ref
resource statusText style tooltip tooltipText
top width

Inherited from Element:

addEventListener
appendChild
attributes
childNodes
cloneNode
dispatchEvent
firstChild
getAttribute
getAttributeNS
getAttributeNode
getAttributeNodeNS
getElementsByTagName
getElementsByTagNameNS
hasAttribute
hasAttributeNS
hasAttributes
hasChildNodes
insertBefore
isSupported
lastChild
localName
namespaceURI
nextSibling
nodeName
nodeType
nodeValue
normalize
ownerDocument
parentNode
prefix
previousSibling
removeAttribute
removeAttributeNS
removeAttributeNode
removeChild
removeEventListener
replaceChild
setAttribute
setAttributeNS
setAttributeNode
setAttributeNodeNS
tagName
Add a note User Contributed Notes
April 9, 2004, 6:51 pm pike at kw dot nl
it should be noted that the "id" attribute on elements inside actions
(or generally inside templates) is generated by the template. what
happens exactly is described here
http://www.mozilla.org/docs/xul/xulnotes/template-primer.html

If that page is correct, multiple elements may get the same id.
anyways, document.getElementById() does generally not return the
visible onscreen element and some internal bindings (like docShell
- designMode ?) also seem to break inside a template.

Yes, getElementById would return the element inside the template. You should avoid using ids inside a template - Neil

Copyright © 1999 - 2005 XULPlanet.com