3.1. Using the attribute table

The content of the attribute table can be described as follows:

Procedure for adding an attribute or changing its value:

  1. Click on the field at the right of the attribute name. This field is editable.

  2. Type the value of the attribute.

    If the attribute type is enumerated, this field is a menu rather than a text field, so you can directly choose the value of the attribute without having to type anything.

  3. Press Enter to commit the change.

Procedure for removing an attribute:

  1. Right-click on the row of the attribute to be removed.

  2. Select the Remove item in the displayed popup menu.

    Note

    The "Force Removal" item is by default absent in the above popup menu. You need to explicitly enable it by checking "Enable the 'Edit|Force Deletion' menu item" in OptionsPreferences, General|Features section.

3.1.1. Reducing the number of attributes displayed by the attribute table

Clicking the down arrow button found at the right of the header of the attribute table displays a popup menu.

Figure 7.1. Popup menu when a DITA element is selected

Popup menu when a DITA element is selected

This popup menu allows to toggle in the attribute table the visibility of attributes belonging to certain categories. Simply uncheck a menu entry to hide in the attribute table all the attributes belonging to the corresponding category.

All the XHTML configurations define an attribute category called "Scripting". This category contains attributes such as onclick, onload, onmouseenter, etc (up to 62 scripting attributes for XHTML5!). The "Scripting" category is hidden by default.

DITA configurations define a "Conditional Processing" category (audience, platform, etc) and an "Other" category (xtrc, xtrf; hidden by default).

DocBook configurations define a "Profiling" category (arch, condition, etc) , a "Scripting" category (onclick, ondblclick, etc; hidden by default) and an "Other" category (remap, xml:base, etc; hidden by default).

Note that, even when attributes have been made hidden, it's still possible to specify them using the attribute form (auto-completion fully supported there) found above the attribute table.

Also note that once an attribute has been specified for an element, it is displayed in the attribute table in all cases, no matter whether it belongs to a category marked as hidden.



[14] This can be configured, see Section 3.1.1, “Reducing the number of attributes displayed by the attribute table” below . See also the attributeVisility configuration element in XMLmind XML Editor - Configuration and Deployment.