More information is available in the XUL tutorial.
- Type: boolean
- Allows the contents of individual cells in the column to be changed, especially useful when
<treecol type="checkbox">. Also useful for disabling editing of individual treecells. When the user double-clicks an editable cell, a text field appears in which the user can edit the contents of the cell.
- Type: one of the values below
- For columns that are progress meters, this determines the type of progress meter to use.
- No progress meter is displayed. The cell text is displayed instead.
- The cell uses its value attribute to determine the amount of the bar that is filled in.
- The progressmeter is indeterminate.
- Type: URI
- For template-generated elements, this attribute is used to specify the root RDF node where content generation begins. This will correspond to the value of an about attribute on an RDF container. This attribute should be placed alongside the datasources attribute.
- Type: URI
- Set this to the URI of an image to appear in the tree cell. If this attribute is left out, no image appears. You can have both an image and a label.
- Type: string
- The string attribute allows you to associate a data value with an element. It is not used for any specific purpose, but you can access it with a script for your own use. Be aware, however, that some elements, such as textbox will display the value visually, so in order to merely associate data with an element, you could 1) Use another attribute like "value2" or "data-myAtt" (as in the HTML5 draft), as XUL does not require validation (less future-proof); 2) Use setAttributeNS() to put custom attributes in a non-XUL namespace (serializable and future-proof); 3) Use setUserData() (future-proof and clean, but not easily serializable). For user editable
menulistelements, the contents, as visible to the user, are read and set using the Menulist.value syntax. For those elements, setAttribute("value", myValue) and getAttribute("value") do not access or affect the contents displayed to the user.