node
This topic describes the node element.
Description
The <node> element can be used to configure a node, element or attribute in different ways, such as role, pretty name, placeholder and templates.
<x:node match="td">
<x:role>tablecell</x:role>
<x:name xml:lang="en">Cell</x:name>
<x:name xml:lang="nl">Cel</x:name>
<x:placeholder>{name}</x:placeholder>
<x:templates>
<x:template class="red">
<p><?start?></p>
</x:template>
</x:templates>
</x:node>
Namespace
http://www.xopus.com/xmlns/config
Attributes
| Name | Description and use | Type |
|---|---|---|
match | An element name that selects elements and/or attributes that you want to configure. The match attribute does not work like XPath in XSL. It has a few restrictions, which are detailed here. | |
ignoreMixed | Optional. This attribute can be used to work around an issue that arises out of the use of block level elements, such as lists ( | Boolean |
preferElementsOnlyParent | Optional. This attribute can be used to guide Content Editor in the creation of new elements. Some schemas define mixed content elements that have the intention that the author uses either text with "inline" markup or a sequence of "block"-like elements. By setting this attribute to | Boolean |
preferText | Optional. This attribute helps Content Editor give text content priority over element content in the node it is specified for, when that node is defined as mixed content in the schema. It's useful for actions such as toggling between paragraph(s) and lists. eg: When a listitem node has set the | Boolean |
Parent element
nodeconfig